bureaugravity

Somehow this started working for me. I can’t remember how I got it working… I may have deactivated and reactivated the plugin, clicked the button to start building the index, and then didn’t click it again until it was finished.

Have you considered that there might be some other problem on your site causing the issue?

It’s very unfair to the developer to be given bad reviews based on something they can’t control.

I’ll note that in checking this again, the password strength is not technically a requirement anymore, as in the product can be ordered and the account created without the password needing to be a sufficient strength. But as the support thread before this indicates, the css needs to be added to hide the password strength indicator.

I will mark this topic as resolved, but I would like to go on record as saying the css should be part of the plugin.

Thank you! XD

I’m glad I was able to be precise enough to be helpful. Yea, ending files in ?> isn’t best practice before headers, but I was dealing with already written third-party theme files that had them in there. I’ll make sure to check that when editing theme files in future until you release the patch. Thanks for responding!

I don’t remember mentioning this issue ever before.

I was using string locator with a theme called “CityNews”, which uses Visual Composer, to find the string “twitter” in the theme files, because the twitter share button has had issues with correctly escaping double and single quotes for the url (that is an issue with the theme, not with string locator)

My problem with string locator came when I opened a theme file called wp-content/themes/citynews/inc/shortcodes/inc/shortcodes_set.php. The file opened and the nice, color coded editor displayed. I edited line 506, which was part of a PHP if statement, to remove the esc_attr function to see how that would affect the output of the share links.

After saving the file, I noticed I was getting header errors on some pages in WordPress (after trying to update posts, view media files, etc), and the error messages directed me to the last line of that file I had edited. It turns out that after editing and saving the file a few times, there were a few newlines appended to the end of the file. I was able to erase the newlines and the problem was fixed, but I can tell the editor is adding newlines because every time I load the file, a newline has been added to the end of the file. So by opening, editing, and saving the file repeatedly, newlines get appended to the file repeatedly.

Here is a video of opening the file, finding a newline at the end, erasing it, saving the file, and seeing the newline still appear at the end: https://youtu.be/RsxvcUG8_sE

Never mind, found my solution.

We had iThemes plugin installed, and “Disable File Editor” was enabled. This added a line to the wp-config.php file that disabled the “edit_theme” permission.

Yes, the backups downloaded just fine by right clicking and saving.

Hi, I’m having this same issue on one of our sites. Single-site, menu doesn’t show up, can’t access page directly because of insufficient permissions error even on administrator account. Any advice or solutions?

That is the solution I have decided to use for myself. It’s too bad nobody else has had this issue and come up with the reason why it broke in the first place.

I rolled WordPress back to version 4.3.1, and everything is working again. So it’s a compatibility error between WordPress 4.4 and WooCommerce or the WooCommerce NMI addon.

Thank you for your responses.

@esmi I’d need to create a staging site, because disabling every plugin or changing the theme is not possible since the site is live and has relatively high traffic. I know I shouldn’t have made an upgrade without backing the site up or testing it in a staging environment, so that’s my fault.

@marios That makes sense, and I figured as much. I just hate it when the only solution it to wait for a plugin author to fix it. Oh, and I have WP_DEBUG set to true, but WP_DEBUG_DISPLAY set to false and WP_DEBUG_LOG to true so that I can keep track of errors, as the site is live and I’m trying to maintain it.

Thanks again!