Search Results for 'composer'

Hi Bettina,

Please read the thread, because what you have said: “This is a default mobile modal, so it can not be customized with the TagDiv Composer” doesn’t seem to be relevant.

Hello Bettina,

Your solution did not work. Using my browser’s inspector, I can get a class (something like tdi_148) from a page and assign “display: none;” to it. But on another page this class will be different. So I will have to manually add more and more classes for every single page. Moreover, I may have several “Related article” blocks in one post.

Finally, I created my own classes and assigned them to each shortcoded element using the field Extra Class in TD composer:

@media (max-width: 767px){
    .my-custom-hidden-mobile {
        display: none;
    }
}

@media (min-width: 768px){
    .my-custom-visible-mobile {
        display: none;
    }
}

Now it works as expected. I get shortcode of the flex block and I insert it in many various posts on my site. They are properly hidden on mobile screens (or visible on bigger screens only).

• This reply was modified 3 years by Sergey.

https://i.imgur.com/w3FiOgi.png

hi carlin
I read your article and confirmed that the size of the thumbnail is reduced when I do the same in Composer Composer. This is not how I want it to be.

I would like the image to be output as it is with the real news theme as it is now. i’m hoping for this

Is this a theme issue?
Is it a problem with the size of the uploaded picture?
Or is it a plugin conflict issue?
other problem

This is exactly what I want to check and solve.

It is working in tagDiv Composer, but doesn’t work on the live site!

Hi
yes I used mobile theme with amp
SETTING
Salta al contenuto principaleVai alla barra degli strumenti
Informazioni su WordPress
Sicilia Report
00 commenti in moderazione
Nuovo
SEO
Theme support
WP Rocket

Bespoke Web Development & Design Services
Take your website to the next level with web solutions designed for you!

Get free quote
Impostazioni AMP
AMP Settings Configured
The AMP configuration wizard helps you choose the best configuration settings for your site. Reopen Wizard.

Site Scan
The site has not been scanned yet. Scan your site to ensure everything is working properly.

Scan Site

Review
Your site is ready to bring great experiences to your users!

In Transitional mode AMP and non-AMP versions of your site are served using your currently active theme.

Browse your site below to ensure it meets your expectations, and toggle the AMP setting to compare both versions.

Need help?
Reach out in the support forums
Try a different template mode
Learn more how the AMP plugin works
Browse Site
Dismiss
Template Mode

Transitional

Transitional

Advanced Settings

Modelli supportati

Tipi di contenuti
Content types enabled for AMP:

Articoli

Template

Serve all templates as AMP

Limit AMP on a subset of the WordPress Template Hierarchy:

Singolare

Plugin Suppression
When a plugin adds markup that is not allowed in AMP you may let the AMP plugin remove it, or you may suppress the plugin from running on AMP pages. The following list includes all active plugins on your site, with any of those detected to be generating invalid AMP markup appearing first.
Stato Plugin Dettagli
Plugin status:
Active Ad Inserter Pro No validation errors yet detected.
Plugin status:
Active Advanced Database Cleaner PRO No validation errors yet detected.
Plugin status:
Active Advanced Editor Tools No validation errors yet detected.
Plugin status:
Active Classic Editor No validation errors yet detected.
Plugin status:
Active Featured Image from URL (FIFU) No validation errors yet detected.
Plugin status:
Active Imagify No validation errors yet detected.
Plugin status:
Active Resize Image After Upload No validation errors yet detected.
Plugin status:
Active Site Kit by Google No validation errors yet detected.
Plugin status:
Active tagDiv Cloud Library No validation errors yet detected.
Plugin status:
Suppressed tagDiv Composer Since 16 April 2023. Done by Redazione CT.
Plugin status:
Active tagDiv Mobile Theme No validation errors yet detected.
Plugin status:
Active tagDiv Newsletter No validation errors yet detected.
Plugin status:
Active tagDiv Social Counter No validation errors yet detected.
Plugin status:
Active tagDiv Standard Pack No validation errors yet detected.
Plugin status:
Active Videojs HTML5 Player No validation errors yet detected.
Plugin status:
Active Wordfence Login Security No validation errors yet detected.
Plugin status:
Active Wordfence Security No validation errors yet detected.
Plugin status:
Active WPeMatico No validation errors yet detected.
Plugin status:
Active WP Rocket No validation errors yet detected.
Plugin status:
Active WP User Avatars No validation errors yet detected.
Plugin status:
Active Yoast SEO No validation errors yet detected.

Analytics
Scopri ulteriori informazioni sull’analisi per AMP.
Analytics Configuration #1
Tipo:
Vendor or blank
CONFIGURAZIONE JSON:

}
}
Remove entry
Add entry

Sandboxing (Experimental)
Try out a more flexible AMP by generating pages that use AMP components without requiring AMP validity! By selecting a sandboxing level, you are indicating the minimum degree of sanitization. For example, if you selected the loose level but have a page without any POST form and no custom scripts, it will still be served as valid AMP—the same as if you had selected the strict level.

Enable sandboxing experiment

Paired URL Structure
When using the Transitional or Reader template modes, your site is in a “Paired AMP” configuration. Your site’s canonical URLs are non-AMP, and the separate AMP versions of your pages have AMP-specific URLs. The structure of a paired AMP URL is not important, whether using a query parameter or path suffix. The use of a query parameter is the most compatible across various sites and it has the benefit of not resulting in a 404 if the AMP plugin is deactivated. Note: Changing the paired URL structure can cause AMP pages to temporarily disappear from search results until your site is re-indexed. If you’re migrating from another AMP plugin with a different paired URL structure, then you may want to change this setting. Otherwise we recommend leaving it as is. Learn more

There are one or more entities that are already using the “amp” URL slug. For this reason, you cannot currently use the path suffix or legacy reader paired URL structures. See below for the source of the slug conflict(s):

Tag: AMP (ID: 9265)
Query parameter: ?amp=1 (default)
Path suffix: /amp/ (unavailable due to slug conflict per above)
Legacy transitional: ?amp
Legacy reader: /amp/ & ?amp (unavailable due to slug conflict per above)

Altro

Redirect mobile visitors to AMP

Enable Developer Tools
Enable AMP developer tools to surface validation errors when editing posts and viewing the site.

This is a per-user setting. It presumes you have some experience coding with HTML, CSS, JS, and PHP. Once enabled you will have access to Validated URLs and Error Index in the admin menu, the Validate URL item in the admin bar, and the AMP Validation sidebar in the editor.

Use native HTML image tag
The native HTML can now be used instead of the AMP-specific <amp-img> tag. AMP no longer requires the latter because lazy-loading is now a feature of the Web platform. Using native images can further improve page performance, although not all AMP components have been updated to work with them (see example). If you have CSS that is specifically targeting <amp-img> tags, you will need to update them to target instead (which can be done by default since such tags are automatically rewritten in CSS selectors when conversions are done).

Delete plugin data at uninstall
When you uninstall the plugin you have the choice of whether its data should also be deleted. Examples of plugin data include the settings, validated URLs, and transients used to store image dimensions and parsed stylesheets.

Salva
Grazie per aver creato con WordPress.Versione 6.2

• This reply was modified 3 years by zarbos.