jayPEG
Forum Replies Created
-
Forum: Plugins
In reply to: [Plugin Organizer] Duplicate RulesHey Jeff,
We copied the site to a testing server and after removing it and ensuring that all the DB Tables were removed, we re installed it and the issue was then resolved. If we were able to provide you with the DB Tables from the live site, do you think you might be able to tell where a corruption may have occurred?Forum: Plugins
In reply to: [Plugin Organizer] Duplicate RulesThank you Jeff. I wonder if it’s a corruption and simply needs to be removed and re installed. We’ll give that a try.
Thank you Vij! I just updated it and tested and it appears to work perfectly. Thank you so much for adding this feature request.
Thank you very much Vij. I’ll look forward to it. Just a thought, it would be cool if it could also be disabled by product category.
Thank you for a truly great Plugin!
Thank you Ewout! That did the trick. Using the WooCommerce – Store Toolkit Plugin, I was able to easily find the custom fields needed to output them into the template.
Your help was exactly what I was in need of.Forum: Plugins
In reply to: [Contact Form 7] Form not sending emails over 7MBThank you Takayuki. It’s a red border.
Forum: Plugins
In reply to: [Ad Blocking Detector] Whitelist IP for blockingTerrific! Thanks again for the information.
Forum: Plugins
In reply to: [Ad Blocking Detector] General Plugin Usage QuestionsJohn,
Thank you so much for the very detailed explanation of your Plugin.I’ve tested it on the small-scale already and it appears to work really well.
I’ll let you know if I run into any issues, but so far, so good.
Very good. I guess it just didn’t reveal itself until the FooGallery upgrade for some reason.
I very much appreciate it and will contact the theme developer.Absolutely! I have Debug active. Thank you!
Thanks bradvin. It’s a site that’s under development Here
The pages are using the Masonry template, but it’s breaking theme styles across the site, even on non gallery pages.
Here’s a screenshot of the pages as it appears with the styles working correctly using 1.2.4:
1.2.4…and here it is with the broken styles after updating to 1.2.6:
1.2.6…and finally, this may help, after updating, it’s causing some theme files to not load in some way.
Console ErrorsI can provide an admin login if it helps. I have “WP Rollback” installed to go back and forth between the two versions.
I don’t believe so, but it is a possibility.
Certainly. It was built using a child theme to the “Boilerplate” theme, however current testing is on the Twenty Fifteen theme.
Nothing in the error logs unfortunately. There were a couple notices that I resolved due to having defined a constant after the wp-settings.php in the wp-config.
At the beginning, I left W3 Total cache enabled and wouldn’t get any other errors, but after disabling W3 Total cache, I would get the notices & warning when updating a recurring event. It doesn’t appear to be anything major though.
I also checked for any white spaces in the PHP that might cause the “Cannot modify header” warning.
I went ahead and selected all of the recurring events and changed them all to “draft” and then back to “published” to see if any of them might have been stuck, but no luck there.
Notice: Undefined index: event_attributes in /usr/local/www/site.com/wp-content/plugins/events-manager/classes/em-event.php on line 2007 Warning: Cannot modify header information - headers already sent by (output started at /usr/local/www/site.com/wp-content/plugins/events-manager/classes/em-event.php:2007) in /usr/local/www/site.com/wp-admin/post.php on line 237 Warning: Cannot modify header information - headers already sent by (output started at /usr/local/www/site.com/wp-content/plugins/events-manager/classes/em-event.php:2007) in /usr/local/www/site.com/wp-includes/pluggable.php on line 1196Thanks again!
They actually are listed as Published and displaying on the front-end. I installed it and tested on a completely separate site and it works perfectly.
As far as I know, they’ve been accumulating since the ability for site users to submit the front-end form was implemented. They all come in as “Pending” and one of the site managers receives an email letting them know of a new event submission.
Could there be any server-specific issues that might cause something like this? It is running on an NGINX server with a front-end proxy.
