I want to display the full-size featured image on desktop and a smaller size (medium or thumbnail) on mobile devices. However, there is no built-in way to modify the [wpv-post-featured-image] shortcode to serve different image sizes based on screen size.
Solution:
Use two instances of the shortcode: one for desktop and one for mobile. Wrap each instance in a DIV with specific CSS classes, then apply CSS media queries to show or hide them based on screen width. The hidden image will not significantly affect performance due to modern browser optimization.
The content on the blog archive page is not fully translated. A slider added to the archive template appears correctly in the default language (Spanish), but in other languages (e.g., English), a different slider from another plugin is shown. The archive pages sometimes show French as the default language instead of Spanish, indicating a potential conflict between WPML and Toolset.
Solution:
The customer discovered that the plugin "Post Types Order" by Nsp Code was causing the issue. This plugin created different template versions for each language and changed the default language of existing templates.
Deactivating and reactivating plugins one by one helped identify the culprit.
The customer removed the "Post Types Order" plugin, which resolved the issue.
I have created a custom template for my posts archive page, and the first post in the grid has no title. Switching from a dynamic heading to a dynamic field shows the title initially, but it disappears after some time.
Solution:
Inspect the markup of the page and find that the heading link has no text. Changing the theme from Child The,e to GeneratePress resolves the issue, indicating a possible JavaScript code problem in the Raypa theme. Contact the theme developer for further assistance.
Problem:
The user needed to change the slug of an archive page from "autoclave-comparator" to "comparador-de-autoclaves" and later wanted to translate this slug into multiple languages using WPML. However, she faced difficulties in finding the setting to change the slug and translating it for different language versions. Solution:
We instructed them to change the slug by editing the custom post type in Toolset under the Rewrite settings. Later, when they wanted to translate the archive slug for different languages, we explained that WPML only allows the archive slug to be translatable if it matches the 'rewrite['slug']' or the custom post type name slug. This means the archive slug must be the same as the slug for single posts or the post type name for it to be translatable in WPML. Relevant Documentation: https://wpml.org/documentation/support/translating-slugs-for-custom-post-type-archives/
Wir dokumentieren bekannte Probleme und ihre Lösungen in Toolset-Fehlerverzeichnissen. Sparen Sie Zeit, indem Sie zuerst dort nachsehen, ob der bei Ihnen auftretende Fehler bereits bekannt ist. Die Liste wird kurz gehalten. Wir tun unser Bestes, um bei jeder Veröffentlichung von Toolset-Plugins alle bekannten Probleme zu lösen.
Support-Richtlinie
Das Toolset-Team hilft Ihnen, die Toolset-Plugins richtig zu benutzen, liefert Ihnen alle nötigen Informationen, unterstützt Sie bei der Lösung von Problemen und gibt Ihnen Tipps zu Best Practices.
Bitte stellen Sie sicher, dass Sie nur ein Thema pro Support-Ticket eröffnen.
