abledragon

Hi there,

Many thanks – that did the trick.

Cheers,

Martin.

Hi Guys,

That CSS fixes the Details page but messes up the Thumbnail page:

Front page (Thumbnail view) on FF and Edge

Martin.

Hi there,

Perfect – that did the trick and it actually looks better than it originally did prior to 4.4.0.

Many thanks!

Martin.

Hi guys,

Just to let you know that I’ve now rolled back to 4.3.11 on the Almerispa site as well.

If you need me to update to 4.4.0 to check on fixes, let me know.

Cheers,

Martin.

Hi there,

Many thanks…

I added the CSS to the catalogue’s custom CSS field. This does fix the font problem for all elements on the catalogue page, but not on the other pages on the site. I can send screenshots again if you like.

This affects Chrome, Firefox and Edge – all non-catalogue pages are rendering with the browser default font for body text, menu and footer areas in all of those browsers. H elements are not affected – they are rendered in the correct font.

Just an observation: the CSS you sent me defines the font that I’m using on that site, but not everyone is using the same font – so that is not a universal fix.

Also, just to confirm re Chrome: as well as the incorrect font style on the non-catalogue pages, the page still does not render correctly, because the next/back buttons are not rendering with the box and shadow around them. I have rolled back to 4.3.11 on the other UPC sites that I’m managing and the screenshots below compare the two versions:

Next-Back Buttons Version 4.3.11

Next-Back-Buttons Version 4.4.0

Cheers,

Martin.

Hi there,

Thanks for getting back to me.

Adding that font-family CSS to the Catalogue custom CSS field made no difference.

As you can see from the screenshots I’ve uploaded below, the font selection is being corrupted outside of the UPC areas and on non catalogue pages as well as within UPC areas.

The Sale icon and the next and back buttons are rendered incorrectly on both Firefox and Edge – see the screenshots below.

On Chrome while the ‘Sale’ icon does not show up as a square there has been some additional padding added, moving the Sale icon away from the div edges. Also the back and next buttons are not appearing as before, and the font family selection has been corrupted both within and outside UPC areas.

I have uploaded 6 screenshots for you to review:

Screenshot of Almerispa Footer font with UPC Deactivated

Screenshot of Almerisap footer font with UPC Activated

Screenshot of non-catalogue page font with UPC activated

(I can upload an image of this font with UPC deactivated if it would help)

Screenshot of Sale icon and next buttons on Edge

Screenshot of Sale Icon and next Buttons on Firefox

Screenshot of Chrome UPC page

Please note on the Chrome screenshot I forgot to circle the next and back buttons.

Cheers,

Martin.

Hi Guys,

Many thanks – that did the trick,

Cheers,

Martin.

Hi Tammie,

Please accept my apologies for my late response to your questions and I do appreciate you taking the time to go through and respond to my feedback.

My comment ‘social blogger’ was just a way of referring to someone who has no interest in working in the code editor view. They typically don’t know HTML or CSS and have no interest in knowing it. These people are not experienced bloggers and are looking for a way to easily create page layouts where they can see what they are doing – in the way that some of the front of page editor plugins currently allow. They would work in the visual view and expect what they create in that view to be what it would look like on the front of the site.

But that is not the case.

The easiest way to describe the disconnect between the visual view and the front of the site appearance is this: the visual view editing window in Gutenberg is 616px wide. If the content column on the front of the site is 1000px wide the content layout will look very different on the front of the site from what it does in the visual editor. And 1000px content width these days is among the narrower of widths.

Using the columns block to create 2 columns or, worse, 3 columns, makes the columns look ridiculously narrow in the Visual Editor (less that 200px wide if 3 columns are used), whereas on the front of the site they would be around 300px wide – 50% wider.

This disconnect would frustrate a novice user.

You referred to nested blocks creating more complicated layouts… My point is that the more complicated the layout the less the visual view will give the novice user an accurate representation of how it looks on the front of the site..!

The objective must, surely, be to make the representation in the visual editor view match the front of site rendering as closely as possible, but they don’t come close..!

One possible solution might be to make the editing window in the visual view wider so that the representation in the Visual view would more closely match the appearance on the front of the site.

Currently there is all that completely wasted white space on either side of the visual editor (and code editor) and it gives a cramped feeling, whereas the classic editor gives one a feeling of space.

Even if making the editor window wider would not fix the problem of disconnected rendering of the content layout, I would still like it to be made wider in any case.

One other point that I should have mentioned before: I cannot see any place to edit the permalink. That is a serious omission.

The version I was working with when I wrote my original feedback was 2.5. Version 2.7 came out today, and the bugs I referred to appear to have been fixed.

Again, my apologies for my late reply and thanks, again, for taking the time to review my feedback.

Cheers,

Martin.

Hi there,

Ok, that’s great. I need to be able to prepare my clients in advance for the shift to Gutenberg, so it would be really good if you guys could put out a general email when you know what changes, if any, will need to be made, especially those that will affect end-users.

The one area that comes to mind (that affects me, not my clients) is that UPC uses shortcodes to establish catalogue pages and, as I understand it, shortcodes will become obsolete under Gutenberg.

Many thanks for your quick reply, and a general advisory mailing when you know what steps we will need to take would be great.

Cheers,

Martin.

Hi Rolf,

I updated to 4.4.3 this morning and the plugin changed the UTC time displayed in the WP settings to my local time. Deactivating the schedule did not fix the issue, I had to deactivate the plugin.

As soon as I deactivated the plugin the UTC time was displayed correctly. I reactivated and deactivated the plugin a second time just to be sure and got the same result.

I’m also on Siteground and they confirmed the server TZ database is correctly set up.

Cheers,

Martin.

Hi Mikko,

Ok, many thanks,

Cheers,

Martin

Hi there,

Yes, I saw (and updated)

Many thanks!

Cheers,

Martin.

Hi Guys,

OK, thanks,

Cheers,

Martin.

OK, Thanks,

Cheers

Hi there,

OK, I understand the point.

Is there a way I can make the categories non-clickable, so they are visible but only the sub-categories can be selected..?

I know there’s no option in the settings, but is there a code snippet you could give me that would do that..?

Cheers,

Martin.