zakoops

Hi,

You should find a screenshot here for that visual glitch.

Please note that this behaviour occurs on any block whatever its source, Otter or not.

Thanks for looking into this matter!

Thanks for looking into it!

Hello,

Any development in the past 4 months regarding the possibility of being able to translate this text?

• This reply was modified 4 years, 6 months ago by zakoops.

I’m using XAMPP 7.2.12 (Rev. 0) on a Mac desktop using macOS Catalina 10.15.4 (19E287).

Still, I’m actually looking for your local setup (Local By Flywheel) that I did not know!

I’m closing as Resolved as it is not that important.

Thanks for you reply.

Hi,

Thanks for your reply!

I created a page in WordPress, imagining it was a post, and then used each of the 4 settings (page templates) available in Twentig. And then I realize, like you, that these settings are effectively best used in a page setting, instead of a post. From a distance, it felt like a missed opportunity to support only pages (and not posts…)!

Thanks again for making me realize your point of view.

Regards,

Hello Anthony,

Thanks for the follow-up! Will check on github…

Regards,

zakoops

Hi,

Thanks for your reply!

Your answer seems to suggest that the problem I refer to manifests as soon as I click on the “Clear” button. But no error is shown here as a result of that action and I’m afraid I was not sufficiently explicit…

Detailed steps to reproduce the problem, just to be sure:

1. I insert an AB Container block with nothing inside (apart from the empty default Paragraph block).
2. I then click the Clear button as mentioned before (background-color was the default #fff and now that property is gone from the inline style attribute).
3. I then update (publish) the post. No error has been shown yet.
4. I go back to the dashboard (meaning, I quit the Gutenberg editor).
5. Then I go back to the Gutenberg editor, to modify or review my post.
6. And then, not before, I see the message “This block has been modified externally.”

If I select a solid background color or an image for the AB Container block (instead of clearing the background) and that I repeat the six steps above, I never encounter such problem —hence my suspicion about that small Clear button. But that could well be an issue with Gutenberg itself as mentioned in your message…

If needed, I can provide a screenshot of the Chrome console on your github repo as it seems we can’t post images here…

I’m taking the opportunity to thank you for that fine set of additional blocks.

JoomUnited deserves kudos for this prompt reply and plugin update.

Many thanks!

This feature is an absolute requirement that must be on your priority list, that’s for sure.

On our website, we will always have visitors and potential clients from any part in the world.

Hope that this feature appears real soon in the plugin.

Thanks!

Yeah, version 2.0.9 solved the problem on my site.

Thanks Chouby!

Got exactly the same problem…

As Christos is saying at the top of this thread, I also see a javascript error in /polylang/js/post.min.js

Thanks for looking into this problem!

Hi Jeremy,

I thank you for your reply —quite comprehensive for context and possible solutions.

I decided for the alternate solution. Therefore I grabbed Sublime Text and extended Jetpack’s default list of tags in functions.php file, as you have proposed (in a child theme though).

And this works perfectly!

So thanks again!

For the sake of completeness following my previous post, I want to let know that I’ve been able to resolve my problems of WordPress not updating the core files, themes and plugins.

And it’s something that was at the antipode of anything I could have suspected. I posted my solution here in a new thread of the WordPress Localhost Installs forum.

For the sake of completeness following my previous post, I want to let know that I’ve been able to resolve my problems of WordPress not updating the core files, themes and plugins.

And it’s something that was at the antipode of anything I could have suspected. I posted my solution here in a new thread of the WordPress Localhost Installs forum.

Hi,

@patriksmith

On Mac OSX 10.11.3, I had an old XAMPP installation that I deleted —only because I had problems updating WP and plugins.

So, after 2 days of work, I have finally installed this brand new version of XAMPP. Exactly the same one as yours:

– XAMPP 7.0.2 (Apache 2.4.18, PHP 7.0.2 with MariaDB)
– OpenSSL 1.0.2f (but ‘openssl version’ in Terminal gives ‘OpenSSL 0.9.8zg’)
– WP 4.4.2

On a fresh installation of WP and no plugins or themes except Twenty Sixteen, I was somewhat stunned to find out that these updating problems are still there, as if these 2 days of work were just a waste of time. Like you, the front end runs smoothly.

At the time of the old XAMPP installation, I underlined the problem I had in this thread, some 3 weeks ago. In that thread, James Huff (WordPress Volunteer Moderator) said that WordPress is going to need at least OpenSSL 1.0 and pointed to another thread for solution (found here) for OS X 10.11.x. I read the whole thread as well as the step-by-step procedure by Micheal Fraase available here.

But Mr. Fraase has El Capitan/Server 5.0.15 which is not quite like having simple XAMPP on plain vanilla El Capitan installation (not sure here). Furthermore, if I were to go that route, I would have to install Homebrew and run a batch of esoteric commands to install another set of cURL and PHP modules —and not too sure if I could break the integrated security of OSX doing so.

Frankly, I have to admit being first a writer that likes having a nice site (hence that test bed in localhost). So I’m not confortable with the road proposed here.

In the end, is there any localhost solution (XAMPP or otherwise) that is able to run WordPress without updating problems on OSX El Capitan?

If not, I would consider a flat-file system like grav, or go directly with an hosted solution on wordpress.com.

Thanks in advance for any input!