Search Results for 'block'

Since amp ‘forbids’ client side scripting, it may be they are blocking anything being ‘run’ — or it may be that it runs first time, but then when cached on Google’s CDN for edge loading, the element script can’t run, as it’s not actually on the CDN.

There are folks doing stuff with Ajax with AMP for refreshing origin content; which is a bit like expiring the bucket on a CDN to refresh the local copy of content.

Personally, I’m of a mind, that AMP is an interim solution while wifi speed and phones play catchup. For instance, a new iPad PRO is more powerful than a 10 year old PC that HTML5 was built for.

In theory, one could argue that simply building your own print template with lean code, your desired custom elements like forms, or related post, or video, or whatever, could be ‘dressed down’ to lowest form like a print template, serve that for mobile and not even use AMP. Speed would be the same, especially if you’re already using CDN — and having a lightning bolt in SERPS doesn’t mean your page is better than everybody else’s page, just that it’s compatible, and might not even show up in SERPS, with all other things being equal with relevance, site age, content, etc.

Does the user experience suffer with AMP? Then why use it?

Questions for another time and place probably, but after nearly 2 years since the BETA, we’re kind of re-evaluating this for 2018, frankly.

Just more ramblings … 🙂

You can do trial & error or try figuring out from the icon of the block. Personally, I do both 🙂

Hey Catalin,

URL: http://top101hentai.com
Screen shot link regarding YouTube Video Playlist Block – https://prnt.sc/gfudhg

Regards,
Rosa

thanks. How do you work out what the blocks look like, cause the list on the list is big. Is there way of seeing it before dragging it in the sidebar?

Put any block on the sidebar you want but then go to Block Settings > Filter > Category Filter > Select the category you want for the block

Thank you very much for the recommendations.
Usually I use a child theme to make my own modifications and not lose them when updating the main template, when changing to the main template the images were displayed again.

Many thanks to the entire Newsmag team for the quality that has always characterized them.

P.S. If you share a little of your good fortune with me I will be thanking you even more. 🙂

Hi Simion, thanks for that, that seems to have done the trick, I do however have a related issue with the registered params for custom blocks.

I used Block 10 as a base for my own custom block so everything should be the same, however, in page builder and now as a widget the params are completely different with a number of them missing? Please see the attached image.

Instead of ‘General – Filter – Ajax – Extra’ my custom block has ‘Filter – General – Ajax – Extra’ with a number of the ‘General’ params missing, Custom Title, title colour, head template etc, am I missing something?

Yes, well — theme doesn’t manage your open graph settings, image compression level, server speed, IP blocking, Facebook API, etc.

All you can do on theme and plugin side is add the tags, check that FB can access them, adjust anything breaking the tags, or blocking loading of images, etc., and then it’s up to FB to capture the content.

You cannot pay them or force them or berate them — they don’t care; you’re not paying them to grab your posts.

I’ve been in the beta FB stuff since FB first launched, and this is a recurring issue. But there you are.

Setup your FB developer account, check your posts, code, etc., learn to clear FB cache of your post if it’s hiccup-ing, check your page speed carefully, caching, image speed, etc. — all that stuff impacts FB being able to get stuff “quick.” A 600×450 image that is 35kb will be more likely to get captured properly than a 350kb image the same size, for example.

Anyway, good luck.

I think that setting is in the blocks panel in the theme settings.