audunmb

Thanks for the reply and suggestion.

> Otherwise, I don’t think there’s a simple way to remove the dropdown functionality of the Navigation Block, since it’s a key part of the way the block is built to work.

Why is that? It’s the block for adding menus? Menus have many uses, not only to add top level navigation. Though, the navigation block is very limited as it is now. Both with the hamburger menu option (bad UI in most cases) and this limitation on how to display menus. With non-FSE themes this isn’t an issue at all.

Are there any other blocks for displaying menus? Can the page list block you mention display menus? Listing all pages on my complex site won’t work.

• This reply was modified 2 years, 3 months ago by audunmb.

@thelmachido yes, it’s possible, just very well hidden. Actually, nearly all of the options in Full Site Editing is well hidden. There’s no “Edit templates” in the regular control panel, you have to first click “Edit site”, and then hidden as an option in the top panel there’s “View all templates”.

This is OK for a beta version, but it’s horrible UI.

As noted, besides the site icon, there are simply a lot of options missing. The main drawback is the lack of responsive options. For example:

* I can’t show my website slogan in desktop header and hide it on mobile (yes, you can do this with CSS but you shouldn’t have to. )

* I can use a hamburger menu (not recommended if you want people to click on the things in the menu), but I can’t have an actual mobile-adapted menu (with only the most relevant items and a “more”/hamburger button).

* For some reason, you can’t create a navigation block which shows all the submenu items by default. This is regular behaviour in footer menus.

Did you find a solutiuon to this? I have the same issue on my localhost install.

To be fair, it was www.remarpro.com-moderator that closed your previous thread (in a very unhelpful way IMO), unrelated to the plugin. But try contacting them using the contact form on their webpage https://wp-events-plugin.com/contact-us/ and use the “None of the above”-option.

For a better rating (from me, others may have other preferences) use wordpress defaults for styling.

Though, the option to choose whether it should be a heading block or regular text block would be a nice feature.

Ok, only selected fonts, not the whole library. I still don’t need a custom font list for my animated text. This will conflict with loading fonts from the theme, especially with Full Site Editing themes and the styling provided trough them.

Branding parts of the normal interface is a confusing thing to do. So still only two stars from me, even if the plugin in itself works.

Thanks, but that doesn’t work with Adobe fonts. It only supports local fonts, and the Adobe license doesn’t allow local fonts.

A workaround that works for me now is to use a custom plugin for block styles. Then I can add the fonts I need trought the plugin css and use Adobe fonts for special block styles (like Heading). Still, for the default fonts I need to use the free fonts that can be used locally.

An option may be to specify the fonts trough the theme.json file and then load the fonts from Adobe trough the plugin (or other solution for custom css), but the webfont api of theme.json breaks if you don’t provide the source of the font (which means that the child theme.json won’t load at all).

Using inspector this CSS causes this

select:not(.elementor-field), .woocommerce div.elementor .the7-elementor-widget form.cart table.variations td.value select:not(.elementor-field) {
  -webkit-appearance: none !important;
  -moz-appearance: none;
  background-image: linear-gradient(45deg,transparent 50%,var(--the7-input-color) 50%), linear-gradient(135deg,var(--the7-input-color) 50%,transparent 50%);
  background-position: calc(100% - var(--the7-right-input-padding) - 5px) 50%, calc(100% - var(--the7-right-input-padding)) 50%, 100% 0;
  background-size: 5px 5px, 5px 5px, 2.5em 2.5em;
  background-repeat: no-repeat;

The appearance: none hides the regular dropdown arrow, while the background image is the superimposed dropdown-arrow. You have to remove or override all of them to make this look normal.

It might be from Elementor by the look of it.

Seems like there’s some styling from woo-commerce that overrides how this looks on your site. Instead of a regular dropdown arrow there’s a background image thing.

I’ll make a new post for the bug with categories and tags.

The main sticking point for not making support by default is due to the lack of user warnings when events are not complete (such as a missing date) or any other reason for the event not being published after hitting the publish button.

Several plugins have a pre-publish checklist, you could probably add that to make sure that posts have date, location etc.

Also, it seems like categories and tags doesn’t work if I enable Gutenberg. The screen where you choose them doesn’t show and I can’t add it trough the settings.

I somehow missed this reply. To bad, I’ve been using you plugin for years, and it’s great, but lacking support for the new WordPress editing makes me consider switching to another.

Thanks for your answer. I was a aware that hamburger menu was an option, but I don’t want a hamburger menu only (it’s bad for UX), I want a short menu and an extended menu (where the hamburger is good).

CSS hacks is also possible solution, but doesn’t fix the menu issue. It can fix size of the logo image, but often you have different versions of a logo for different sizes and uses. A separate header for mobile view would be a much better solution.

Do you (or anyone else) know if there’s anything on the roadmap for separate mobile view templates?

Currently, for instance the popular Neve theme (not FSE) has a header builder which allows for different headers in mobile view.

I think something similar should be a rather obvious thing to do.

And maybe not only for headers and footers, but for all templates. The UX on mobile is different, so you need different templates.

Some things you may want to hide or move (CTA buttons, graphical elements, banners, etc), some things you may want to make smaller or tighter to get a better view on mobile. Many custom blocks already have options for mobile view, adding that to the whole editing interface should be obvious.

To add a template, remember to also add it as html file in the templates folder (preferably use a child theme), not only in the json file.

AFAIK for the Home page-template, it actually controls the “blog home” page. If you have static home page, you can create a Front page template for that.

There’s an block option for setting it to default. I don’t know why it doesn’t default to the default, but you can change it at least.