Search Results for 'composer'

Prezados, bom dia.

Tudo bem?

Estamos enfrentando problemas de lentidão e instabilidade no site mensageirodapaz.com.br, que utiliza o tema Newspaper.

Apesar de já termos realizado diversas ações junto ao provedor de hospedagem, incluindo aumento de memória, ajustes de recursos e atualização de versões do PHP, o problema persiste, e a performance do site continua abaixo do esperado, impactando diretamente a experiência de navegação.

Além disso, identificamos incompatibilidade no plugin Tag Composer, que apresenta erros ao utilizar versões do PHP superiores à 7.4. Isso tem nos obrigado a manter uma versão antiga do PHP, o que acaba limitando a atualização de outros plugins e comprometendo a segurança e evolução da plataforma.

Diante disso, solicitamos, por gentileza, uma análise técnica mais aprofundada por parte da equipe responsável pelo tema, para identificação de possíveis gargalos de performance, incompatibilidades ou ajustes necessários que possam estar impactando o desempenho do site.

Ressaltamos que o projeto está em fase de lançamento de um portal de assinaturas com conteúdo digital, sendo a estabilidade e performance fatores críticos neste momento.

Fico à disposição para fornecer acessos de forma segura por um canal apropriado, caso necessário.

Desde já agradeço pela atenção e apoio.

Atenciosamente,

Prezados, bom dia!

Tudo bem?

Estamos enfrentando problemas de lentidão e instabilidade no site mensageirodapaz.com.br, que utiliza o tema Newspaper.

Apesar de já termos realizado diversas ações junto ao provedor de hospedagem, incluindo aumento de memória, ajustes de recursos e atualização de versões do PHP, o problema persiste, e a performance do site continua abaixo do esperado, impactando diretamente a experiência de navegação.

Além disso, identificamos incompatibilidade no plugin Tag Composer, que apresenta erros ao utilizar versões do PHP superiores à 7.4. Isso tem nos obrigado a manter uma versão antiga do PHP, o que acaba limitando a atualização de outros plugins e comprometendo a segurança e evolução da plataforma.

Diante disso, solicitamos, por gentileza, uma análise técnica mais aprofundada por parte da equipe responsável pelo tema, para identificação de possíveis gargalos de performance, incompatibilidades ou ajustes necessários que possam estar impactando o desempenho do site.

Ressaltamos que o projeto está em fase de lançamento de um portal de assinaturas com conteúdo digital, sendo a estabilidade e performance fatores críticos neste momento.

Fico à disposição para fornecer acessos de forma segura por um canal apropriado, caso necessário.

Desde já agradeço pela atenção e apoio.

Atenciosamente,

Hello,

Since updating to WordPress 7.0 today, I have detected a visual/functional issue in the builder’s CSS panel, specifically in the Margin / Padding fields of the Single Image module.

I’m leaving you a Loom video where the behavior can be seen clearly:

https://www.loom.com/share/26601c055dd3494d9745ede4635d838b

The problem is the following: before the update, within the visual margin/padding scheme, the fields allowed values of at least two characters or values with a unit to be displayed correctly. For example, if a padding value was 10%, the field allowed me to see 10 or 10%, or at least scroll inside the input in a useful way to check the full value.

Now the behavior has changed. The fields are displayed too narrow and only show one character of the value. For example, visually it may look like the padding is 1 / 1 / 1, but in reality the values are of the type 10% / 10 / 10%. When I move inside the field, instead of being able to see the full value or at least two characters, only one character is shown at a time; in this example, in order to see the %, I have to move within the field and instead of being able to see 0%, as part of 10%, only that is shown: the %.

This makes the CSS panel difficult to use, because I cannot visually check whether the real value is 1, 10, 10%, etc. The problem does not seem to be that the value has been lost, but rather that the panel input is displaying it cut off or with insufficient width. I have been using TagDiv for more than 7 years and I know what I am talking about when it comes to composition and the details of the composer.

I have tested it both in the desktop composer and in the mobile composer. I have also tested it in incognito mode, in case it could be due to browser cache. In addition, the page cache was cleared after the update.

For this reason, I understand that it could be a visual incompatibility of the builder after updating to WordPress 7.0, an internal CSS issue in the panel, a change in the width of the inputs, a rendering issue in the editor, or some incompatibility with the current version of WordPress/browser.

It is not necessarily that the page design has changed, but rather that the editor no longer displays the full values correctly inside the margin/padding fields.

The issue directly affects editing, because it makes it very difficult to review or modify margins and paddings without the risk of changing incorrect values.

Thank you. Please, I would really appreciate your help with this.

I am trying to assign my staging site as the 2nd site for the license. There is no way to assign it because you say I have another staging site that is licensed. That is incorrect. The license applies to TravelMaine.com but the staging2.travelmaine.com was deleted a long time ago. Why are you making me buy another license for a new staging site? That does not seem fair to me. 

Also, my developer said the site is breaking on the staging site when they try to update because I need the two plugins (see message below). Why are they not included in the update? Is this happening because you will not allow me to use my license on a staging site? Please advise ASAP!

Hello Lisa,

Thank you for contacting our Help Desk.

We have completed testing of the theme update on the staging site.

The Newspaper parent theme was upgraded successfully, while the child theme remained in place as expected. However, after the update, we found an issue with two required companion plugins, td-composer and td-cloud-library. These plugins did not remain active properly after the upgrade, which caused problems with the theme functionality and page layout.

Because of this, we reverted the change after testing so the site would remain stable and continue working as expected.

At this point, the issue does not appear to be with the update process itself, but rather with the plugin versions that should match the updated theme version. The package provided seems to be missing the corresponding plugin files, or it does not include the correct versions needed for this release.

To proceed safely, we would need the complete theme package for this version, including the bundled plugin files, so we can install the matching versions and test the update again.

Please send over the full package if available, and we will be happy to continue from there.

Best Regards,

Kamen Kumanov
Technical Support Supervisor

Hi there,

I’ve been trying for awhile now to upgrade a site to 12.7.6 from 12.7.5 but each time it breaks the top portion of the site. After upgrading, I re-install and activate the tagDIV Composer and tagDIV Cloud Library as both installations are removed but the logo, nav menu, ad, weather widget and general formatting are removed. This is what it should look like:

This is what it looks like after updating the theme:

These are the theme plugins that are installed and activated:

Thoughts on what might be causing this?

Hello,
I have a critical issue on my news site: I cannot publish new articles. When accessing the editor (Add New Post), the page stays blank.
Technical details:

WordPress: version 7.0 (latest)
Theme: Newspaper, version 12.7.6 (latest)
tagDiv Composer: latest version available
All plugins are up to date

Console error (DevTools):
edit-post.min.js?ver=28ef50b859708963e197:1 Uncaught TypeError: (0 , yt.registerLegacyWidgetBlock) is not a function
at Object.pn (edit-post.min.js?ver=28ef50b859708963e197:1:49057)
at HTMLDocument.<anonymous> (wp-edit-post-js-after:5:25)
There are also deprecation warnings related to your blocks:
Block with API version 2 or lower is deprecated since version 6.9.
Note: The block “tds/partiallocker” is registered with API version 1.
Note: The block “tds/contentlocker” is registered with API version 1.
Plus a 404 error when loading load-scripts.php.
Likely cause: the registerLegacyWidgetBlock function from the @wordpress/widgets package was removed in WP 7.0, while a script injected by your theme/Composer (wp-edit-post-js-after) is still calling it, which completely breaks the Gutenberg editor from loading.
What I’ve tried:

Temporarily deactivating other plugins (issue persists, so it’s isolated to Newspaper/tagDiv Composer)
Clearing cache (LiteSpeed Cache, full purge)
Confirmed all components are on the latest version

Please confirm if this is a known compatibility issue with WP 7.0, and let me know your estimated timeline for a fix/patch. In the meantime I’m using Classic Editor as a workaround, but I need Gutenberg working again as soon as possible since the site is active and requires frequent article publishing.
Thank you

Hello,

We are currently working on the website:

https://www.sostenible.com.mx/

We are having an issue with the page editor / builder. The pages are no longer editable through the builder, and on the frontend the content is being displayed as raw Visual Composer / WPBakery shortcodes instead of being rendered properly.

For example, the homepage is showing content like:

[vc_row][vc_column][td_block_ad_box spot_id="custom_ad_2"]…
[td_block_2 custom_title="ACTIVIDADES PRIMARIAS"]…
[/vc_column][/vc_row]

The site was originally running an older version of the Newspaper theme, version 7. Everything was working correctly before, but the issue suddenly started. We then migrated/updated the theme to version 12, expecting the problem to be resolved, but the issue still persists.

Based on what we are seeing, it looks like the problem may be related to Visual Composer / WPBakery Page Builder, because the builder is not loading correctly and it appears to be asking for a license or activation. Since the content depends heavily on Visual Composer / WPBakery shortcodes, the site is currently unable to render the pages correctly.

Could you please help us review the following?

Confirm if the bundled Visual Composer / WPBakery plugin included with the Newspaper theme is active and compatible with version 12.
Check if the plugin requires a separate license or if it should be activated through the theme package.
Verify why the shortcodes are being printed as plain text instead of being parsed/rendered.
Confirm if there is a missing plugin, corrupted builder installation, or compatibility issue after the migration from Newspaper v7 to v12.
Let us know the recommended steps to restore the page builder functionality without losing the existing page content.

The main issue is that the website content is still stored using Visual Composer / WPBakery shortcodes, but the builder is no longer processing them correctly.

Thank you.

Best regards,
Adalberto Larios

Hi,
I received a message from BlogVault abour the vulnerability of Tagdiv Composer 5.4.4:

“The The tagDiv Composer plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 5.4.4. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes.”

Please advise.

Thank you!

Hello,

I’m using the Newspaper theme (version 12.7.6, with tagDiv Composer) on my live news site zzpnieuws.nl, which has an archive of 1,100+ articles. I want to use the Relevanssi search plugin to improve site search, but the search results page returns no results when Relevanssi is active.

What I’ve confirmed:

– With Relevanssi active, the search results page (e.g. /?s=schijnzelfstandigheid) shows “no results” for terms that appear hundreds of times in my archive, even though Relevanssi’s index is fully built and correct (1,122 documents, ~139,597 terms; posts and pages both included) and all Relevanssi settings are correct.
– The moment I deactivate Relevanssi, the theme’s native search works again immediately and returns the expected results. So the theme search itself is fine; the conflict is specifically between the search results template and Relevanssi.
– This persists on the latest version 12.7.6, with all caches cleared.

I’ve read an earlier reply from your team (Bettina) to another user, suggesting to edit the search page with tagDiv Composer and use a Flex Block with the filter “Search: Current Search” and no offset value. I’d like to apply this correctly but I’m not sure which template controls my search results page.

My questions:

1. Which template controls the search results page in the Newspaper theme – is it a Cloud Library template, a dedicated Search template in the Website Manager, or the theme default? I have a custom archive page that contains the search form, but the results appear on a separate /?s= page.
2. How should the Flex Block (“Search: Current Search”, no offset) be configured so the search results respect Relevanssi’s output instead of the theme’s own query?
3. Is there a recommended filter or hook for this that survives theme updates, rather than editing a core theme file?

I have a full backup in place and can provide temporary admin access through the official support channel if needed. This isn’t urgent – native search is working as a fallback – but I’d like to know the correct way to integrate Relevanssi with your theme.

Thank you,
Marco Weeber
zzpnieuws.nl

Hello guys,
I just spend months on re-creating my website on the Newspaper theme. When everything was complete, I deleted everything on my root-domain folder and cloned this stagging site to the root to replace the old website.

Everything works fine – except that in the lower right corner, I now have an:
“ERROR Sitekey is invalid” message.

Please check it on my live website:
htttps://www.Pro-Street.dk

I have running through all my plugins, and as soon as I activate the theme and Tagdiv Composer, this error appears. How can I fix it? 🙂

Hello tagDiv Support,

I am experiencing a serious issue with tagDiv Composer on my website using the Newspaper theme. The Composer has gradually become slower over time, and it has now reached a point where it consistently freezes whenever I attempt to add even a single element to a page. The browser eventually displays a “Page Unresponsive” message.

The issue was not present when I initially started building the website. Composer worked normally in the beginning, but performance degraded over time until it became unusable.

Here are the troubleshooting steps I have already completed:

• Switched PHP versions from 8.3 to 8.2 with no improvement.
• Confirmed PHP settings meet recommended requirements:

PHP Version: 8.2.30
PHP Memory Limit: 512M
PHP Max Input Variables: 10000
PHP Time Limit: 180 seconds
PHP Post Max Size: 1024M
PHP Upload Max Filesize: 1024M
• Created a staging site, and the exact same issue occurs there.
• Deactivated all non-tagDiv plugins, but the issue persisted.
• Checked the browser console and only found Content Security Policy report-only warnings and slow network messages. No obvious JavaScript errors were present.
• Tested Composer on multiple pages, and the freezing behavior continues.
• Cleared caches and tested after changing PHP versions.

My hosting provider is GoDaddy, and I am trying to determine whether this is related to a known issue with tagDiv Composer, a compatibility issue, or a server-related problem such as admin-ajax.php requests or ModSecurity interference.

Could you please advise if there are any known issues related to this behavior or recommend additional troubleshooting steps? If necessary, I can also provide administrator access, browser console logs, network request information, or any other details needed to diagnose the problem.

Additionally, could you let me know if there are any known compatibility issues with the current versions of Newspaper, tagDiv Composer, or GoDaddy hosting environments?

Thank you for your assistance. I look forward to your guidance on resolving this issue.

Best regards,

Jesse
traversecity.fm

I bought the theme just today and was trying to get the hang of things. When I click the “Edit with TavDiv composer” button, I get the following error.

Ooops… Error 404
Sorry, but the page you are looking for doesn’t exist.

Website: https://www.textilevista.in/

Hello TagDiv Support,
I’m using the Newspaper theme with td-composer – https://www.total-motorsport.com/
On the frontend, td-composer is loading these files:

ext-language_tools.js
ext-searchbox.js

from this path:
/wp-content/plugins/td-composer/css-live/assets/external/ace/
This causes the following console errors:

Uncaught ReferenceError: define is not defined
Uncaught ReferenceError: ace is not defined

Because of these errors, two things are broken in the header:

The hamburger menu does not open on mobile.
The search function in the header does not work.

I have already tried:

Clearing all caches
Re-saving the header template in Composer
Multiple attempts to remove the Ace scripts (both via PHP and JavaScript)

None of these fixed the issue. The site is otherwise stable.
Could you please investigate why td-composer is loading Ace Editor assets on the public frontend and provide a fix?
Thank you.

I haven’t found an answer to this: Some prebuilts use CSS animations for entire columns, such as:

td-text-animation td-right-animation td-order-2

If I’m correct, these classes are being defined within the CSS files of the TD Composer plugin. However, I’m wondering why they don’t seem to work on every page if I copy the classes and apply them to the “Extra Class” option of a column within the Composer. Any advice?