Search Results for 'composer'

Also my TD composer is not working ,Its showing ,,,,Error at zones: 5(models) : 1(dom). The model does not match the content Current state has involved an issue. You could try an UNDO operation (CTRL+Z / CTRL+SHIFT+Z)

I’ve tried uninstalling and reinstalling td composer, and td mobile theme, I also tried uninstalling and reinstalling the theme, but nothing works. Also, my site is currently running AMP for the mobile version, but I had redirects set up before to use the non-AMP mobile version because it’s capable of doing more such as the text to speech button. The non-AMP mobile version was working with no problems for quite a while.

Hello. This is the second time I’ve had this same problem when adding a logo image in the footer with the tagdiv composer template builder, the logo that goes with the site title and tagline in the footer created a PHP error, and it’s happening with the Minty Pro footer I think it is. This is the second time I’ve had to contact my webhost support so they can enable allow_url_fopen on their end. It shows enabled in my Cpanel php.ini, but it actually isn’t enabled, even if I disable and re-enable it in php.ini.

It breaks the mobile version of my entire website and it will just rapidly keep reloading the web page on mobile, and images don’t load correctly, it jumps to the top when trying to scroll down.

The error is on line 792 of tdb_header_logo.php, but I get something weird on line 816 also, but it could just be the svg. I’m not sure if it’s normal.

Inbetween ” for $logo_image = ”; on line 816 I get: +/VFkz/6XTzORpC9jetuBMWM5iXmJ6byOFG2mdQNCA5P/bIhVPwkHFH0J6Ernuq6bII9xC2ho2Z1PGFn4pylVSzGdXT883kc04a/zsFwATSE1Dd6RwpXV8B8ms3wmpb3iGQdN4pkoQLPMVc3COlfvU+NuRd5OYcj1HsLat+sq7uGtI3JMCS/iXnK7+Al6FVkFxYwOrY5wz6GQuQs2zuqUtaArO7oKlBtVkhbtm+xYFYYcXQhnU6yBf1SgnMpqP+GUZXv4HTWv66jUwfh7sswY46R4t9MYeV1dPecbWvdWUyX51k/oYM+6uGsBb7Q+72xuvcwNmm2lPClC9XG2V49DgTBOOqGsdA423J0LW4vNqyHbiMfKXtTtMuYVCi2Hd26amDZYEdwrmZ0RezqSHVFxu2XIZzBfg75igepkfkgKe7aS+xWeOaMjhbCwtX9rmDLy/Tf7vgHgnQNxKnNE3xU2S1lWd3CP/e7wLqCJS+K6Up2osMHN3GPxzX0X8Z08lDnV+YDwNEfAZVCRX2dhM6vcJqOVAffMefbhLuq8qOM6bBwErOHplRROqXd2gpXQlzkE3VwoINdvQ0+r0obxcUgWLNYXgyOIur8F7Z8eft6u608AAAAAElFTkSuQmCC

Here is the error I get:
[19-Sep-2020 06:39:43 UTC] PHP Warning: getimagesize(): https:// wrapper is disabled in the server configuration by allow_url_fopen=0 in /home/theaegis/public_html/wp-content/plugins/td-cloud-library/shortcodes/header/tdb_header_logo.php on line 792
[19-Sep-2020 06:39:43 UTC] PHP Warning: getimagesize(https://www.theaegisalliance.com/wp-content/uploads/AEGIS-App-v3-200×200-1.jpg): failed to open stream: no suitable wrapper could be found in /home/theaegis/public_html/wp-content/plugins/td-cloud-library/shortcodes/header/tdb_header_logo.php on line 792

Here is the detail of the error that I received by email directly from WordPress:
Error details
======================
An error of type E_ERROR was caused in line 2264 of the /srv/data/web/vhosts/*****/htdocs/wp-content/plugins/td-composer/legacy/common/wp_booster/td_util.php file . Error message: Allowed memory size of 134217728 bytes exhausted (tried to allocate 40960 bytes)

I followed the recommendations in the post above, but received this email a second time. I went into recovery mode and systematically TD Composer is disabled. I do not know what to do.

My site is still under construction and I just imported a theme without making any big changes.

Hi, Calin,

Yes, it’s a little confusing, but I think once i understand it, and it works, I’ll be able to handle it 🙂

I have now adapted the file “wp-content/plugins/td-composer/legacy/common/wp_booster/td_module_single_base.php”, but no change appears on the author’s box. I tested it in the main-theme and in the child theme, removed the author-box and added it again, but nothing changes. Of course, all cache plugins are deactivated, too.

Wouldn’t it be the easiest to create a complete own block for the tagDiv Composer? (In the composer it is called “Single Post shortcodes”). To avoid confusion or misunderstandings when naming elements like modules, blocks, etc. I have attached a screen to show exactly which element I want to replace/rebuild.

https://prnt.sc/ujzhai

Br

• This reply was modified 5 years by V3N0M.

also when i open the page in tagDiv Composer and click the logo it opens the homepage – is this the default behavior? no menu is opened in the left panel.,

There’s no such color in Theme panel. Found that it’s written in the file:
wp-content/plugins/td-composer/legacy/Newspaper/includes/demos/history_pro/demo_style.css but changed there doesn’t change it on the web, as web loads wp-content/plugins/td-composer/legacy/Newspaper/includes/demos/history_pro/demo_style.css?ver=10.3.6.1
How to fix it?

Hi Calin,

What I try to get is an AMP-Version that looks nerly the same like the normal site version. The only way to get this is in transitional mode, since the settings you recommend refer to (not recommended by the plugin itself) the reader mode, which outputs a very basic AMP theme.

The issue with transitional mode is, that TagDiv currently only bought up an AMP-Version that is also very basic, like the mobile theme. (no support for TagDiv composer elements).

In the meantime AMP has pushed forward and delievers correct output for nearly all elements (when the AMP-Plugin is active and the mobile theme is disabled via classic editor). There are only a very few things not working -> Means, users can have an fast AMP-Version of their websites that delivers all the content and widgets like on desktop.

The only big issue that currently stopps users from using this great AMP-Versions is the header icons are not clickable. (even when only TagDiv plugins are active). But that surly comes from the diabled mobile version. Which needs to be disabled to have the full desktop elements and not the basic grid.

What is missing is an AMP transitional template which is stored with the desktop version.

Or I need a way to apply the AMP mobile header to the AMP Version created out of the desktop version

Hello,

This important point is written in that blog article:-

Only theme files under this folder i.e. wp-content\plugins\td-standard-pack\Newspaper can be changed using the child theme:- https://prnt.sc/ujk85e

And “td-composer” is a plugin file, so do you think we can override plugin files with a child theme? If yes then how? A sample child theme is already installed which was provided in the theme files. Suppose I have to add this place in the child theme: wp-content/plugins/td-composer/legacy/Newspaper/parts/login.php then how can we override this place in child theme?

Also, I went to this code file here: https://prnt.sc/ujkae5 but i don’t know what to edit here to remove popup login and add a custom Login/Register link. Can you please guide me?

Thank you!

• This reply was modified 5 years by TechieBraj.
• This reply was modified 5 years by TechieBraj.
• This reply was modified 5 years by TechieBraj.
• This reply was modified 5 years by TechieBraj.