- NewsmagHow to update a plugin
- NewspaperHow to update a plugin
- NewsmagHow to update the theme
- NewsmagHow to update the WPBakery plugin
- NewspaperHow to update the WPBakery Page Builder plugin
- NewspaperHow to Update the Newspaper Theme
- 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
Hi,
Could you please assist me.
i use your theme on my website – https://www.greencitytimes.com but the blog posts are not displaying on mobile anymore.
if you view this blog post on a mobile device – https://www.greencitytimes.com/smart-city-technologies/ you will see the content does not display, but the content displays on the desktop version.
I have updated all plugins, i have also updated the theme still the issue persists.
Could you please help!
Hi Meytar Zeevi,
From what I can see, this task has been marked as complete, but the strange thing is that I don’t see it being listed on the release notes.
What I can suggest is to try a staging, or make a backup of the site and contact us by email (contact@tagdiv.com) to make the update and see if everything is ok.
Thank you!
Hello,
I think that the plugin update caused this issue. Please try to check one by one, and find the culpirt plugin.
Thank you!
Buna,
Cred că actualizarea pluginurilor a cauzat această problemă. Vă rugăm să încercați să verificați unul câte unul și să găsiți pluginul care cauzeaza problema.
Multumesc!
Hello,
The license is for a lifetime and you will have access to updates.
-> https://themeforest.net/licenses/standard
-> https://themeforest.net/licenses/terms/regular
The only thing that will expire is your support.
Thank you!
Buna ziua,
Filtrul este activ. Nu am facut nicio modificare. Probabil ca am un plugin conflict, desi nu am niciun plugin nou fata de momentul functionarii corecte. Am efectuat doar update-urile pluginurilor
Multumesc!
Hello!
I did and then had to update manually. Hopefully this will be fixed and they will update automatically. Until then, thanks for the work around!! Have a great weekend!!!
Hi,
Did you disable the extra plugins? You can try to update the plugins manually -> https://forum.tagdiv.com/newspaper-how-to-update-a-plugin/
Thank you!
Hi,
We fixed the issue https://tagdiv.com/newspaper/?utm_source=forum&utm_medium=menu&utm_campaign=forum_loggedin&utm_content=92178 -> https://i.imgur.com/il0AUG0.png by this
wasn’t updated https://patchstack.com/database/vulnerability/td-composer/wordpress-tagdiv-composer-plugin-4-1-csrf-to-xss-vulnerability
Thank you!
I am having the same issue with composer, cloud library, newsletter, standard pack. They all threw an ajax error when I updated to 12.5. I uninstalled, deleted, cleared cache and reinstalled. and the same. I also tried in Firefox and Edge and the result was the same.
I’ve had a hard time documenting this issue and I hope you can (and should) help me fix it.
It all starts from the new update from version 12.4 to 12.5 in Newspaper.
The problem appears in the “Flex Block” module when using “Pagination” (whatever the selection) and trying to filter by “Post Type:” with the “Category filter:” option with the “Single – Related from taxonomy” option ” and a specific taxonomy to be displayed within the content type is added in the “Single – Related from taxonomies:” box.
First I leave you the video so you can see how it works correctly in version 12.4 and it was running correctly before the update to 12.5. Let’s go there! (please note the time and day below to see that it is only the update that matters). We will do everything on the same post so that there are no doubts https://www.trebol-apuestas.com/tragaperras/ancient-script/
Watch video — https://www.loom.com/share/88f2105a9de84a94a26f73fb53d06b27?sid=1ecaa2b1-df53-46eb-b8c6-5cb36729a8ec
Not all right! Games that are organized by CPT UI and that in turn penetrates ACF with the personal field “study”.
Now we are going to version 12.5 and for this we will see how it works first and then I will show it in depth with another video. (Remember we’re only 5 minutes after the previous video and having installed 12.5, all with the TAG DIV compositor the same!)
Watch video — https://www.loom.com/share/4a4c4cb1cf8349f28f8db52785b050aa?sid=bbbd3b21-b633-4668-a5d8-64b1b8b9eded
See, it already does what it wants, and it doesn’t filter by CPT UI with ACF once the scroll button is clicked as before.
Now, so that there is no doubt that it is not working, I am going to demonstrate it with the composer creating the 3 modules in this version 12.5 so that it can be seen that it REALLY UNDERSTANDS what it has to show but that it does not know how to do it when it is displayed, click next, show more and infinite load. As you will see in the video there are 16 games (slots) related to that CPT UI and ACF in this particular post, because when any type of pagination is added it stops working in version 12.5 (because I remember, in version 12.4 if it worked).
Let’s go there!
Watch video — https://www.loom.com/share/2d6a6469dc79491abde57d70f72b0c66?sid=5762832b-a76d-496d-ba4b-e89a1f756118
Let me know your solution!
Remember you can see everything in the post https://www.trebol-apuestas.com/tragaperras/ancient-script/ so that it does not affect SEO I have to put the other slots with only one module so you can review the problem in that entry.
I am getting an error which is infinite loading whenever I want to update page or post. There is some issue with AMP which is related to The error message indicates a PHP Notice related to the incorrect usage of the amp_has_paired_endpoint function in WordPress. The notice mentions that the function was called incorrectly while the AMP (Accelerated Mobile Pages) feature is disabled via the amp_is_enabled filter. The notice also indicates that the service ID “paired_routing” is not recognized and cannot be retrieved, which could be causing the issue. To resolve this error, you may need to review the code where the amp_has_paired_endpoint function is being called and make sure it is used correctly. Additionally, check if the AMP feature is properly enabled or disabled based on your requirements. If you are unsure about how to debug and fix the issue, you can refer to the provided link “Debugging in WordPress” for more information on troubleshooting PHP notices in WordPress.
12.5 with all the all the latest updates.
I-Themes security reports are being emailed to all their users reporting this as high severity vulnerability and advising to deactivate this essential plug-in.
As of Aug 2, it’s being reporting it as unpatched.
Hello,
I’ve come across a confict that the tag div composer plugin is having with the ultimate membership pro plugin (https://codecanyon.net/item/ultimate-membership-pro-wordpress-plugin/12159253) and it’s extension called wp workflow restrictions.
The extension is supposed to restrict the number of posts that a visitor can view before they are redirected to a paywall. Unfortunately, the tagdiv composer plugin is overwriting the code of the plugin and preventing it from executing. This is a recent problem that didn’t previously exist so it’s most likely a result of one of the most recent tag div updates.
I’ve got in touch with the UMP development team and they said they’d be happy to send you the technical data of this conflict. Are you happy to collaborate with them to solve this issue?
Thank you,
Howard
Hello,
WE are using Newspaper theme for our news site from April, and we are very happy with it. Last week on the 26th of July we realised that our website had been collapsed. After checking the backend, we found that it seemed, as we had not activate the license. We activated it again, reinstalled the plugins, and after a lot of settings our site worked well again. Unfortunatelly it happened the second, or third time (the first time when it happened was during the construciton time, so that is why we are not sure).
We have checked and this happens after updating the theme.
Could you please help us, how can we avoide the website collapse after the next update.
Thanks and best regards
Ivett
On reflection a screenshot does not add anything – all the information is drawn from iThemes Security weekly report.
This is what they say about their report and what they have to say about this weeks:
Unpatched plugins and themes are the #1 reason WordPress websites get hacked. Our weekly WordPress Vulnerability Report covers recent WordPress plugin, theme, extension, and core vulnerabilities. Learn when to apply updates or replace software products that have unpatched vulnerabilities.
Since last week, 94 total vulnerabilities emerged in public disclosure. They may affect over 7 million WordPress sites. There are 56 plugin vulnerabilities with security patches, so run those updates!
Additionally, there are 35 plugin vulnerabilities and three theme vulnerabilities with no patch available yet.
If you use an unpatched plugin or theme, check their vendors’ intentions and progress on a security release. Suppose no patch is forthcoming or the vulnerable software has been marked “closed” and dropped from the official WordPress theme and plugin repositories.
In that case, you should consider deactivation and removal in favor of alternative solutions.
This is the warning for this week on tagdiv composer:
PLUGIN
tagDiv Composer
PLUGIN SLUG
td-composer
VULNERABILITY
Cross Site Request Forgery (CSRF)
PATCHED IN VERSION
No Fix
SEVERITY SCORE
High
CVE
2023-39166
There is no patch available yet, deactivate.
This is a serious warning that goes out to all their customers. Please advise.
Thanks
Jude
Hello!
We will investigate it and if there is an issue from our side, then we will add the fix in one of the future updates.
Thank you for understanding!
The Ithemes security was yesterday, after the latest tag div update
Hello,
Please let me know what version of the theme you have. If you don’t have the latest version of the theme 12.5, then please update it.
My recommendation is that before updating the theme to make a full backup for the database and current website, disbale the extra plugins during the update process, after that update the theme manually – https://forum.tagdiv.com/how-to-update-the-theme-2/ (after the theme update, make sure that the needed plugins are installed, like tagDiv Composer, maybe tagDiv Standard Pack and tagDiv Cloud Library).
In the worst cases, the settings in the theme panel may be lost (there have been isolated cases), in these cases, after the theme plugins that were previously used are activated, you will have to use a backup for the theme panel -> https://forum.tagdiv.com/import-export-theme-settings/
Thank you!
Hi,
Usually, this happens with cache plugins. If the cache plugin does not have mobile support then the mobile theme version can be delivered instead.
The solution would be to use the recommended WP Super Cache plugin instead and activate these settings (especially the mobile device support): https://forum.tagdiv.com/cache-plugin-install-and-configure/
Using our theme, you can choose from 3 mobile versions
-> mobile responsive => https://www.screencast.com/t/oJ2ShOp47
-> mobile theme plugin => https://forum.tagdiv.com/the-mobile-theme/
-> mobile page => https://tagdiv.com/newspaper-10-3-7-update-brings-customizable-and-fast-mobile-pages/
Suppose you created the mobile pages with tagDiv Composer. In that case, when you install the Mobile Theme plugin, your pages will be overwritten by the plugin (the mobile theme comes with its templates for page, post, category, etc so your current templates from the desktop theme will get converted to the mobile theme layout, the page content is made without builders in mobile editor => https://www.screencast.com/t/xbgZG8kH also, the options that are provided to edit the mobile theme version are limited (this keeps the things simple)).
This is a video about Responsive Newspaper Theme, AMP & Mobile Theme, Mobile Pages & Templates -> https://www.youtube.com/watch?v=SpGkOnJeNZY
So, the mobile responsive is what you see then that you select the viewport on phone => https://www.screencast.com/t/matV17hH, so some settings may apply for each viewport(where is the border blue), and others are not(where the border is black).
The mobile page has the mobile templates from Cloud Library => https://www.screencast.com/t/YCcZ8rL8
Mobile responsive version of the theme and the mobile page editor can be edited with tagDiv Composer, the mobile theme plugin not.
For example, you can have the mobile theme plugin activated and use the mobile page/mobile responsive version for the homepage/pages, but for the categories pages/404 page you can’t use the mobile page/mobile responsive version if you have the mobile theme plugin activated.
So, if you want to design the pages with tagDiv Composer, you can use the mobile page or mobile responsive version.
Thank you!
This high severity vulnerability to still being reported with recommendation to delete the essential plug.
Are there any updates on this?
tagDiv Composer
PLUGIN
tagDiv Composer
PLUGIN SLUG
td-composer
VULNERABILITY
Cross Site Request Forgery (CSRF)
PATCHED IN VERSION
No Fix
SEVERITY SCORE
High
CVE
2023-39166
The vulnerability has not been patched. You should deactivate the plugin.
Hello! ever since i update this theme .. i had a problem with sharing it on twitter
ERROR: Fetching the page failed because the request timed out.
https://cards-dev.twitter.com/validator
i use facebook debug it works on fb but on twitter it wont
Indeed it seems to work now on iOs. I have no idea why -_-
For the hidden X, I have updated my CSS and it is now showing. However, the original problem I had was that I wanted to remove the social media icons and the log-in area from the mobile menu. But I couldn’t find the way to do it.
If you could tell me how to remove those, then I would be able to remove my weird CSS 🙂
Hi
Since I updated the 12.5 my homepage is showing incorrectly
But pages 1 plus deep are showing correctly https://livingunrefined.com/100-crazy-things-to-do-before-you-die/
This field called td_wp_editor (meta field) and this is the function for exposing it to the REST API.
function expose_td_wp_editor_field() {
register_rest_field(‘page’, ‘td_wp_editor’, array(
‘get_callback’ => ‘get_td_wp_editor_value’,
‘update_callback’ => ‘update_td_wp_editor_value’,
‘schema’ => null,
));
}
function get_td_wp_editor_value($object, $field_name, $request) {
return get_post_meta($object[‘id’], $field_name, true);
}
function update_td_wp_editor_value($value, $object, $field_name) {
if (!empty($value) && is_string($value)) {
return update_post_meta($object->ID, $field_name, wp_kses_post($value));
} else {
return delete_post_meta($object->ID, $field_name);
}
}
add_action(‘rest_api_init’, ‘expose_td_wp_editor_field’);
I really look forward to when you will be replaced by chat bots, they at least answer quickly and to the question asked. Regards!
still document.write() error is remain please update us.
url: https://www.learningall.com/
https://pagespeed.web.dev/analysis/https-www-learningall-com/0b8ip9p2as?form_factor=desktop
