Create a bilingual archive page with Toolset and WPML. It worked for a while and then it stopped. All the content from the archive view, including filters and pagination is not showing up. Any static text block is working and the Maps block that is connected to the view is also working.
In Gutenberg, the translated page block for the View indicates that the view cannot be found. (see images)
Link to a page where the issue can be seen:
Main page in french (working): hidden link
Secondary language page in english: hidden link
I expected to see:
The translated page content with the same structure as the main language:
- Page Title (working)
- Maps Block (working)
- Archive View Filters (not showing up on translated page)
- Archive results (not showing up on translated page)
- Archive pagination (not showing up on translated page)
Instead, I got:
Empty space where the view content should be:
- Page Title
- Maps Block
Hello. Thank you for contacting the Toolset support.
Thank you for sharing access details, Admin access details you shared is working but I will require admin rights so that I can see all plugins and settings in order to review your current setup.
Can you please send me wp-admin administrator access details. In addition to that when I try to edit the problem URL page, it says me you are editing the current post for now. Can you please stop editing and send me administrator admin access details.
- hidden link
The user shared already has admin rights. If it is not working, please let me know. The menu options on the left have been simplified with Adminimized. I will disable this now so you can have full visual access to the menus and options.
When I go to the page it does say that it is currently being translated, but not that someone is currently editing it. It was 2am here at the time of your message and no one from the team was on the website. If you get this message again, please do what you need to do and take control. It could always be a tab forgotten open. We do have backups of everything so please do not fear to run tests on the website.
We have indeed followed the excellent tutorials from the Toolset website. The view has been translated directly with the page like shown in the video and textual tutorials. This is why we do not understand why the view is now not being recognized.
It seems like it may be in the Toolset or WPML (or Annonce CPT WPML) settings, because when we do a test with a new blank page with only static content blocks and add a view of the custom post type Annonces (Ads in french), the view is never recognized.
As mentioned, please feel free to do all the tests needed as we have beckups on multiple levels and at multiple places. You can also change the main language to english if this helps!
I'm seeing that the its displaying the English translation:
- hidden link
I've added a space and updated the page and send the "Announces" page for translation from:
=> WPML->Translation Management-> Select the page and send it for translation
WPML->Translation and attempt to translate now or if you are using automatic translation it will attempt automatically to translate it again. It seems its translated.
It is possible you have seen an old working version of the page as we had to rollback the website to be able to clone it and continue development while you guys look at the issue.
Please share a screenshot of what you see right now. I still see the empty view (see my shared screenshot).
Sorry about the confusion and the rollback. Of course it had to happen exactly when you were going to take a look at it, haha...
We did manage to get results to show again, which was due to a gutenberg block conflict.
However, now our problem is that static text in a view archive block does not want to be translated. We use a gutenberg heading block (from Kadence blocks) to display if an ad is featured or not and it does work in french (EN VEDETTE) but not in english (should display FEATURED instead of EN VEDETTE). Please see attached images.
All the translation strings that we could find have been translated. Please see attached images.
Same thing for the text "Rafinez votre recherche" in the page.
Thank you. This seems to have done the trick for the accordion block.
How about the P tag in the loop? It seems like "EN VEDETTE" still cannot be translated to "FEATURED". It is a simple P tag using the a Kadence heading. We also tried with the native Toolset Blocks Heading for compatibility and it still doesn't show up.
As mentioned in the previous message, all strings as "EN VEDETTE" have been translated via WPML > String translations.
Also, is there a simpler way to register new strings in a page than to delete the translated page and re-translate it?
I have attached a screenshot of the text on the archive page and in the editor.
By the way, is it normal for Gutenberg to be so slow with nested elements? Because this has been a major pain in creating a fully featured website with Gutenberg editor and we will d efinitely not be using it for complex pages in the future. Every click in teh editor has a 5-20 seconds delay because it's always fetching data by AJAX. Our dev server is huge and ultra-quick.
Is there a way to developing our own PHP views with Toolset? As we could not find any resources on this. If we could create a single card via PHP and show it via the View Loop , it would help us tremendously. We tried shortcodes to display the info but as soon as a filter is updated, the shortcodes displayed data breaks and shows the actual shortcode like [example_shortcode].
For now, the delay is all we can work with it seems as Gutenberg hates having so many nested blocks. Please locate the element via the element tree on the left and be patient once you click on the element. It seems to be the quickest way to be able to make changes.
Yes, you have more complicated structure using blocks and nested blocks. Even you exclude Toolset here, nested blocks will be pain especially with conditional blocks.
I tried to translate simple Advanced text block added by kadence block on my sandbox site and its working just fine. Here is the auto-login link to my sandbox site:
=> hidden link
And here you can see on the following page I've added the "Advanced text" block with text "My text in English":
=> hidden link
If you click on to translate to German, it does display on ATE: hidden link
Our issue is resolved now. Thank you for your support Minesh!
I'm sure part of our issues were due to our limited experience with WPML, which we have learned a ton with your guidance.
In the end, reusable blocks were the culprit, which could be translated by going in our reusable blocks manager (duh...). Which it did not seem easy to find.
