Hello,
When this message appears “ Errors at columns: 1(models) : 0(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)” then indeed it is a problem, most of the time the problem is from a code that is not compatible with our theme, therefore after you set it with tagDiv Composer and save the page/cloud template, the next time when you try to edit it, you’ll get that error. Please remove the code and see if the problem persists.
We have a guide for how to investigate this problem and fix it -> https://forum.tagdiv.com/tagdiv-composer-not-working/
You can try to add your code in Theme Panel -> Analytics/JS Codes => https://www.screencast.com/t/nou4AMaBhSMn
Also, you can use the cloud templates for header and footer, whence you can import one, and with tagDiv Composer, you can edit and style it as you wish.
Let us know about your results!
Thank you!
Hello,
On a clean install, I’ve beein importing Mintyside Pro templates and for one of them (the footer template) the TagDiv Composer is not active / available (template cannot be edited with TagDiv – however, at the time of import, I was able to do it). For all the other templates on the “Cloud Templates” tab, TagDiv Composer is working. How to solve it?
Thanks.
a
the footer templates does not have the button to be edited in the backend
Needing to edit the footer for each separate page or page template is obviously not the intended or expected behavior.
Will this bug be fixed anytime soon? Can you please provide a patch in the meantime?
Thanks!
Hello,
The footer template can be edited only from the frontend, edit a page/post template with tagDiv Composer and go down to the footer, or if you want to assign one, use the Manager => https://www.screencast.com/t/GllWehU3l (the footer templates does not have the button to be edited in the backend).
We were talking about this in this topic here: https://forum.tagdiv.com/topic/how-to-edit-footer-template-default-pro-by-tagdiv-composer/
Hope this helps you!
Thank you!
I have the same problem. All the other templates can be edited with the TagDiv Composer. Only the footer template does not have this option.
Hello,
The footer template can be edited only from the frontend, edit a page/post template with tagDiv Composer and go down to the footer, or if you want to assign one, use the Manager => https://www.screencast.com/t/GllWehU3l (the footer templates does not have the button to be edited in the backend).
Let me know the result!
Thank you!
Hello, in cloud template, how to edit Footer Template – Default PRO by TagDiv composer? I can not find option for TagDiv composer, but at the same time can see TagDiv composer option for other cloud templates, what’s the problem and how to fix it?
Thank you!
I have just installed prebuilt website. But Footer template has not “Edit with tagDiv Composer”. All other templates have it. How can I edit footer Template with tagDiv Composer?
Thanks
Hi Emintexno, please check to see if the code for fonts is still there, if not you can set theme again -> https://forum.tagdiv.com/how-to-add-icons-in-menu/ if there is still a problem, please provide me a link to your website.
2. As for the footer, the theme has some pre-made footer templates with blocks that can not be edited, you can add only extra widgets in footer section, if you want to have control over the elements from footer, please use a footer like footer style 2, 3, 6 and add the blocks widgets you want to display. -> https://i.imgur.com/OvP5F6S.png -> https://i.imgur.com/JCvz78U.png -> https://forum.tagdiv.com/newsmag-footer-templates-2/
Thank you for your understanding!
Hello,
If you have Standard Prebuilt Websites you can do the change in Theme Panel -> Footer -> Sub Footer => https://www.screencast.com/t/aa994RDz or if you have Pro Prebuilt Websites with Footer Template from Cloud Library can edit with tagDiv Composer => https://www.screencast.com/t/NfLmOMH4 , add element -> Row => https://www.screencast.com/t/uyhT5kVE, and in inner row->inner column, add Inline Text => https://www.screencast.com/t/rS2RiW7SWT.
Hope this helps you!
Thank you!
Hi,
The default Google Fonts: Open Sans and Roboto.fonts can be enable/disable from here -> https://imgur.com/eViu8D4 those are use for classic elements and templates. For pro it can be set only with tagdiv Composer.
The footer template can be edited only from frontend, edit a page/post template with tagDiv Composer and go down to footer, or if you want to assign one, use the manager -> https://i.imgur.com/Q5PeHkp.png (the footer templates does not have the button to be edited in backend).
Let me know the result!
Hi Calin,
Thank you. I’m using Cloud templates. I checked each single section of the homepage (where GTMetrix tell me that I also have the Roboto font: https://imgur.com/a/ilRtOqD). In some sections I specified Open Sans font, in the others I have “Def” as default font. So, what is used as Def font? Where is it specified?
Anyway, as Footer section I’m using the “Footer – COV-19 Italy Report PRO” but I can’t edit it with Tagdiv Composer, so I can’t check which fonts it’s using. Take a look: https://imgur.com/a/ilRtOqD
What can I do?
Thank you.
Hello!
You can only modify the footer with TagDiv Composer if you go to a page where it is assigned and edit that page with TagDiv Composer, and then you will have access to the footer also.
Also, it is normal to appear right there with no settings because those settings are for the default footer templates which you can not edit with TagDiv Composer. For example, if you will select there a default template you could see the setting on, but only for them and not for a PRO footer which is a cloud template.
Thank you!
Hi Vlad,
Thanks for touching base. We managed to address those issues as well in the meantime, but thanks for the suggestion.
Thanks again for your input, and kind regards.
Edit (for other people who may be facing similar issues): We found out the footer and headers were overridden by the mobile pages created through the tag div composer (left hand side panel, top options). Once a mobile page is created, settings for those should be set separately through the cloud templates, and applied to those as well. At least that’s what did the trick in our case.
Hello!
A demo theme you should be able to edit with TagDiv Composer or set from Website manager which header or footer you need right there. Read more about TagDiv Composer here: https://forum.tagdiv.com/tagdiv-composer-tutorial/
If you created the mobile pages with TagDiv Composer, then when you install Mobile Theme plugin, your pages will be overwritten by the plugin.
The Mobile Theme is a performance optimized theme included in the Newspaper main theme and it loads only for mobile devices. It comes with it’s own templates for page, post, category, etc so your current templates from the desktop theme will get converted to the mobile theme layout. For more details, please take a look here: https://forum.tagdiv.com/the-mobile-theme/
Thank you!
Hi Calin
Okay sorted Social Share problem. The image issue still exists. The second time we have disabled all plugins. Still can not add an image to a temple, in fact, we cannot seem to save any changes to any templates. The header and footer save, the content doesn’t.
I have sent you an invite to create a password on our cPanel for Medika and will email you logins for the WP site.
Calin, we are clearly on different pages. Here is my issue which I posted again this morning.
The site may look fine to you however the social media share isn’t working. It is completely broken, we don’t have either Pinterest or Wahtsapp. Those are the only four platforms the plugin shows in the front end and the option to add any addresses in the Composer has been completely blanked out.
Our problem is the Composer. It refuses to add ANY image to a template or update the page settings. It only saves the header and footer, not the content, so we cannot make any changes to existing templates, new ones don’t work either.
The reason the sticky header is no more is that it won’t allow us to repair the header by adding an image back to the template, so I have had to disable it. Trust me this isn’t a plugin issue, we have disabled everything. Also, we’ve noticed that Profilegrid has lost some of its functionality since the TagDiv upgrade.
Again, we are WP latest version, tagdiv and PHP latest versions, 512k ram allocated. No other issues, site functions, but we cannot change anything using composer.
If we disable the Standard pack sections disappear of the site, new Pro sections that should be visible. Tried a pro template to see if that would make any difference as we are running on Medical one, no change, just crashed older pages.
Hello !
You can create your sidebar using tagDiv Composer if you use cloud library templates: https://www.youtube.com/watch?v=fa7GenCHcBU&t=1s
On mobile you can achieve that using theme panel – Ads – Footer Ads.
Thank you !
After the most recent update and also the previous one, the Composer will not allow us to update any images or change blocks in existing templates. It saves headers and footers but not content. Huge sections are also missing from the block options within the composer, such as the ability to select social media icons for the single post share tool.
I am running the latest WordPress and Newspaper. 512 Meg memory allocated and latest PHP. Tried reinstalling and disabling plugins, no change, tried downgrading WP and Newspaper, no change. We are trying to update templates and remove older blocks to activate a new Pro temple. Hugely frustrating.
Whenever I go to Cloud Templates and click on New, I get an error message that says: “Invalid reply from server endpoint.”
I want to be able to use widgets in the footer but can’t figure out how to do that using the current template I’m using. The site is http://daddyhooding.com.
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
good day i nuy newspapaer theme yesterday and now am setting my wordpress, but in the theme panel the footer have no option to configure it, then when i go to cloud template to get some footer i click add new it then say loading templates then i getting an error saying
”Invalid reply from server endpoint” please help i need to set up the footer for my website
good day i nuy newspapaer theme yesterday and now am setting my wordpress, but in the theme panel the footer have no option to configure it, then when i go to cloud template to get some footer i click add new it then say loading templates then i getting an error saying
”Invalid reply from server endpoint” please help i need to set up the footer for my website
Header:
Although I have opened Website Manager and set Mobile Menu Sticky as enabled, and saved, when I open the website on an actual mobile device and scroll down, the sticky header does not appear. Inside the TDC environment, when previewing the website on a mobile device, the sticky header is there and functions as set and expected.
Footer:
I open TDC and select the footer row. Then, right between the settings tabs and the search box, I click on the mobile icon to edit those settings. The styles and settings which are displayed in the TDC preview window do not represent the ones applied in reality. Yes, I’ve saved the changes, cleared the cache, minified JS and CSS versions, and even browsed the page from a new and single incognito session from an actual mobile device, and in chrome’s and firefox’s dev tools. For once, the background color is different (light blue in TDC vs Black in reality), and then the structure of the footer is different also.
In website manager, under the footer section, I only see two options; Global Template and/or No Footer. Currently applied I have the Footer Template – Default PRO.
Then in cloud templates I open the Footer Template – Default PRO to edit it, but “Edit with Tag Div Composer” button is not available. In the textarea I can only see gibberish, which I know is not gibberish really, but a nightmare to work with at the least.
Lastly, in the admin pages, under Newspaper > Theme panel > Footer, I see no other option other than the CLOUD LIBRARY TEMPLATE section, but the Footer Settings or any other section besides the CLOUD LIBRARY TEMPLATE, as described here ( https://forum.tagdiv.com/footer-templates/ ), are nowhere to be seen.
The theme version is 10.3.7
Please advise as you see appropriate.
Hello!
You can simply edit your page elements using TagDiv Composer plugin. Check our guides here:
1. About TagDiv Composer : https://forum.tagdiv.com/tagdiv-composer-tutorial/
2. About headers : https://forum.tagdiv.com/header-manager/
3. About footer : https://forum.tagdiv.com/footer-templates/
If you have any other questions or issues, contact us!
Thank you!
