opentype

→ Plugin Settings

You need to delete the old templates and install the latest ones.

The preview isn’t very reliable. Don’t count on that. Test it on the site. And test it without a SuperGrid template first. If you can’t get a regular Pages block with the stock block template and a record feed working, I would suggest to open a support ticket with IPS.

Please use browser inspector options or plugins to find them like we would do it with any other CSS customizations as well. Sorry, I am not following that. In general, the SuperGrid block is just a different styling for “Pages record feeds”. There is nothing special about it and it shouldn’t depend on any other blocks. You should be able to create a regular feed block – see it working – and then add the SuperGrid theme later to it. That should change the appearance, but show exactly the same entries as before.

Go to the SuperGrid settings. There is a color selector there to change that default white background to your dark background color.

As far as I can see that is a theme problem. You can try it in the default theme to make sure.

Looks fine to me.

SuperBlocks as Pages blocks in general are meant as links to content. Embedding full content there would lead to various other problems and so I don’t plan to change that. For videos in Pages databases I would rather solve this in the content itself. Write a little sentence to describe the video. That wouldn’t hurt and even help with SEO.

That is already an option.

Nope.

The blog entries need a “Featured Photo”.

Feel free to support my feature request to improve the Pages template updating procedure:

I tried both on my development installation and my demo site. I can’t replicate that problem, so for now I assume the template is fine.

You can force to show more images in the plugin settings by going to the tab “image settings”.

Looks fine to me. The image from my site show a widget with 3 entries. Yours has 6.

Go to Plugins → SuperDocs Settings and click Edit. Turn off “Use custom header image” or add another one.

Is this really starting all over again? How many times does it have to be pointed out that URL delisting shown in the Search Console cannot be caused by the sitemap generation? Listing and delisting happens when Google crawls the actual URL and it is decided based on what it finds on that URL. That’s it! The sitemap can only help Google to find the URL faster. Nothing in the sitemap will cause an URL to be delisted. How could it? It’s just URLs saying “please check this out, Google!”. No slow or incomplete sitemap will cause delisting. No faulty sitemap will cause delisting. No entirely missing sitemap will cause delisting. Nothing in the sitemap can cause delisting. If you find an actual bug in the sitemap creation you can demonstrate to be true, better open a support ticket or start a new topic about this bug and nothing else instead of adding it to this huge pile of “I don’t like my Google stats and I will just blame IPS and ask them to fix it”.

No. And copying some text from a blog on the internet doesn’t prove the opposite. In any case: I merely add a button to access IPS’ contact form. I won’t change its functionality.

Not sure I understand the question. It’s just a more visible button linking to the contact form. (And you can choose the user groups who see it.) Contact forms do not require additional consent, just as a online shop does not need consent that you use the shipping address for shipping the order. However: It doesn’t hurt if you describe your use of the contact form data in the privacy policy. Is the data stored on the website or sent via email? Will it be deleted after a while? Do you guarantee not to sent advertising or give the data to someone else. This kind of stuff …

Advise? Drop it and use the native cookie notice function that was added to Invision Communtiy.

It is using the setting “Cache sidebar, header and footer blocks”, but that is usually only set to a few minutes. So to be clear: the order should change each time the cache time has run out, not on every page load.

Yes. That is correct. And you also need to turn on the “Shuffle Entries” checkbox.

SuperBlocks is just styling. It doesn’t change anything about the ordering of records. That comes from Pages. So your problem probably has a different cause.

It shouldn’t matter where the image is stored, as long as its accessible and not outdated. I can’t really debug this from a screenshot though. Have you tried to hitting the “scrape again” button as mentioned in the instructions?

Support topic for this product: