Kadai Crosshansen

Yeah, after investigating I have found that probably that is the cause of the error/problem. So, it is Stripe and not the plugin.

None the less, we were able to fix the issue reverting the options of the plugin to a previous working state (thanks to a backup).

Thanks and have a nice day.

hehe, yeah, glad it helped!

Well, it is going to be a bit tricky to change the fonts for the theme, but it is doable.

First of all you need to create a child theme and then, on the functions.php file of the child theme, define a new lovecraft_load_style function, where you define what you need.

Usually you need to copy and paste the code and change where it says ‘//fonts.googleapis.com/css?family=Lato:400,700,900|Playfair+Display:400,700,400italic’ to what you need.

But that is just the first step, as then you need to search in the style.css file for all the definitions that have the font-family rule. Then copy all of them into the child style.css file and change the rule to reflect the fonts you want and where.

Can be tricky, but is doable.

I can confirm this bug with Gutenberg Examples and the RC of WordPress 5.

To make it happen, you need to have “turned off” the Gutenberg development plugin. Since WP5 is bringing it in, makes sense to turn off the development plugin.

None the less, the function “wp_get_jed_locale_data”, what should have been added to core as stated here, is not present in core (or maybe it with another name).

To prevent the error, one needs to activate the Gutenberg plugin. Or either copy the “gutenberg_get_jed_locale_data” function with a function_exists check.

While it is then added back.

This is a real issue.

I have had the same problem on my VPS, and eventually had to use the “–skip-plugins” flag on it to be able to run the commands properly. It deactivates all your plugins.

Instead, if you just want to deactivate Swift Performance, you can use “–skip-plugins=swift-performance-lite” and it will not be loaded for the cli.

None the less, this issue needs to be properly fixed.

I can confirm that the new version does indeed includes some issues and even fatal errors.

Some of my development sites die with this:

Fatal error: Uncaught RuntimeException: The gmp or bcmath extension must be installed to read this database. in /www/data/public_html/wp-content/plugins/wordfence/vendor/maxmind-db/reader/src/MaxMind/Db/Reader/Decoder.php:259
Stack trace:
#0 /www/data/public_html/wp-content/plugins/wordfence/vendor/maxmind-db/reader/src/MaxMind/Db/Reader/Decoder.php(129): MaxMind\Db\Reader\Decoder->decodeBigUint(‘[j)\x82’, 4)
#1 /www/data/public_html/wp-content/plugins/wordfence/vendor/maxmind-db/reader/src/MaxMind/Db/Reader/Decoder.php(93): MaxMind\Db\Reader\Decoder->decodeByType(‘uint64’, 3465515, 4)
#2 /www/data/public_html/wp-content/plugins/wordfence/vendor/maxmind-db/reader/src/MaxMind/Db/Reader/Decoder.php(193): MaxMind\Db\Reader\Decoder->decode(3465515)
#3 /www/data/public_html/wp-content/plugins/wordfence/vendor/maxmind-db/reader/src/MaxMind/Db/Reader/Decoder.php(100): MaxMind\Db\Reader\Decoder->decodeMap(9, 3465513)
#4 /www/data/public_html/wp-content/plugins/wordfence/vendor/maxmind-db/reader/src/MaxMind in /www/data/public_html/wp-content/plugins/wordfence/vendor/maxmind-db/reader/src/MaxMind/Db/Reader/Decoder.php on line 259

I never had this error before. Just appeared in this update.

Also, it appears sometimes. Even on sites that did had this update a few hours already.

I confirm this is working as expected now.

Thanks for the fix.

@andreeaw: better to wait for the next version (1.23) before update. As I am unsure if this might happen on any other environment (This was present on the version of PHP I use, but maybe not in the one that the developer has)

So, is better to have a word from Anders about this before updating (specially if the website its important or production one)

EDIT: Nevermind, there is the answer. Thank you Anders.

• This reply was modified 6 years, 10 months ago by Kadai Crosshansen.

Look here: https://themes.trac.www.ads-software.com/changeset?old_path=%2Flovecraft%2F1.21%2Fcomments.php&old=86930&new_path=%2Flovecraft%2F1.22%2Fcomments.php&new=91741&sfp_email=&sfph_mail=

On lines 139-140 (past version) and lines 148-149. Apparently the version of PHP I am using on a server (PHP 7.0.28) just complained at the way the parentheses and colon where written there.

Needed to revert the closing parentheses as how it is on the lines 139-140 to make the script run without issues.

Continuation:

I believed first that this may have been caused by the child theme customizations I have done to your theme, but it is not.

Tried it on a test install I have and the same error appeared there. With a unmodified version of the lovecraft theme. Still can’t figure out what is wrong exactly.

Anders, there is an error in the last released version.

I have just updated and started to get the next message:
PHP Parse error: syntax error, unexpected ‘)’ in /home/—/public_html/wp-content/themes/lovecraft/comments.php on line 149

I have quickly checked the file and there is a double closure for an array and apply_filters… but no idea if the error actually happens way above.

For clarification on this issue… currently, you can have one language for the website and another one for your “user account”.

The language that is set in Settings > General > Site Language will affect the front-end and any person that registers to the website.

But administrators can change the language of its admin pages at Users > Your Profile (or Edit my Profile). This change will not modify the language that is shown at the front-end.

This plugin works perfectly and may have its uses… but right now it seems that it is a bit redundant.

Try to clear your cache, as for now it may be the cause of the problem… but need more people to confirm this.

In my case, I cleared several layers of cache files (example CloudFlare and browser cache) and the 404 log page started to, somewhat, working for deletion attempts. But it sometimes works and others did not.

If this is not an option for you, I recommend to rollback to version 2.6.3, as it is more likely to work fine for you.