Helen Hou-Sandi

What role are you giving users that you’re trying to block? The plugin will not allow access for users who aren’t a subscriber or higher. There are filters in place you could use to alter the user role check using code but no current plans for UI to choose that, as the plugin’s goal is really logged in vs. logged out user and not capability checking.

Hi there – this plugin is geared toward restricting entire sites rather than specific pages. It is possible to accomplish this using some code, but it may be that your particular use case would be better suited for a plugin that’s made to block specific pages based on membership or something else.

Hi @patbell101 – if you choose one of the other settings for Site Visibility, like “Allow search engines to index this site”, it should function as turning it off.

Hi @leoland and @qroberts – thanks for reporting the issue. I believe this should be fixed now in 7.0.1; please let me if not.

Thanks for reporting this – seems like it was the missing piece in why I couldn’t reproduce the issue as originally reported on GH. It seems likely to be a less common setup or else there’d be more reports but I’ll try to get that fixed up today.

Hi @embedplus! Thanks for the report. I’ve created a GitHub issue for tracking here: https://github.com/10up/ads-txt/issues/26

Do you have any info on specific crawlers that do this? I’m not against fixing this at all, I would just like better understanding of why they do this and if they fall back to the non-query string URL at all.

Hi @felipebadr! We chose this route for a number of reasons, including the potential amount of content somebody might enter (the potential scenario where it’s too much to be stored or retrieved reliably from options), the ability to customize how posts and post content are stored and retrieved, and perhaps most importantly from the editor/site admin perspective, taking advantage of the built-in revision functionality. Revisions are not yet easily available in the UI because of some quirks in revision navigation that make it not ready for general usage yet, but it’s planned for the next release.

If there are any specific things you feel we could do to further optimize the plugin, happy to hear about them. Otherwise, I’m sure there are other plugins out there that better fit what you’re looking for, which is the benefit of the WordPress ecosystem!

The plugin itself does not store or transfer user data.

Well, fortunately that was a quick catch ?? Version 6.2.1 is out now and should address the issue. Please let me know if it doesn’t, and thanks to all of you for reporting the issue!

Hi all – I apologize for the bug going uncaught before release. I’m working on identifying the issue now and will work to release a fix very soon.

This should be fixed in 2.3.1, let me know if you still have the issue!

Thanks for bringing this over to GitHub ?? Linking here for future reference: https://github.com/10up/simple-page-ordering/issues/19

I did some more testing, so to be specific – it does work if you drag a page in between a parent and existing child or between two existing child pages. The plugin makes the reasonable assumption that if you do that you want it to be in that hierarchy. You cannot, however, create new hierarchies where there were none before.

Hi there – if you’re willing to give this plugin another shot, could you try version 2.3 and see if that fixes your issue?

Thanks for reporting your issue with helpful details! This should be fixed in the new release of version 2.3. Let me know if it still doesn’t work for you.