Pro version requesting wrong wp-json URL in ssp-single-admin

Hey @lsaul,

We are not allowed to provide pro support here in the forum.
Please head over to our website and submit a ticket to your account. Thanks! ??

I’ve submitted multiple tickets, but have yet to hear back.

That’s why I posted here.

It has been 2 days.

What email address does simply static support use? So I can be sure nothing is getting filtered out.

• This reply was modified 3 weeks, 4 days ago by lsaul. Reason: asked about email address to check

Please do not mark this resolved until it is.

The fetch is running against the wrong URL throwing errors on the single page process.

In ssp-single-admin.js line 11
fetch('/wp-json/simplystatic/v1/is-running'

That URL is forbidden, and does not check the subdomain.

The URL /wp-json/simplystatic/v1/ is available and accessible.

Was there a version change that modified this code?

I’ve added the URL filter, and it’s still not respecting the config

add_filter( 'ss_origin_url', function ( $url ) {

$url = 'our-domain-url';

return $url;

} );

I think we can improve on that and automate the URL detection further.

However, this is easily solved by setting up WordPress correctly when running it on a subdirectory configuration and has nothing do with Simply Static directly.

If you don’t know how to configure WordPress in a subdirectory (which seems to be the case here), read the docs here: https://developer.www.ads-software.com/advanced-administration/server/wordpress-in-directory/

Also, be aware that you need to tell the WordPress Rest API that your website is running under a different URL: https://www.ads-software.com/support/topic/rest-api-fails-to-load-when-site-is-on-a-subfolder/

I understand bugs are never fun, but you know what isn’t fun either?
Blaming our support while causing the problem yourself and leaving a one-star review.

I’m closing this ticket now.

Update:

In the next update, we will get the Rest API URL via get_rest_url() and pass it directly to the script to avoid these problems in the future (even if you haven’t configured WP correctly to work in a subdirectory).

Depending on the context (Single/Build export), the Ajax variable differs, but the general idea is shown in the code below:

 fetch(sspb_ajax.rest_url + 'simplystatic/v1/is-running',
        {
            credentials: 'same-origin',
            headers: {
                "Content-Type": "application/json",
                'X-WP-Nonce' : sspb_ajax.rest_nonce
            },
        }

Great, thanks! That is genuinely helpful.
It’s unfortunate that I had to leave a negative review to get such a thoughtful support response though. Which was not my intention.

I work with this plug-in on a near daily basis, and it’s used for important work. You have to understand how frustrating that is when it doesn’t work.

I was able to get the plugin to work again after restoring from backup, so there was probably an update that got through somewhere that caused publishing to fail. I still have to figure out what happened. The issue addressed does not seem to be the root cause, because publishes still work even though I’m still seeing the error FYI.

Regardless, it’s probably a good thing to correct. Glad you were able to address it.

• This reply was modified 2 weeks, 6 days ago by lsaul.

Hey @lsaul,

thanks for your follow-up!

I understand your frustration, and that’s why we are working under high pressure to fix and release all of your reported bugs (the RC is ready; we are stress-testing it).

We can also send it to you, but it seems none of our e-mails reach you or your colleagues (all of our replies are sent via [email protected]).

Feel free to use our email to follow up (maybe use a different email to reply than the company one).

I’m also working on getting my response to your review edited and the personal details removed.

Thanks for your understanding. I’ll have to connect with our IT team to see what might be going on with the emails possibly being filtered out.

I’ll be sure to update my review, and I apologize if it was more negative than intended. I was frustrated and working under pressure which may have inadvertently come out in what I expressed.

The plugin normally works great, there have just been a few times where it stopped. It becomes challenging when I have to work through getting it going again with other work going on. That’s all.

Thanks again.

Hey @lsaul,

we just published the official release now: https://simplystatic.com/changelogs

It should include everything you’ve mentioned, specifically:

• dynamic endpoints for Builds and Single export triggers (to get the correct Rest API endpoint)
• remove headers from the debug log when using GitHub integration (to avoid leaking the token)
• refactored GitHub integration (task splitting, better error handling) (to get the deployment issue fixed)

I recommend updating the free version as well to clear all the outstanding transients (we now use plain options to avoid issues with object caching).

I haven’t made progress updating my reply to your review (yet)—for some reason, I’m no longer able to edit it, but I’m in touch with a moderator to get that sorted.

Hi Patrick – thanks for updating me. I’m checking back on this so I can update my review. Glad to change the review, will update as soon as I can. Really sorry about the misunderstanding.