Hi,
So you want to insert the code in the AMP header file, that would be here in this plugin file
– https://www.screencast.com/t/TAQGzA4Zldt
Be sure to test if the ads appear with a mobile or mobile emulator.
Thanks
Hi,
We could take a look at this, send us an email at contact@tagdiv.com and provide admin access, also cPanel if possible. Include a link to this topic in the email.
Hi,
That is an interesting discussion, however I can’t provide any specific details about how the theme will be adapted for Gutenberg or what exactly will happen. I am positive that when the time comes we will think of the best solution in the matter.
Hi,
I would suggest that you carefully check the custom CSS you used for the modifications. Without it the category page would look like this
– https://www.screencast.com/t/GLsHU5WSBGMv
The CSS you used is the cause of the problem. Remove it or modify it if possible.
Hi,
Usually a WP memory of 256M would be sufficient for most users. Woocommerce is a resource heavy plugin, they mention an 128M minimum
– https://docs.woocommerce.com/document/server-requirements/
– https://forum.tagdiv.com/requirements-for-newspaper/
If there is no need for modifications in your case, then you could try the solutions from these topics which solved some issues with the composer previosuly
– https://forum.tagdiv.com/topic/gray-page-tagdiv/
– https://forum.tagdiv.com/topic/javascript-error-td-composer-wont-load/
Let us know if these solve the problem.
Thanks
Hi,
Why not simply install the plugin by FTP, that would take about a couple of minutes. The theme plugins are provided in the theme package plugins folder
– https://www.screencast.com/t/C0rn9NLmbHo
Unzip the composer and upload it in the WordPress wp-content->plugins folder. That would be all there is to it.
There are many cases of this issue happening, a simple search on Google and this can be seen, also various fixes can be found
– https://www.google.ro/search?q=wordpress+the+plugin+does+not+have+a+valid+header&oq=wordpress+the+plugin+does+not+have+a+valid+header&aqs=chrome..69i57j0l2.3112j1j7&sourceid=chrome&ie=UTF-8
Hi,
The theme already has the wp_footer code – https://www.screencast.com/t/4aDwZIvU
So the problem you are having would be caused by something else.
Hi,
The missing option would have a simple explanation, you are using an older theme version than when the option was introduced
– https://themeforest.net/item/newspaper/5489609 (changelog at the bottom of page)
– https://www.screencast.com/t/axu4iVseE
I believe the option was also related to the current GDPR laws. I assumed you were using the latest theme version.
If you could provide a link to your website and mention the elements I should inspect I will take a look.
The facts are like this, if you want to disabled Google fonts update the theme first. After you disable them, the theme will not load any Google fonts anymore.
There are currently 3 custom font upload fields. I believe that will be increased to 5 in the coming update/updates. If these are not sufficient, then the better option between those I presented above would be to load the fonts with font face
– https://css-tricks.com/snippets/css/using-font-face/
– https://premium.wpmudev.org/blog/custom-fonts-css/
Thanks
Hi,
You must be using an older version of the theme and also plugins, that version of the Visual composer (now WPBakery page builder) would be a couple of years old.
We introduced the tagDiv composer in version 8.0 of the theme as the new main page builder, please check the changelog at the bottom of this page
– https://themeforest.net/item/newspaper/5489609
Many new features in the theme are only for this composer, not WPBakery.
If you use such an old theme version, there will probably be issues using the theme with latest WordPress as well. It is recommenced and good practice to keep WordPress, the theme and plugins up to date if possible
In the changelog you can see the many new additions, fixes and other changes made in the theme. This is an update guide if you decide to update
– https://forum.tagdiv.com/how-to-update-the-theme-2/
– https://forum.tagdiv.com/how-to-update-visual-composer-plugin/
After you update the tagDiv composer plugin will be activated automatically. As a note, if you update and you used WPBakery on posts, there could be problems with the post layout. Also there could be problems with page elements specific to WPBakery.
If any of these problems are present, it would be best for the moment to deactivate the tagDiv composer plugin.
Thanks
Hi,
It will work, legally a theme can be installed and activated on a single end product (website) according to the Envato license terms
– https://themeforest.net/licenses/standard
So if in the end you will be using the theme only on your final website, there would be no problem.
Thanks
Glad you fixed it. Also thank you for mentioning it, this may be helpful for other users.
Hi,
1. Sorry for the inconvenience. Indeed that string cannot be translated in the AMP version, at the moment it could only be modified in the plugin files
– https://www.screencast.com/t/GW3rKuaU3
2. In the footer they were fixed, in the sub-footer they are not yet fixed. I believe this is fixed for the next update.
Hi,
I found some articles about that, Twitter may serve AMP pages but they mention only when using the mobile social apps
– https://searchengineland.com/twitter-ramps-amp-278300
– https://developer.twitter.com/en/docs/publisher-tools/amp/overview.html
Hi,
I see you are already using those icons you mention in the homepage
– http://prntscr.com/k9ud7k
I don’t have an actual official guide that you could follow in this matter unfortunately.
Maybe we will add the possibility to allow the usage of user icons with a theme or composer setting, in the future. I believe this is added on our request list and it will be considered.
Hi,
It would be the same style as the rest of the socials
– https://demo.tagdiv.com/newspaper/wordpress-news-magazine-charts-the-most-fashionable-new-york-couples-in-2016/
I saw this issue in previous cases, the Pin it plugin was the cause. It affects the sharing button of the theme and adds it’s own design for it. The button should look as it is supposed to if you deactivate that plugin.
Thanks
Hi,
I could take a look, please provide a link to your website so I can inspect it. The height of the header is affected by the line-height setting
– https://www.screencast.com/t/itBOTSz5B
Most header styles have a recommended size for the logo for best overall results. The exception are headers 9, 10 and 11, these have no limit for the logo image.
Hi,
@spelling A general way to disable the cropping does not exist, each module will crop the original image to create a thumbnail
– https://www.screencast.com/t/AQ1Phu9m8D
You could try to modify the crop there, or remove it, then check the results. It would be the same as before if you modified this previously. Be sure to regenerate the thumbnails after you make the modifications
– https://forum.tagdiv.com/thumbnails-fix-strange-looking-images-on-blocks/
Hi,
That module is not used in any block or grid, it can be selected in the theme panel to be used in category pages for example, tag pages etc.
Some blocks with a bigger thumbnail would be these ones
– https://demo.tagdiv.com/newspaper/block-22/
– https://demo.tagdiv.com/newspaper/block-23/
The tagDiv composer flex block would be a good recommendation, but with WPBakery it is not available unfortunately.
Hi,
I tested this again, the tagDiv composer can be activated along the WPBakery page builder. There could be problems visually or in functionality when both are active however.
WPBakery specific elements or layouts may not display properly, or if you also used the builder to create posts.
We could take a look if you cannot activate the tagDiv composer, send us an email at contact@tagdiv.com and provide admin login.
Having 2 page builders active require more resources so make sure there is enough WP memory, for most users a value of 256M would be sufficient
– https://forum.tagdiv.com/requirements-for-newspaper/
Hi,
Those pictures are thumbnails created from the featured images or videos you set for your posts
– https://forum.tagdiv.com/featured-image-or-video/
– https://forum.tagdiv.com/theme-thumbs/
The pages can be edited with the tagDiv composer, you can modify it as you want
– https://forum.tagdiv.com/tagdiv-composer-tutorial/
– https://forum.tagdiv.com/block-settings-guide/
It all depends on how you want it to look, the composer has many elements and settings. Each block and grid can be customized, you can filter and sort the content it displays.
Please let us know if you have more questions or you need help with something.
Thanks
Hi,
The WPBakery page builder’s frontend editor is disabled in our theme, this has been the case from the start I believe
– https://forum.tagdiv.com/how-to-use-visual-composer/
It could only be enabled by making a modification in the theme files if this is required. Try making the modification mentioned in this similar topic
– https://forum.tagdiv.com/topic/how-to-enable-frontend-editor-mode-in-visual-composer/
Best if you check some SEO guides and tutorials online, and decide for yourself how to create the content of the website. Some guides I found
– https://www.hobo-web.co.uk/headers/
– https://yoast.com/how-to-use-headings-on-your-site/
– https://www.link-assistant.com/blog/how-to-optimize-header-tags-of-your-website-for-good-seo/
The post title is the h1 heading, so you could follow it with the other headings to create a structure.
Hi,
I have tested the Revolution slider plugin provided with the theme (version 5.4.8) also latest theme version. The slider appears, there is no such error for me. I used default settings in the slider troubleshoot
– https://www.screencast.com/t/TG1mlkOb
Maybe try and deactivate all your other plugins, keep only theme plugins and slider. That should solve the problem and also help identify which plugin could be causing the issue.
Thanks
Then there is a problem, this is a related topic with suggestions you could try
– https://forum.tagdiv.com/topic/strange-chinese-symbols-replaced-icons-and-arrows/
Hi,
The sorting will only work by publish date, so modifying the post in any way will not affect the sorting.
So in blocks using the latest sorting, the posts will be ordered by the date of publishing, not modified.