it’s the same code with a major change in one of the lines, in order to support other post status like draft, private and so on.
it’s working fine here, either for regular and custom posts, either published, future or whatever, logged or not.
i need to look at the line more closely. are you sure you didn’t test with the snipet and the plugin altoguether? it might be messy if both functions are running in parallel.
hi joelle,
please update to v1.35.
make sure:
1. to remove that snipet before testing.
2. clear your browser’s cache before reload. or do a hard refresh.
then report to me. hope it’s fixed. 8-|
Thread Starter
Joelle
(@joelle)
Hello! Sorry so quiet, been super busy. π
I was able to get the permalinks to load without the additional snippet or any additional plugin, so we’re good to go there.
Thank you so much for all the improvements.
great! i’m very happy everything goes well now.
JdA
Thread Starter
Joelle
(@joelle)
Alas…
Plugin could not be activated because it triggered a fatal error.
Parse error: syntax error, unexpected '[' in /home/cassiecl/public_html/wp-content/plugins/the-future-posts/includes/main.php on line 404
can you tell me which version of PHP is installed?
joelle, please tell me the PHP versions on both Glynn and on this new site you’re trying to install.
and both versions of WordPress too.
thanks.
p.s.: i think the problem is related either to PHP or WP versions.
Thread Starter
Joelle
(@joelle)
Both clients are using WP 4.9.8.
the one where I get the error is using PHP version: 5.6.30
the one where it works (glynn) is PHP version: 7.0.30
are you sure it’s v5.6.30?
i cannot test it with such version, but i tested it with prior versions and things worked fine. see bellow.
so, update PHP to v7.x and i think you will be fine.
= 1.37 – 2018-08-07 =
* The sintax error on main.php line 390 seems to be a PHP problem afterall. Not a code bug. I successfully tested it with PHP v5.4.45, v5.5.38, v5.6.20, v7.0.3, v7.1.4 and v7.2.0. I unsuccessfully tested it with v5.2.4, v5.2.17 and v5.3.29. Furthermore, a customer reported the problem with PHP v5.6.30. Solution: update PHP to a more recent version like v7.0.3 and hopefully the problem should disapear.
Thread Starter
Joelle
(@joelle)
I put in a ticket with my host to move it to a server with 7. I’ll report back when it’s done. π
Thread Starter
Joelle
(@joelle)
YASSSS! It activated without a hitch. π Perfecto!