Hi Charlotte,
Thanks for the kind words and for using our plugin! I’m happy to help get to the bottom of this and get you squared away.
I’ll first try to reproduce the problem myself, I just need some deets about your setup.
1. The name of your theme
2. A list of all your active plugins
3. Your version of PHP (if you do happen to know)
4. Your favorite color (j/k)
Frankie
Hi Frankie, thanks for the quick reply!!
I think this should be what you need – I have the MOST AWESOME THEME EVER and this info is captured in 1 place to copy and paste!!
# SITE_URL: https://store.charlottesogn.com
# HOME_URL: https://store.charlottesogn.com
# IS MULTISITE : No
# THEME | VERSION : customizr-pro | v1.2.38# WP VERSION : 4.7.1
# PERMALINK STRUCTURE : /%postname%/
# ACTIVE PLUGINS :
Booster for WooCommerce: 2.5.9
Childify Me: 1.0.15
Coming Soon Page & Maintenance Mode by SeedProd: 5.0.5
Contact Widgets: 1.4.0
Custom Login Css: 1.0.1
Disable Comments: 1.6
Formidable Forms: 2.02.13
WooCommerce: 2.6.12
WooCommerce Helper: 1.7.2
WooCommerce Stripe Gateway: 3.0.7
WP101 Video Tutorials: 0.3
WPFront User Role Editor: 2.13
PHP Version: 5.6.27
MySQL Version: 5.6.32-78.0-log
Web Server Info: Apache
WordPress Memory Limit: 40MB
PHP Memory Limit: 256M
PHP Upload Max Size: 64M
PHP Post Max Size: 65M
PHP Upload Max Filesize: 64M
PHP Time Limit: 30
PHP Max Input Vars: 1000
PHP Arg Separator: &
PHP Allow URL File Open: Yes
WP_DEBUG: Disabled
Show On Front: page
Page On Front: shop (#251)
Page For Posts: (#0)
AND, if you go to my website: https://store.charlottesogn.com OR https://charlottesogn.com I bet you can tell what my favorite color is!! (Hint: #26cad3).
Thanks so much for your help and let me know if you need more info!!
Charlotte
Charlotte,
I was able to reproduce the issue you described, and deactivating the WPFront User Role Editor plugin fixed it.
It’s happening because that plugin is adding a custom “User Restrictions” field to every widget, which our widgets weren’t designed to explicitly support.
I’ve created a bug report for this on our repo so we can add support for custom fields and prevent these errors in the future.
Thanks for reporting it!
Frankie, Thank you so much!!! I added the plugin to the sidebar and it looks awesome!!!
How can I find out when the plugin conflict is resolved? I feel like I may well need the User Role Editor.
Thanks so much for your help and have a great day,
Charlotte
Frankie, one more question pertaining to GoDaddy:
One of my plugin developers (Formidable) says that my site has error reporting turned on. About 6 weeks ago I did see a couple of error messages so I know that is correct. They indicated that I should work with my host tech people to turn error reporting off because that is a site security issue.
I called GoDaddy several times on this. We’ve checked the wp-config.php file, also the php.ini, user.ini and gd-config.php files. Everything seems to be indicate that error reporting SHOULD be turned off but I know from the previous experience that isn’t correct.
I’ve come to a COMPLETE dead end – it’s a complete “he said, she said” between the plugin developer and GoDaddy. I’m DESPERATE for any ideas on a board I can post on, or any kind of resources to get more ideas on how to solve this.
I KNOW this is off-topic – many apologies – and HOPE you can give me even just a little advice on where to go.. thank you in advance!!!
Charlotte
The issue will be fixed the next release of Contact Widgets.
In the meantime, just deactivate the User Role Editor temporarily while you are saving your contact widgets, then activate it again after.
I’ll give you some general info about how PHP errors work in WordPress, but I would recommend you call our awesome support if you get stuck.
1. Changing the error_reporting or display_errors directives at the PHP level (ini) won’t help you because WordPress will override these settings anyway.
2. In order for PHP errors to be displayed, you have to manually add a WP_DEBUG constant to your wp-config.php file and set it to true. So as long as WP_DEBUG is missing from your wp-config.php file, or if it’s there but set to false, then PHP errors won’t be displayed on your site.
See https://codex.ww.wp.xz.cn/WP_DEBUG
3. By default, WP_DEBUG is set to false and WordPress will not display PHP errors.
If all of the above is configured correctly, and you’re still seeing errors, then my guess is that the errors you’re seeing aren’t from PHP.
Thanks, Frankie!! Yes, I think that must be the case, that the errors aren’t from PHP. This is an excerpt from my wp-config.php file:
* For developers: WordPress debugging mode.
*
* Change this to true to enable the display of notices during development.
* It is strongly recommended that plugin and theme developers use WP_DEBUG
* in their development environments.
*
* For information on other constants that can be used for debugging,
* visit the Codex.
*
* @link https://codex.ww.wp.xz.cn/Debugging_in_WordPress
*/
define(‘WP_DEBUG’, false);
require_once( dirname( __FILE__ ) . ‘/gd-config.php’ );
define( ‘FS_METHOD’, ‘direct’);
define(‘FS_CHMOD_DIR’, (0705 & ~ umask()));
define(‘FS_CHMOD_FILE’, (0604 & ~ umask()));
/* That’s all, stop editing! Happy blogging. */
So, at this point GoDaddy says “see, you’re good!” but I got error messages in spite of that!! If my errors are coming from somewhere else, what next? Is it a security risk or not? If not, then I’ll leave it be and not worry about this any more. But if it is, ANY suggestions or guidance on where to go is GREATLY appreciated!!
Thanks so much and keep me posted on when the plugin conflict is resolved!!
Charlotte
It’s also possible that a rogue plugin or a file somewhere in your theme is defining WP_DEBUG. Have you checked the functions.php file in your theme or child theme?
You could also try adding define( 'WP_DEBUG_DISPLAY', false ); just above the /* That’s all, stop editing! Happy blogging. */ line in your wp-config.php file.
I did check with my theme developer BUT my child theme is via a plugin so I will check with them too. Also, I just had a quick look at the functions.php files that I could find (Filezilla) but didn’t really see anything.
Thanks for the snippet!! I looked that up and it seems like it’ll hide error messages.. don’t I want to know if something isn’t working correctly? Also, is it true that having debug mode on is a security risk? That is my main reason for pursuing this.
I’m waiting on GoDaddy to update my WP to v 4.7.1 then I will add the snippet after I confirm that everything is running ok on the new version – should be anytime now!!
THANK YOU!!!!!!!!
I recommend you speak with our awesome hosting support team to dive any deeper on this error issue.
Will do, but there’s the rub – GoDaddy says everything is hunky dory!!
My plugin developers says they’re wrong, and I have a security issue!!
NOW do you see my situation??
Anyway, I will keep this on my radar and THANKS FOR YOUR HELP!!!
Please keep me posted on the plugin conflict between Contacts Widget and WP User Role Editor!!
have a great day,
Charlotte
Hi Frankie and guys!!
Why did you mark this topic as “Resolved”??
I am going to have to put my store on my main blog domain to make it work properly. (long story) Anyway, I installed this plugin on my blog charlottesogn.com just now and it still doesn’t work! I enter my email and phone number and a title and the Save dot just spins around and around and never does finish saving the settings.
Also, I did resolve the other issue and let me know if you want to know how that worked out.
So, for me, it still doesn’t work! Please advise and let me know what info you need from me.
Thanks for your assistance and have a great day!
Charlotte
FYI, it still seems to be a conflict with User Role Editor, if that helps.
Thanks!!
Charlotte
The issue has been fixed but not released. New version will be going out next week.
