Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • I was searching the same thing. Basically I want to make the editor easier to use for a non-techy person and the Gutenberg preferences allow me to do so. But as you said, not system wide.

    ffabb

    (@ffabb)

    To use the template of the Blog-Homepage on all the other so-called Archives using a Site Editor-enabled theme, do the following:

    1. Open the Site Editor by using the Admin Bar
    2. Open the Templates menu (typically /wp-admin/site-editor.php?path=%2Fwp_template)
    3. Locate both the “Blog-Homepage” and “All Archives” entries in the templates-lists.
    4. Open the “Blog-Homepage” template and click into the preview to use Gutenberg. Copy the necessary elements using the context menus (to locate the elements I suggest using the list view – just press the three lines in the top bar).
    5. Next, open the “All Archives” template, delete the existing contents (keep Header & Footer I guess) and paste the template-parts you copied previously.

    In case you only want that layout on the “Golf Courses” “Travel” and “Products” sites, click “+” on the templates page in the Site Editor and create new templates just for these categories.

    If you have any further questions, feel free to ask!

    Cheers!

    ffabb

    (@ffabb)

    Hi @jroliver6! I see that you’re using the Hevor theme, but could you please share whether your theme is using the new Site Editor (FSE) or the Customizer instead? If you need any assistance with that, just write!

    Welcome to WordPress, by the way!

    • This reply was modified 11 months ago by ffabb.
    Thread Starter ffabb

    (@ffabb)

    Thanks to @graylaurenm for pointing out a workaround on Github, involving creating custom taxonomies and selecting the created taxonomy in the FSE create-template popup. This worked indeed!

    A workaround on your end would be to use a custom taxonomy. Then all of those archive pages would have one template while categories would have another. This would avoid a lot of complex logic by taking a more foundational approach.

    Lot’s of people are having this issue on deactivating the plugin, including me. Really bad, and no updates from cookie-script.com

    Same error, any updates?

Viewing 6 replies - 1 through 6 (of 6 total)