- Apitd_api_top_bar_template::update_key
- Apitd_api_top_bar_template::update
- Apitd_api_single_template::update_key
- Apitd_api_single_template::update
- Apitd_api_footer_template::update_key
- Apitd_api_footer_template::update
- Apitd_api_smart_list::update_key
- Apitd_api_smart_list::update
- Apitd_api_thumb::update_key
- Apitd_api_thumb::update
- Apitd_api_category_top_posts_style::update_key
- Apitd_api_category_top_posts_style::update
- Apitd_api_category_template::update_key
- Apitd_api_category_template::update
- Apitd_api_module::update_key
- Apitd_api_module::update
- Apitd_api_block::update_key
- Apitd_api_block::update
- Apitd_api_header_style::update_key
- Apitd_api_header_style::update
Hi Calin. No that isn’t the problem at all. Images cannot be updated or changed through Tagdiv composer when you’re working with templates. Simply doesn’t work. Social media share the s similarly affected. Tried rollbacks etc with different versions of WP, no different. I assume you guys mad changes to the TagDiv composer plugin as well, and this is where the problem lies.
The images on the site are fine except for logo on sticky menu. Gone and now can’t put it back.
Hi all,
we buyed a license of the Newspaper theme in September 2018, updates have been made up to version 9.6.
At the moment I can’t update the theme to the latest version (10.3.9) due to lack of time and because the site using it has many customizations to test.
However, I have to update WordPress to the latest version (5.6), are there any compatibility issues or can I proceed safely?
Thanks,
acd.
Hi sloope, so after the theme update you clear the cache and purge the CDN and the problem with the menu appear. Was this problem there when you were logged?
There were reported from some users some jquery problems, if is the same for you, then those can be fix for the moment using the Enable jQuery Migrate Helper plugin and try this option – https://www.screencast.com/t/WYlKJVLi Clear all the caches (also the browser cache).
If there are still some problems, please let me know!
Thank you!
Hi ray274, do you use child theme? also did you checked the plugin conflicts? Also dis you made any changes in theme or plugin files? because those are removed when the theme is updated.
Please provide as many details you can about the problems, also a link to your website will help.
Thank you for your understating!
Hi,
I have updated Newspaper theme to 10.3.9 version with WP 5.6. I have an issue with tag in the post. If I try to add a tag in a post via small window in the right side panel nothing happen. The totally of my posts use tag so How can overcame this issue?
the code works, the problem is that every time u update the theme, the code disappear and I must fix editing the functions.php
Hi I have updated to WordPress 5.6 and the Newspaper 10.3.9. Now all the post images (Featured Images) in homepage disappeared (these problem is showing only in Firefox). The site is http://www.inpressmagazine.com. Minimizing the window the images appear but this did not happen before the update.
Hi,
Please make a full backup and update to Newspaper v10.3.9 this should fix the problem. Just make sure that the Instagram account is set -> https://forum.tagdiv.com/instagram-widget/
If there is still a problem, let me know!
the same issue here. After update submenus dont work
Hi,
This problem will be solved for the coming update!
If there are other problems, let us know!
Thank you!
Hi Guys,
we have just updated to the latest version of your great theme and to WordPress 5.6
Now we just have an error on the website stating:
Fatal error: Uncaught Error: Class ‘td_util’ not found in /www/htdocs/xxx/agency/wp-content/themes/Newsmag/functions.php:52 Stack trace: #0 /www/htdocs/xxx/agency/wp-includes/class-wp-hook.php(287): {closure}(false, Object(WP_Query)) #1 /www/htdocs/xxx/agency/wp-includes/plugin.php(212): WP_Hook->apply_filters(false, Array) #2 /www/htdocs/xxx/agency/wp-includes/class-wp.php(658): apply_filters(‘pre_handle_404’, false, Object(WP_Query)) #3 /www/htdocs/xxx/agency/wp-includes/class-wp.php(748): WP->handle_404() #4 /www/htdocs/xxx/agency/wp-includes/functions.php(1291): WP->main(”) #5 /www/htdocs/xxx/agency/wp-blog-header.php(16): wp() #6 /www/htdocs/xxx/agency/index.php(17): require(‘/www/htdocs/w00…’) #7 {main} thrown in /www/htdocs/xxx/agency/wp-content/themes/Newsmag/functions.php on line 52
Any info on what to do here?
Hi,
Yes, there is a new theme version that is compatible with WP 5.6, make a full backup and try the new update -> https://tagdiv.com/update-newspaper-theme/
Thank you!
Hi,
There is a new version of Newspaper that was tested with WP 5.6 -> this can be updated like this -> https://tagdiv.com/update-newspaper-theme/
Thank you!
Similar issue here, the menu doesn’t show anymore on the category pages, I didn’t change or add any plugins the past weeks and the problem started after the last update.
Hi,
Yes there will be some updates for theme compatibility with WordPress 5.6 and php 8, unfortunately I can not say for sure when those will be made.
We try to make a theme update in this month.
Thank you!
Hi ghoangit,
This situation appear if you make update to last version of WordPress 5.6, then the button for composer is remove from Gutenberg, but the pages still can be edited from frontend or from pages -> https://i.imgur.com/7LgjYE1.png
The button will be add back soon!
Thank you!
Replying so I can get an update once this issue is fixed. 🙂
Thanks, it works. But don’t know why there is an “extra css” after update the theme and required plugin.
Beside, with the same website, I don’t know why it keeps showing the mobile view (again, not mobile theme and AMP) even I use Google Chrome in my desktop.
Thanks!
Dear Tagdiv support,
hope you’re well and healthy!
Unfortunately, today, after autoupdating the WP version to 5.6, the following content disappeared at frontend:
1) all the images inside EVERY post
2) all the thumbnails of EVERY post (also videoposts).
3) the background image.
4) In addition, the main menu bar was not fixed anymore at the top while scrolling down.
After restoring the previous WP version 5.5.3, fortunately all the images re-appeared again (and the menu bar was fixed again).
Some info on the plugins installed:
a) almost every plugin updated, except for Newspaper theme 10.3.2 (instead of 10.3.9);
b) other plugins:
Auto Image Attributes From Filename With Bulk Updater – active at last version
Media File Renamer – deactivated but updated at last version
Regenerate Thumbnails Advanced – deactivated but updated at last version
ShortPixel Image Optimizer – deactivated but updated at last version
Please find a screenshot attached of how the thumbnails appeared.
Please, if you think it’s needed to update Newspaper to 10.3.9 to avoid this issue (Wodrpress will autoupdate in 48 hours) can you handle the Newspaper update?
Thanks and regards!
Angelo
It seems to be working again after the last update…
Hello, after updating the theme the menu was no longer visible.
This is how it looked before: https://ibb.co/61YbGc7
This is what it looks like now: https://ibb.co/khRWytY
I have noticed that in Chrome tools if I deactivate this option (opacity), the menu is visible again.
https://ibb.co/dfvrPMc
How can I do it from the theme panel?
Or should I wait for an update?
Good afternoon,
Today, WordPress automatically updated to 5.6 and now, when clicking “Add New Post,” I get all of the following error messages (See at the end.) I tried downgrading to the previous version 5.5.3, but that didn’t work. I also disabled ALL plugins except for tagdiv plugins and the error messages still appear. The only plugin that makes it go away is disabling the tagdiv composer plugin. I can then edit new posts, but it breaks the frontend of the site so that is not a solution.
See error messages below:
Notice: register_rest_route was called incorrectly. The REST API route definition for td-cloud-library/new_template is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/montanadailygazette.com/wp-includes/functions.php on line 5311
Notice: register_rest_route was called incorrectly. The REST API route definition for td-cloud-library/td_cloud_proxy is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/montanadailygazette.com/wp-includes/functions.php on line 5311
Notice: register_rest_route was called incorrectly. The REST API route definition for td-cloud-library/download_image is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/montanadailygazette.com/wp-includes/functions.php on line 5311
Notice: register_rest_route was called incorrectly. The REST API route definition for td-cloud-library/ajax_autoload is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/montanadailygazette.com/wp-includes/functions.php on line 5311
Notice: register_rest_route was called incorrectly. The REST API route definition for td-composer/do_job is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/montanadailygazette.com/wp-includes/functions.php on line 5311
Notice: register_rest_route was called incorrectly. The REST API route definition for td-composer/save_post is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/montanadailygazette.com/wp-includes/functions.php on line 5311
Notice: register_rest_route was called incorrectly. The REST API route definition for td-composer/save_history is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/montanadailygazette.com/wp-includes/functions.php on line 5311
Notice: register_rest_route was called incorrectly. The REST API route definition for td-composer/load_header_template is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/montanadailygazette.com/wp-includes/functions.php on line 5311
Notice: register_rest_route was called incorrectly. The REST API route definition for td-composer/update_header_template is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/montanadailygazette.com/wp-includes/functions.php on line 5311
Notice: register_rest_route was called incorrectly. The REST API route definition for td-composer/get_header_templates is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/montanadailygazette.com/wp-includes/functions.php on line 5311
Notice: register_rest_route was called incorrectly. The REST API route definition for td-composer/get_header_template is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/montanadailygazette.com/wp-includes/functions.php on line 5311
Notice: register_rest_route was called incorrectly. The REST API route definition for td-composer/decode_html_content is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/montanadailygazette.com/wp-includes/functions.php on line 5311
Notice: register_rest_route was called incorrectly. The REST API route definition for td-composer/get_image_url is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/montanadailygazette.com/wp-includes/functions.php on line 5311
Notice: register_rest_route was called incorrectly. The REST API route definition for td-composer/get_image_id is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/montanadailygazette.com/wp-includes/functions.php on line 5311
Notice: register_rest_route was called incorrectly. The REST API route definition for td-composer/save_parts is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/montanadailygazette.com/wp-includes/functions.php on line 5311
Notice: register_rest_route was called incorrectly. The REST API route definition for td-composer/change_template_name is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/montanadailygazette.com/wp-includes/functions.php on line 5311
Notice: register_rest_route was called incorrectly. The REST API route definition for td-composer/save_header_mobile_menu is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/montanadailygazette.com/wp-includes/functions.php on line 5311
Notice: register_rest_route was called incorrectly. The REST API route definition for td-composer/load_footer_template is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/montanadailygazette.com/wp-includes/functions.php on line 5311
Notice: register_rest_route was called incorrectly. The REST API route definition for td-composer/update_footer_template is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/montanadailygazette.com/wp-includes/functions.php on line 5311
Notice: register_rest_route was called incorrectly. The REST API route definition for td-composer/get_footer_templates is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/montanadailygazette.com/wp-includes/functions.php on line 5311
Notice: register_rest_route was called incorrectly. The REST API route definition for td-composer/get_footer_template is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/montanadailygazette.com/wp-includes/functions.php on line 5311
Notice: register_rest_route was called incorrectly. The REST API route definition for tdw/save_css is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/montanadailygazette.com/wp-includes/functions.php on line 5311
Add New Post
Hi team,
I have been struggling with this issue since end of October and still do not have a fix. Yes, there was a lot of issues getting you access to my hosting site, but you have had this access somce 25th November, and since then I have heard nothing, despite many emails asking for an update.
PLEASE can someone help and resolve this issue.
Thanks,
Emma
Hi — thanks for the reply. As I mentioned, I had already tested for plugin conflict, checked system requirements, and followed the instructions in the links you provided; none of that worked until later in the day when the Composer started working again, so I’m good there.
I am, however, still having an issue with the main menu on the navbar. I was using a Cloud Template and after the update all of the menu text turned white. We’re using a white background so the links work but you can’t see them. I’ve tried deleting/re-uploading the Cloud template plugin and duplicating and renaming the previous template but it’s still white on white. Can you please advise on potential solutions? Thank you!
Try viewing in Google Chrome and Microsoft Edge browsers my images are showing fine in Google Chrome, however in Microsoft Edge the images show up when you keep refreshing the page, may be with the new wordpress 5.6 update Firefox is not responding that well, hopefully Tagdiv`s developers are on the case?
