Josh
Forum Replies Created
-
Excellent.
Thank you for the confirmation.Please let me know if you experience any other issues.
Forum: Reviews
In reply to: [HMS Testimonials] Awesome PluginYou did a nice job with the styling them on the WP Edit website.
Thank you, thank you very much. I agree, it looks really nice π Thank you for making it possible.
Unfortunately I haven’t had the time over the past few months to knock it out.
Ohhh… I know the feeling there!!
At first, I was planning on having 1 setting to define the order, but the ability to create forms is a good one and I will go that route.
What I was thinking… on the “custom fields” page… if that order in the top meta box could be sorted.. and output that order on the front-end form… it would be great.
I’m not sure how that order ties in with other aspects of the plugin… but if it doesn’t interfere.. that would be my route.
I also plan on fixing the star ratings. It’s a bit “hackish” to get images to show up especially for people not familiar with PHP.
Yes.. agreed. But it still works great when done properly! Perhaps include a royalty-free set of star images in the plugin… and just code a checkbox option to use the number rating or the star images?
You have an awesome plugin here. I tried all the other testimonial plugins and yours was the only one I could find which allowed everything I needed.
Thank you!
Forum: Fixing WordPress
In reply to: Database issueπ My pleasure.
Glad you got it working properly.[Marking topic as resolved.]
Forum: Fixing WordPress
In reply to: Jetpack forces image to max 300pxHow about:
.site-logo-link img { width: 500px; height: 500px; }Forum: Fixing WordPress
In reply to: Database issueWell; comment meta was introduced in WordPress version 2.9. It’s possible your WordPress installs are using versions before 2.9… in which case the table would not exist.
You can attempt to run the following SQL query to add the comment meta table:
CREATE TABLE wp_commentmeta ( meta_id bigint(20) unsigned NOT NULL auto_increment, comment_id bigint(20) unsigned NOT NULL default '0', meta_key varchar(255) default NULL, meta_value longtext, PRIMARY KEY (meta_id), KEY comment_id (comment_id), KEY meta_key (meta_key) )I’d take a database backup beforehand.. just to be safe.
Got it.
Thanks mate.Forum: Plugins
In reply to: [WP Edit] 3.0 is conflicting with WordPress Firewall 2No worries at all π
Thank you for taking the time to work with me.
Please have a wonderful new year.
Forum: Fixing WordPress
In reply to: Add button for span in tinyMceIt’s pretty code intensive… but these guys have a really good tutorial.
Forum: Plugins
In reply to: [WP Edit] 3.0 is conflicting with WordPress Firewall 2Okay… here is the deal with the error.
The Firewall plugin is using code to search the url parameter and compare it with different values. Here is the code (plugin lines 190 to 203):
if(get_option('WP_firewall_exclude_terms') == 'allow') { $exclude_terms = array('#wp_#i', '#user_login#i', '#user_pass#i', '#0x[0-9a-f][0-9a-f]#i', '#/\*\*/#'); foreach($exclude_terms as $preg) { foreach($request_string as $key=>$value) { if(preg_match($preg, $value)) { if(!WP_firewall_check_ip_whitelist()) { WP_firewall_send_log_message($key, $value, 'wp-specific-sql-injection-attack', 'WordPress-Specific SQL Injection'); WP_firewall_send_redirect(); } } } } }It is using a search pattern (preg_match) to determine if any of the url parameters match what the plugin deems “insecure”.
Since my plugin page uses the page name of “wp_edit_options”… it is matching the “#wp_#i” preg_match… thus generating the error.
This is a legitimate page… so the Firewall plugin is incorrect. You will need to disable that plugin (and find an alternative)… or adjust it’s code, and remove that “#wp_#i” from the array.
Just following up. Did you ever send me an email?
Forum: Plugins
In reply to: [WP Edit] Second row of buttons MIA?Just following up… did you get this sorted out?
Forum: Plugins
In reply to: [WP Edit] 3.0 is conflicting with WordPress Firewall 2I apologize. I wasn’t suggesting the plugin wasn’t functioning properly; that’s my mistake if that is what I inferred.
I was suggesting it’s better to use plugins which are up-to-date… and not using outdated WordPress hooks and filters. My debug log fills with errors when that plugin is activated. One function being used has been outdated since WordPress version 2.0.
I’m not sure what to suggest as an alternative. I suppose if you are not noticing any server or performance issues… then you might not need/want to change.
As far as the error it is reporting.. I’m still digging into. I’ll post back when I get a little more information.
EDIT: Can you provide me the exact steps to replicate the issue?
Forum: Plugins
In reply to: [WP Edit] 3.0 is conflicting with WordPress Firewall 2Okay… I just downloaded the firewall plugin.. and immediately received numerous php warnings.
Specifically… I see this notice across all pages:
Notice: has_cap was called with an argument that is deprecated since version 2.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in C:\xampp\htdocs\src\wp-includes\functions.php on line 3495That means it is using an older, non-supported, WordPress function… which begs the question of whether the plugin works on current versions of WordPress (we are seeing one symptom now).
Also, when I hover over “Settings” in the admin menu… there is a lot of space where an error is being shown. If you turn on error reporting in WordPress… you’ll also see these notices.
Lastly, since that plugin is not hosted on the WordPress.org plugin repository… I cannot be certain of it’s validity.
So… all in all…. I’d probably recommend searching for a more up-to-date plugin which has the same features.
As far as it alerting me of my plugin… I can’t seem to replicate that issue. I am able to see the WP Edit settings page (although the noticed mentioned above still appears). Also, no emails have been sent to me from my site.
I’m sorry, but I can’t seem to replicate your exact issue. My recommendation would still be to find a more updated plugin; or possibly email the author of the firewall plugin and ask if they are aware of the php notices.
Hi,
Are you upgrading from a previous version… or did you just install it for the first time?
If you are upgrading…. try resetting the buttons; and see if the issue persists.
If this is the first time… then some other jquery is interfering with the plugin settings page.. and we’ll have to identify which one.
Forum: Plugins
In reply to: [WP Edit] 3.0 is conflicting with WordPress Firewall 2Wow – Okay….
There is certainly no malicious code in WP Edit; so don’t worry about that part π
I wish the firewall plugin provided a little more info… something like the file or line number where the error is occurring.
Can you provide me a link to the Firewall plugin you are using? I’ll download it and see if I can replicate the issue on my end.