patrickposner
Forum Replies Created
-
Hey @streettb,
thanks for reaching out!
It’s because of your old WordPress version – Passster needs at least WP 6.5 to run because of the depency upgrades in WP (major version upgrade of React).
Forum: Plugins
In reply to: [Passster - Password Protect Pages and Content] Padding left issueHey @luislu,
this is fixed now in 4.2.7! π
Forum: Plugins
In reply to: [Passster - Password Protect Pages and Content] Schedule Password ChangesForum: Plugins
In reply to: [Simply Static - The Static Site Generator] fuse search without auto complete@oferlaor not yet.
We have planned to add that, including:
- using the default search template of your theme for the results
- handle the search requests via URL and parse them with JS
- Offer a customizable (and embeddable) result block/shortcode
This would allow you to either use both on the same page but have more control over the results or use a dedicated results page.
I can’t really tell you when this will be available, but it’s definitely planned π
Forum: Plugins
In reply to: [Simply Static - The Static Site Generator] cleanup errorUpdate published!
Forum: Plugins
In reply to: [Simply Static - The Static Site Generator] cleanup errorHey @oferlaor,
thanks for reaching out!
Please update to the latest version of Simply Static Pro (1.6.3.1), and you should be able to run the export without any problems.
I will push a quick update for the free version in a second to avoid the error, but we deprecated the function mentioned.
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.
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.
Forum: Plugins
In reply to: [Simply Static - The Static Site Generator] simply_static_page issuesHey @fliespl,
thanks for your suggestion!
We used the URL parameter instead of a custom header for a couple of reasons:
Cache Busting:
A significant portion of our user base uses shared hosting plans, and what’s even worse is that they use Litespeed instead of Apache/NGINX.
The problem is that you can’t bypass the cache with a custom header here, which has resulted in hundreds of complaints that the static site isn’t updating at all.
The URL parameter solves as a mechanism to prevent that.
Wrong usage of Custom Headers:
We noticed that many plugins use custom headers for things like license validation, but most of them simply overwrite the existing headers passed via the http_request_args filter we are using internally.
That’s why we opted to use the query string instead of custom headers.
However, I could see this being offered as an alternative via filter.
Our development is happening publicly on GitHub, so feel free to provide a PR with your suggested changes, and we will review and merge it: https://github.com/Simply-Static/simply-static
Cheers,
PatrickUpdate:
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
},
}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.ww.wp.xz.cn/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://ww.wp.xz.cn/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.Hey @lsaul,
thanks for your review and your feedback!
I just want to clarify some of your obvious lies here so that others will not believe your made-up arguments.
- You asked for pro support but never reached out to us via the appropriate channel
- You don’t own the license at all, so it’s even harder for us to connect the communication (globalgiving.org is the license holder).
- We haven’t marked the issue as closed after you opened it again. However, pro-support requests tend to be deleted by the w.org moderators, so it makes no sense to have the discussion there.
I’m glad you found an alternative. Simply Static might be a bit above your technical skill level, which is fine, as we target developers.
EDIT:
I just found the tickets (and we replied to all of them).
I will follow up with Justin Rupp and offer a review of your implementation – I’m sure we can fix it for them in minutes.I will also talk to them about your behavior and work ethos – I think it’s good to manage the expectations here – I know it’s easy to blame the tools as a freelancer, but that’s just not how it works.
- This reply was modified 1 year, 7 months ago by Yui.
- This reply was modified 1 year, 7 months ago by patrickposner.
Forum: Plugins
In reply to: [Simply Static - The Static Site Generator] .php files won’t copy in 3.2.0Hey @sasharp,
thanks for the report!
We are indeed automatically excluding all files with the PHP extension now.
There shouldn’t be a reason to have them on your static site, but there are always exceptions.That’s why we added a filter to the plugin to reenable it:
add_filter( 'ss_excluded_by_default', function ( $excludes ) {
unset( $excludes['.php'] );
return $excludes;
} );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! πHey @jainarun,
thanks for your report!
That’s one of the reasons we recommend LocalWP or Lando instead of MAMP: https://docs.simplystatic.com/article/56-how-to-fix-problems-with-your-local-development-tool
You might have a good reason for using MAMP, so if you want to use it, you need to find a solution to make WP-Cron work on it.
There are a couple of posts about that:
https://stackoverflow.com/questions/19815317/setting-up-a-cronjob-on-mamp-infintewp