Fixed it.
Rather than deleting, I will add here that the fix was to disable the Solid Security plugin. It was blocking the request that was sent to pull a list of pages.
Hey @p42webdev
Do you mean our settings page? Solid Security was blocking us getting the pages to show in the select box?
Correct. Settings page and yes Solid Security was blocking the URL you are calling to get a list of pages.
Disabling the Solid Security plugin, loading and setting the page to use in the Settings page, then turning the plugin back on worked.
ok thanks. I will take a look at this and see how we can avoid this.
Glad it works for you now though 😀
hey @p42webdev Implemented a fix to use our own REST API rather than WP
Please update to 1.3.1 and let me know, it has the fix
Updated, but now I am getting “0 posts loaded.” (in the little helper text below the dropdown on the settings page).
I tried deactivating Solid Security, but it didn’t make any difference. Same “0 posts loaded.” message.
So, for me at least, that is a step backward.
Sorry. Srange. I did some tests and works for me.
Don’t worry, it won’t effect your site unless you save the empty setting
In the console do you get an error?
The problem now is that I can’t set the page at all and the one I set yesterday is now wiped out. 🙁
Checking out the inspector/console. No console errors. I see the call to load the pages (4x) and all are returning a 200 status, but if you check the “response” tab, it is empty.
I tried hitting the URL: https://domain.com/wp-json/wpe/v1/settings/posts?post_type=pages&per_page=100
and get this: {“code”:”rest_forbidden”,”message”:”Sorry, you are not allowed to do that.”,”data”:{“status”:401}}
If I turn off Solid Security and hit the same URL, I get the same error. So maybe another plugin?
Nope. Turned off ALL plugins (except this one of course) and still getting the same response.
does your user role allow you to manage posts? I added in security “manage_posts” and it’s blocking you
Before I release a fix for your case – can you download the file here: https://we.tl/t-3LnE3Tox51
Then upload to: wp-content\plugins\frontend-reset-password\includes\settings\organization\wp-enhanced\rest-endpoints\class-rest-endpoint.php
If it works, Ill release an update
I am the Site Admin, so full permissions.
I uploaded that file. No difference in response (the 401 error). I tried it both with and without the other plugins.
@p42webdev Please do not email the developer access to your site. They will be banned if they accept that.
@peterjabu You need to right now explain that you will not seek login to any user’s site. Please take this serriously.
While I know you have the best of intentions, it’s forum policy that you not ask users for admin or server access. Users on the forums aren’t your customers, they’re your open source collaborators, and requesting that kind of access can put you and them at high risk.
If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.
Thankfully are other ways to get information you need:
You get the idea.
We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It’s actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it’s difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.
When you help users here and in public, you also help the next person with the same problem. They’ll be able to read the debugging and solution and educate themselves. That’s how we get the next generation of developers.
Sorry I was just trying to get this solved as quick as possible. I will not ask for admin logins again. Let me try debug more locally to try replicate this and get a fix
-
This reply was modified 1 day, 13 hours ago by
peterjabu.
@p42webdev and for others interested. We have released a version 1.3.3 that uses ajax call instead of REST which security plugins might block.
Works now
