Search Results for 'composer'

Dear Bettina,
we have the same problems with the tag div composer. Did you solve the problem in the latest update, so that we can make a clear new installation and have a theme without vulnerable files? If yes please provide the version number without these known problems.
Thanks
Dennis

I’m receiving the same error on a fresh website (no other plugins etc)

27-Sep-2023 12:16:35 UTC] PHP Parse error: syntax error, unexpected ‘array’ (T_ARRAY), expecting function (T_FUNCTION) or const (T_CONST) in /home/wwwcypruswedding/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_resources_load.php on line 8
[27-Sep-2023 12:18:05 UTC] PHP Parse error: syntax error, unexpected ‘array’ (T_ARRAY), expecting function (T_FUNCTION) or const (T_CONST) in /home/wwwcypruswedding/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_resources_load.php on line 8
[27-Sep-2023 12:18:13 UTC] PHP Parse error: syntax error, unexpected ‘array’ (T_ARRAY), expecting function (T_FUNCTION) or const (T_CONST) in /home/wwwcypruswedding/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_resources_load.php on line 8
[27-Sep-2023 12:18:29 UTC] Cron reschedule event error for hook: td_instagram_cron_job, Error code: invalid_schedule, Error message: Event schedule does not exist., Data: {“schedule”:”3hours”,”args”:[],”interval”:10800}
[27-Sep-2023 12:20:20 UTC] Cron reschedule event error for hook: td_instagram_cron_job, Error code: invalid_schedule, Error message: Event schedule does not exist., Data: {“schedule”:”3hours”,”args”:[],”interval”:10800}
[28-Sep-2023 06:03:00 UTC] Cron reschedule event error for hook: td_instagram_cron_job, Error code: invalid_schedule, Error message: Event schedule does not exist., Data: {“schedule”:”3hours”,”args”:[],”interval”:10800}

I want to share an update on resolving an issue I encountered, hoping it can assist others who might face a similar challenge and spend a considerable amount of time troubleshooting it. Although it is essential to first consider the recommended steps provided by the TagDiv support team, my solution might be an additional resource.

I discovered that a modal popup embedded in my footer was the culprit. I suspect that something went awry during a recent upgrade. This embed consisted of custom code, replicated from a text on a composer page. I had a Gravity Forms embedded on this page for a newsletter signup. Initially, I created the modal popup page using the Gravity Form shortcode and copied the composer code. However, it is crucial to note that I copied this code via the “edit” option, not “edit in composer,” into the custom code box for my modal popup in the footer.

For reasons I couldn’t initially understand, this was generating an error: Error at zones: 6(models) : 7(dom). I resolved the issue by manually entering the footer and deleting the text in the custom-code=”” field, then saving the file. This allowed me to access the footer via composer and make the necessary adjustments to the pages.

Interestingly, I pinpointed the error to the footer through a process of elimination. While in composer, I first changed the header to “no header” but still encountered the same error. It was only when I selected “no footer” that the error disappeared. This revelation led me to the conclusion that the error originated in the footer.

I believe the modal pop-up custom code triggered this issue. I’m sharing this experience in the hope that it might streamline the troubleshooting process for others facing similar challenges.

Lastly, I want to express my gratitude to the TagDiv staff. Their diligent support in navigating the intricacies of a complex yet powerful theme like Newspaper, which I consider to be one of the best available, is immensely appreciated.

I’m experiencing the problem Error at zones: 6(models) : 7(dom) that I’m convinced began after the most recent update. I use the Newspaper theme on several websites, but this issue has only appeared on one of them. The error is present on every page, and persists even when I create a new page to test it.

I’ve spent considerable time searching for a solution and have tried deactivating and testing each plugin to identify the source of the problem, but to no avail. I have also attempted uninstalling and reinstalling the composer, a step that resolved the issue in the past, but it hasn’t been effective this time.

I reviewed the WP logs and couldn’t find any related entries that could potentially be causing this problem. I distinctly remember editing my site not too long ago without encountering any issues, which leads me to believe that something in the latest Newspaper update might be the culprit.

In my search for a solution, I came across several threads at the end suggesting to contact support with admin credentials, but there hasn’t been any update on that front. If anyone has encountered this issue and found a resolution, could you please share your insights? Your assistance would be greatly appreciated as I am eager to resolve this persisting problem.

• This reply was modified 2 years by elvisfrog.

In TagDiv Composer, the pages are exactly as we designed them, which is why I am surprised. It’s when the pages are displayed on the live website that there is a problem with the design and content.

Yesterday, we downgraded to 12.5.1 and the live site design returned to normal. All the problems that we were seeing in 12.6 disappeared with the downgrade.

We will stay with the downgraded version until the problem with 12.6 is solved, because this is a live site that we are continually working on to load faster.

live-css is a plugin used by td-composer that creates a backdoor for anyone to add malware. You need to fix your plugin.

function td_live_css_on_rest_api_init() {
$namespace = ‘tdw’;
register_rest_route($namespace, ‘/save_css/’, array(
‘methods’ => ‘POST’,
‘callback’ => ‘td_live_css_on_ajax_save_css’,
‘permission_callback’ => ‘__return_true’,
));
}
should be false