Nopalot

Hi Robin,

thanks for the clarification.

It would be useful if GibeWP could handle multilingual forms without the use of yet another third party plugin. Especially if you consider the premium price of up to $499/year – a price, at which most users expect a flawless solution. None the less, GiveWP is a nice plugin. The fundamental problem here is that WordPress is just a bad choice for international sites. But anyway, thanks for your help.

Congratulations on the release of version 5.0. Looks very nice now!

So…,

There’s this big white “Back to WordPress Editor” button at the top of the page. It takes the Elementor post/page and gets it into Gutenberg. Somehow I managed to overlook it though.

Excuse me. Thanks for your help!

• This reply was modified 3 years, 9 months ago by Nopalot.

Interesting that the content remains, that could save a lot of work. Thanks for sharing this. I haven’t tried to disable Elementor completely, as it would cause way too much damage.

The problem is that Gutenberg is inaccessible if the Elementor Plugins are running. I.e. the white box containing the blue “Edit with Elementor” button is covering/blocking any access to Gutenberg. I’m looking for a way to get rid of the box. Ideally without completely disabling Elementor.

Any ideas how to make Gutenberg accessible again are welcome.
Thank you.

Interesting: At https://developers.google.com/search/docs/data-types/faqpage#guidelines it says:

All FAQ content must be visible to the user on the source page.

I’d rather have the same content on page and in the header.

Thank you for taking a look at this issue.

Disabling Bogo fixed the error in Elementor. Unfortunately I can’t provide any further information because the site is now running on a different plugin. Feel free to close this case.

Again, thank you,
Michael.

Elementor shows an error and is unable to edit/open a page if the page is a child page that’s in a locale other than the sites default language. As a response to that error, WordPress sends a “Your Site is Experiencing a Technical Issue” email, which contains the following stack trace:

Error Details
=============
An error of type E_ERROR was caused in line 1933 of the file /usr/www/users/breathyi/wp-content/plugins/elementor/includes/base/controls-stack.php. Error message: Uncaught TypeError: Argument 1 passed to Elementor\Controls_Stack::sanitize_settings() must be of the type array, string given, called in /usr/www/users/breathyi/wp-content/plugins/elementor/includes/base/controls-stack.php on line 1022 and defined in /usr/www/users/breathyi/wp-content/plugins/elementor/includes/base/controls-stack.php:1933
Stack trace:
#0 /usr/www/users/breathyi/wp-content/plugins/elementor/includes/base/controls-stack.php(1022): Elementor\Controls_Stack->sanitize_settings(‘d:1:{s:10:”hide…’)
#1 /usr/www/users/breathyi/wp-content/plugins/elementor/includes/base/controls-stack.php(1775): Elementor\Controls_Stack->get_data(‘settings’)
#2 /usr/www/users/breathyi/wp-content/plugins/elementor/core/base/base-object.php(132): Elementor\Controls_Stack->get_init_settings()
#3 /usr/www/users/breathyi/wp-content/plugins/elementor/core/base/base-object.php(40): Elementor\Core\Base\Base_Object->ensure_settings()
#4 /usr/www/users/breathyi/wp-content/plugins/elementor/core/settings/manager.php(140): Ele

Elementors support team looked at the issue first and discovered that it’s related to Bogo. After asking for some details they’ve provided the aforementioned quote.

Here are some more details that the Elementor support kindly shared:

The error that you receive means that the styles have not been loaded properly (on child pages).

The code refers to this
protected function get_css_file_name() {return ‘post’; } so the developer of Bogo will know where to look at in his code.

Domo arigatou gozaimasu!

Switching to the classic editor is a viable workaround to make the parent page assignable again. Thank you very much for sharing this!

However, there’s one more strange thing that happens on both, the block and the classic editor:
The site uses Elementor page builder with English as the default language. All English pages in the hierarchy can be opened and edited in Elementor. But as soon as a translation is created for a page that has a parent assigned, Elementor can’t edit the translated page and just displays an error message instead. I’ll get in touch with Elementors support to see if we can sort this issue out.

Bogo is a pretty awesome plugin btw! It’s small and it does just the one thing that’s required for a multilingual plugin, it’s the perfect solution imho. Thank you very much for providing it!

Thank you very much for the quick reply!

Sumimasen,
There seems to be something broken when setting the parent of a localized page. I just freshly installed WordPress 5.2.2 and Bogo 3.2.1 – no other plugins or themes are installed.
Default language on the site is English, German has been added as a second Language.
Here are the steps to reproduce the problem:

1. Create a new page “Parent EN” and publish it.
2. Create a new page “Child EN”. Set “Parent Page” to “Parent EN” and publish it.
3. Edit page “Parent EN” and push the “Add Translation” button. This will add a link “Parent EN [German]” under Translations. Click the link to edit the page.
4. We’re now on the German page: Change the title to “Parent DE” and the URL Slug (from “parent-en”) to “parent-de” and publish the page
5. Edit page “Child EN” and push the “Add Translation” button. This will add a link “Child EN [German]” under Translations. Click the link to edit the page.
6. Change title to “Child DE” and URL Slug to “child-de” and publish the page.
7. Now, when you edit the “Childe DE” page again you’ll see the proper url under preview. (which is …/de/parent-de/child-de/). However, under “Page Attributes” -> “Parent Page:” there’s “(no parent)” selected. Opening the dropdown box shows the options “Parent EN” and “Child EN”. In other words, only an English Page can be set as a parent of the German page.

   And here is where it’s getting strange: When you return to the list of Pages (“All Pages” on the left sidebar), you’ll see “Child DE” as a child of “Parent DE”. Which is as it’s supposed to be. However editing “Child DE” still shows “(no parent)” under “Parent Page” and only English pages can be assigned.

Do you have any ideas how to fix or workaround this? I.e. How to assign a German parent to a German page?

Domo arigatou gozaimasu!

• This reply was modified 5 years, 8 months ago by Nopalot. Reason: My Japanese is *unfortunately* really bad
• This reply was modified 5 years, 8 months ago by Nopalot. Reason: Some more clarifications added

Ah, sorry, I didn’t get the membership concept. I’ve updated the rating. Thanks for the quick response.

I see your point…

Once you have 20+ plugins installed, your WordPress menu becomes pretty messy. At this point you start to appreciate plugins that spare you from their own top level menu. Especially if they are plugins with which you rarely (if ever) interact – which is the case for Premium Addons for Elementor.
Also, considering the fact that the plugin can’t be used without Elementor, makes it even more a candidate to add it as a child of Elementor’s menu.
Well, that’s just my personal opinion.

Anyway, thank you for providing the plugin. The components look very nice!

Thank you!

Hello David,

Thank you very much for your help!

The goal is to have a clickable list of the image’s tags shown somewhere close to the image. A “previous/next” link would be very nice as well, but is not important at the moment.

I’ll give the attachment page approach a try. This should be a manageable task, thanks to your detailed explanation in the link.

Again, thank you,
Michael.

@esmi, thanks for the clarification. Using

<ol>
<li><h2>Headline1</h2></li>
<li><h2>Headline2</h2></li>
</ol>

Makes the numbers at the left side of the headlines look different than the headlines. I was trying to get the same style for both, the headlines and the numbers.

I’ll try Pete’s approach next.

Thank you!