bhambob

As I feared… but thanks for confirming. I fooled around a little with using JS/JQuery to modify the input field to type “tel” and adding a pattern, but couldn’t get the oninvalid event to work… moved on to more important issues. Appreciate the quick reply. Thanks.

BTW, added this CSS to show unavailable days with line-through:

/* strikethrough unavailable days, and ensure default cursor */
.ui-datepicker td.ui-state-disabled .ui-state-default {cursor:default;text-decoration:line-through;}

I did just now confirm that the unavailable days (e.g., Mon) cannot be selected and the font is grayed out. My bad for submitting this issue. Please close/delete.

Sorry. Should’ve noted versions: WordPress 4.7.2, Wordfence 6.2.10

Noticed that “Unable to open /var/www/html/wp-content/wflogs/config.php for reading and writing.” has again reared its ugly head just the last few days. Action to be be taken?

Crashed our test site. Forced to delete plugin directory to restore operation. Not going to risk using new release with production site.

Our setup is as follows:

(TEST/DEV) /var/www/development/wp-content/plugins/etc…
(PRODUCTION) /var/www/html/wp-content/plugins/etc.

For obvious reasons, only Production has WAF

took site down. Forced to deleted WordPress plugin directory to restore operation.

With my fingers crossed… I *think* I may have successfully addressed the problem. I took a look here and moved my session_start upstream, into an init action. In the 45 minutes that have elapsed since this change, none of the aforecited errors have occurred. More importantly, the objective for the sessions to being used to begin with seems to have not been compromised.

There is a built-in WP session manager? I didn’t see anything in the WP functions. Should I schedule an optometrist appointment?

I looked at the suggested link, and am already familiar with what can lead to the error. In this case, though, the error began to occur with the install of 4.5.2, and the echo statement at /var/www/html/wp-includes/class.wp-styles.php:237 is where the first output character is emitted. Then I come along later with a session_start() command in a theme functions file, which leads to the error.

Thanks. Will check it out.

So, apparently version 4.5.2 introducing problems is of no concern. I mean, really, we’re supposed to never update again?

Can I get some help with this or not? If not, how do I back up to version 4.5?

We are getting pummeled by this problem, hundreds and hundreds of errors are raised each day. This was never an issue before we moved from 4.5 to 4.5.2.

And I was so hopeful… Before making any change to production I did a file compare between the class.wp-styles.php installed and the one I extracted from a downloaded zip file. They are identical. Other ideas?

For example, XYZ or xyz, or XyZ, or xYz, etc. Use (X|x)(Y|y)(Z|z) and set regular expression checkbox.