Zum Inhalt springen Zur Seitenleiste springen

Startseite › Support › Unterstützung in Deutsch › [Gelöst] Greenshift 7.9 incompatible with WPML

[Gelöst] Greenshift 7.9 incompatible with WPML

Dieses Thema ist gelöst. Hier finden Sie eine Beschreibung des Problems und der Lösung.

Problem:
The client is experiencing an issue where the custom meta field "_gspb_post_css" is not always copied when a page is updated using WPML and Greenshift. The client has manually created an ACF Field with the ID "_gspb_post_css" and set it to copy as a temporary solution.
Solution:
We recommend setting up a staging site to test this issue in isolation with only WPML and Greenshift installed. Additionally, we suggest increasing the WordPress memory limit. To do this, add the following code to the wp-config.php file:

define('WP_MEMORY_LIMIT', '256M');

Place this line just before the "That's all, stop editing! Happy blogging." comment. For more information, please refer to our minimum requirements documentation.

If this solution does not seem relevant to your situation, please open a new support ticket in our WPML support forum.

Dies ist das technische Support-Forum für WPML – das mehrsprachige WordPress-Plugin.

Mitlesen können alle, doch nur WPML-Kunden können hier Fragen veröffentlichen. Das WPML-Team antwortet im Forum an 6 Tagen pro Woche, 22 Stunden am Tag.

Schlagwörter: 

Dieses Thema enthält 3 Antworten, hat 3 voices.

Zuletzt aktualisiert von Marcel Vor 1 Jahr, 9 Monaten.

Assistiert von: Marcel.

Autor Beiträge
Januar 23, 2024 um 11:37 a.m. #15216041

martinS-187

Hey,

i have installed the latest version of WPML and Greenshift and when a page gets translated it doesn't copy always when the page gets updated the required meta field "_gspb_post_css".

More information are also available in the following Facebook post:
versteckter Link

I created now manually a ACF Field with the id "_gspb_post_css" and set it to copy. This works for now but would be nice to have this fixed the right way.

Greenshift already has a wpml-config.xml:
line thats interesting:
<custom-field action="copy">_gspb_post_css</custom-field>

<wpml-config>
        <gutenberg-blocks>
                <gutenberg-block type="greenshift-blocks/heading" translate="1" label="Advanced heading">
                        <xpath>//*[contains(@class, 'gspb_heading')]</xpath>
                        <key name="title" />
                        <key name="text" />
                        <key name="textbefore" />
                        <key name="textafter" />
                        <key name="headingContent" />
                        <key name="customAnchor" />
                        <key name="subTitle" />
                        <key name="animatedText">
                                <key name="*" />
                        </key>
                </gutenberg-block>
                <gutenberg-block
                        type="greenshift-blocks/text" translate="1" label="Advanced text">
                        <xpath>//*[contains(@class, 'gspb_text')]</xpath>
                        <key name="text" />
                        <key name="textContent" />
                        <key name="customAnchor" />
                </gutenberg-block>
                <gutenberg-block
                        type="greenshift-blocks/button" translate="1" label="Advanced Button">
                        <xpath>//*[contains(@class, 'gspb_button_wrapper')]</xpath>
                        <key name="buttonContent" />
                        <key name="label" />
                        <key name="buttonLink" />
                        <key name="customAnchor" />
                        <key name="closeLabel" />
                        <key name="openLabel" />
                </gutenberg-block>
                <gutenberg-block
                        type="greenshift-blocks/buttonbox" translate="1" label="Advanced Button">
                        <xpath>//*[contains(@class, 'gspb_button_wrapper')]</xpath>
                        <key name="buttonContent" />
                        <key name="label" />
                        <key name="buttonLink" />
                        <key name="customAnchor" />
                        <key name="closeLabel" />
                        <key name="openLabel" />
                </gutenberg-block>
                <gutenberg-block
                        type="greenshift-blocks/iconlist" translate="1" label="Advanced List">
                        <xpath>//*[contains(@class, 'gspb_iconsList')]</xpath>
                        <key name="iconsList">
                                <key name="*">
                                        <key name="content" />
                                </key>
                        </key>
                </gutenberg-block>

                <gutenberg-block
                        type="greenshift-blocks/accordionitem" translate="1">
                        <xpath>//*[contains(@class, 'gs-accordion-item__heading')]</xpath>
                        <key name="title" />
                </gutenberg-block>

                <gutenberg-block
                        type="greenshift-blocks/tabs" translate="1">
                        <xpath>//*[contains(@class, 'tabtitlelabel')]</xpath>
                        <key name="tabTitles">
                                <key name="title" />
                                <key name="subtitle" />
                        </key>
                </gutenberg-block>

                <gutenberg-block
                        type="greenshift-blocks/progressbar" translate="1">
                        <key name="title" />
                </gutenberg-block>

                <gutenberg-block type="greenshift-blocks/counter" translate="1" label="Counter">
                        <xpath>//*[contains(@class, 'wp-block-greenshift-blocks-counter')]</xpath>
                        <key name="label" />
                </gutenberg-block>

                <gutenberg-block type="greenshift-blocks/countdown" translate="1" label="Countdown">
                        <xpath>//*[contains(@class, 'gs-countdown')]</xpath>
                        <key name="labelDay" />
                        <key name="labelHour" />
                        <key name="labelMin" />
                        <key name="labelSec" />
                </gutenberg-block>

                <gutenberg-block type="greenshift-blocks/social-share" translate="1" label="SocialLables">
                        <key name="socialLabels" >
                                <key name="fb" />
                                <key name="tw" />
                                <key name="pn" />
                                <key name="wa" />
                                <key name="tg" />
                                <key name="in" />
                                <key name="email" />
                        </key>
                </gutenberg-block>

        </gutenberg-blocks>
        <custom-fields>
                <custom-field action="copy">_gspb_post_css</custom-field>
        </custom-fields>
</wpml-config>

So it looks like its a problem from WPML?!
Januar 23, 2024 um 5:51 p.m. #15218491

Diego Pereira

Hi there, welcome to the WPML support Forum!

While you are waiting for one of my colleagues to take this ticket and work on it, let me provide you with first debugging steps or if I can perhaps help with the issue quickly.

This seems to be a new compatibility issue. In these cases, these are the procedures:
- Install the plugin in a clean installation and reproduce the problem in this new installation. So we can isolate it and do some testing without the interference of server settings or other plugins
- After this, we will check the problem in this new installation and look for a quick solution
- If we can not find a solution, we will forward the problem to our compatibility team
- The compatibility team will do some more testing and will contact the product author to fix the issue

I created a test website with a clean WordPress install. You can access it through this link: versteckter Link - Through this link you will be automatically logged in.

Please upload the plugin to this test install, setup it the same way as in your website (using the same options) and create some dummy content to reproduce the issue. Please note that we only need the plugin and the related functionality, you don't need to setup a entire website or clone your existing site.

After that, please send us clear steps on how to see/reproduce the issue on this test install. We will run some tests.
Januar 23, 2024 um 7:35 p.m. #15218675

martinS-187

I can not reproduce the bug on the sandbox, however i saw in the commits, that the config has been updated 4 weeks ago with the fix:
https://plugins.trac.wordpress.org/changeset/3014156/greenshift-animation-and-page-builder-blocks/trunk/wpml-config.xml

Is there something in wpml cached that it doesnt't work on our page and on the sandbox it works because its all fresh new?
Januar 24, 2024 um 8:36 a.m. #15220161

Marcel
Unterstützer

Sprachen: Englisch (English ) Spanisch (Español ) Deutsch (Deutsch )

Zeitzone: Europe/Madrid (GMT+02:00)

Hallo,

nicht wirklich. Nur die populärsten Plugins bekommen die XML-Config über unser eigenes GitHub bzw. werden dort zentral verwaltet. In diesem Fall kommt alles von den Autoren selbst.

Ggf. greift ein 3rd Party Code hier ein. Setzen Sie am besten eine Staging Seite auf und testen Sie dies dort isoliert nur mit WPML und Greenshift in den identischen Versionen.

Könnten Sie bitte ebenso Ihr WP-Speicherlimit erhöhen? Fügen Sie diesen Code in Ihre wp-config.php ein, um den WP-Speicher zu erhöhen:

define('WP_MEMORY_LIMIT', '256M');

Fügen Sie ihn kurz vor "That's all, stop editing! Happy blogging." ein.

Weitere Informationen finden Sie hier: https://wpml.org/home/minimum-requirements/
Hinweis: WPML benötigt ein WP-Speicherlimit von mindestens 128MB alleine. Dies bedeutet mit einem Standard-Theme und ohne weitere installierten Plugins.

Freundliche Grüße
Marcel