Ben Meredith

Hey @catalaco!

Definitely would love to help out here. Have you opened a support request on this issue? Our team is more than happy to get to the bottom of whatever problems you are having.

The transition from a really old iThemes Security version to the newest Solid Security versions might encounter some hiccups, but we have had a ton of success working through any issues with folks.

Let me know if you’d like help getting to the bottom of it.

For any who might stumble onto this and still have trouble getting that above code to work, a few things:

First, after you implement the snippet in @iovamihai’s last note here, make sure to deactivate and reactivate *any* plugin. Solid Central (currently) only goes and fetches a fresh list of Menu items when a plugin is activated.

Next, our team (on the SolidWP side) is looking into how we can better handle the situation where plugins (SliceWP is not the only one!) who conditionally display menu items. For now this workaround will do, but we ultimately want to find a less hacky solution.

Thanks!

Hey @wpsupacc!

Glad you reached out here!

I was able to replicate what you are seeing, but I’m trying to more fully understand exactly how you see it as a problem. Correct me if I’m wrong here:

1. Users have the ability to request an export of their personal data.
2. In order to facilitate that, they must log into the site.
3. In order to log into the site, they’ll need the hide backend slug
4. That slug has to be sent to them to allow that functionality.

What am I missing? Is there a use case for exporting personal information from a user that doesn’t need to log into the site?

The hide backend slug is not sensitive information, it’s a simply obfuscation of the login URL.

In fact, it’s fairly universally regarded as “not really making the site any more secure” as compared to CAPTCHAs and passwordless logins, etc. It does help users to feel like their site is more secure, but the real security happens with brute force protections, hardening of passwords, 2-Factor Authentication, and other protections.

We’re more than happy to clarify, or to learn more about why you believe this to be a problem.

Have a great weekend!

Hey @creation498!

My second favorite type of issues are ones that resolve themselves. (my first favorite are bugs that we catch in Quality Assurance before we even send them out in public)

Glad to hear this is resolved. If you need anything else at all, we’re happy to help.

For reference, the error message you supplied in that first message is one that comes from “above” (or “below” depending how you visualize the server stack) PHP or WordPress, likely from the NGINX level (according to my brief web search for the error). So it’s not an error message that Solid Security itself is generating. I do find it curious that it was resolved by reinstalling WP without Solid Security, but I am working under the assumption that that was a cooincidence.

Generally speaking, the next time you’re troubleshooting an issue that you have a suspicion is caused by Solid Security, adding this line to wp-config.php will completely disable anything that Solid Security is doing (whether it’s active or not):

define('ITSEC_DISABLE_MODULES', true);

Hi @filona!

Were you able to resolve this? We’re more than happy to continue troubleshooting, if not. @nlpro’s tip of that other thread was super helpful, but in case you missed it, the solution is to add the following line to the wp-config.php file, anywhere between the opening <?php and the line that says That's all...:

define('ITSEC_DEBUG', true);

Once you’ve done that, reload the back end of the website and you’ll see a “Debug” option in the menu under the “Security” heading. Navigate to that Debug page, and scroll to the bottom, where you’ll see an option to “force” the notification to be re-sent, which will add in an integer into that log, which in turn will make the error go away.

I’m going to see if I can replicate that error on a test site (or four) and prevent it from happening. It’s certainly annoying.

Let us know if those steps don’t resolve the issue, and we’re happy to keep troubleshooting!

Very glad to hear this is resolved. Thanks as always to @nlpro for the assist!