WendyDelfosse
Forum Replies Created
-
Forum: Plugins
In reply to: [Just Custom Fields] Fatal error after last updateI truly appreciate that. I’m not on Skype so I won’t ping you there. However this is a non-essential issue for me for the time being as I was using the plugin for something toward future development rather than current use. I did want to alert you quickly in case it affected other users. I appreciate you looking into it so thoroughly and quickly. Hopefully it really was a weird one-off problem. ??
Forum: Plugins
In reply to: [Just Custom Fields] Fatal error after last updateWP 4.3.1
No other custom fields running right now I believe.The update caused a fatal error as well:
Parse error: syntax error, unexpected T_PAAMAYIM_NEKUDOTAYIM in /home1/corecomm/public_html/wp-content/plugins/just-custom-fields/inc/functions.fields.php on line 14
Forum: Plugins
In reply to: [Just Custom Fields] Fatal error after last updateHmm, strange, I tested it on another site, including one from the same host and it works there. but when I tried deleting and reinstalling it still causes a fatal error and won’t activate. I’m more implementer than developer. If you can tell me what details about server config you need I can probably find them.
Forum: Plugins
In reply to: [Just Custom Fields] Fatal error after last updateApparently Hebrew. Means double colon. ::
Forum: Plugins
In reply to: [Just Custom Fields] Fatal error after last update5.4
You might want to check this thread with a similar issue. Looks like the plugin author commented on that one about logging the issue.
Forum: Plugins
In reply to: [WooCommerce] Too many wc transients created in DBOP, Try going to WooCommerce on the side menu, System Status. Then at the top the tab for Tools and you can clear WC transients there.
Mike, That sounds like an awesome update! Thanks for logging!
I had the same issue with WordFence tonight. After looking at what had changed in my files it seems like all the differences were a URL being changed from https:// to https://. I’ve seen other plugins throw warnings like this when a plugin author makes changes to files in a way WordFence doesn’t like. I’m not sure if that helps you to know, monk3, but wanted to let you know it’s not just your site and I’m not overly concerned about the changes myself.
To the plugin author–thought you might want to know about all those warnings being thrown to users who have WordFence installed. (Also thanks for the plugin & all your work!)
Don’t know if you’re still wondering but If I had to guess I’d guess it is the managed hosting because I got the same issue on the same two files when I migrated a site to GoDaddy’s Managed WordPress.