Search Results for 'cache'

Results from the Forum
llaporte
tagDiv Member

For your information, I activated the basic preset of the litespeed cache plugin, while we found the solution. With this preset the social sharing module works but at the expense of speed and other optimization functions.

llaporte
Participant
#0

Hello, I recently had a problem with social sharing and Litespeed Cache. I think I need to exclude the CSS and JS modules from the social sharing module but I don’t know which JS and CSS I need to identify and exclude them from the cache system.

I tried to exclude the JS by entering /wp-content/plugins/td-composer/legacy/Newspaper/js/tdSocialSharing.js in the exclusion field but that has no effect.

This is the only theme module that stops working when I activate the Advanced preset. The social sharing icons and function no longer display at all.

Could you help me.

Thanks in advance

Luc Laporte

Bettina
tagDiv Staff

Hello!

Check the color of the separator, save, clear the cache and see the results.
Make a test and deactivate all plugins except tagDiv ones. Also, if you are using a cache plugin, deactivate it, clear all cache, and try again.

Let me know the results!

Thank you!

Anamaria
tagDiv Staff

Hello,

Please let me know what issue you have using the Lite speed cache plugin. We don’t have a guide using this plugin.

Thank you!

Bettina
tagDiv Staff

Hello @Wriper!

Do you use an extra plugin for ads? Try to deactivate it, clear the cache and check if the ad is still there or not.
For the mobile theme plugin, we have only those options that could be found here: Newspaper -> Theme panel -> Mobile theme -> Mobile ads.

Thank you!

Anamaria
tagDiv Staff

Hello,

There is an option from your LiteSpeed cache https://wordpress.org/support/topic/images-do-not-load-when-cache-is-enabled/

Thank you!

Bettina
tagDiv Staff

Hello @Audrey!

Make a test and deactivate all plugins except tagDiv ones. Also, if you are using a cache plugin, deactivate it, clear all cache, and try again.
If the problem is still there, then please contact us via email at contact@tagdiv.com and provide the following:
– admin url and credentials
– please provide a video or more information about the issue
– a link to this topic in order to identify you

Thank you!

Bettina
tagDiv Staff

Hello Yaron!

Make a test and deactivate all plugins except tagDiv ones. Also, if you are using a cache plugin, deactivate it, clear all cache, and try again.
If the problem is still there, then please contact us via email at contact@tagdiv.com and provide the following:
– admin url and credentials
– a link to this topic in order to identify you

Thank you!

Anamaria
tagDiv Staff

Hello,

Please activate the tagdiv Standard pack plugin and clear the cache.

Thank you!

Anamaria
tagDiv Staff

Hello,

Please activate the tagdiv Standard pack plugin and clear the cache.

Thank you!

simchris
tagDiv Member

If you updated to latest WordPress 6.5; try going to admin and F5 in Chrome or whatever browser to clear jquery cache. We were unable to set schedule for next day posts; clearing the cache of admin code, was only way page would work properly after 6.5 update. Might not be your issue, but try it 🙂
( I don’t work here.)

News Moto
tagDiv Member

Hello Anamaria,

Kindly send litespeed cache settings for newspaper

  • This reply was modified 2 years by News Moto.
Assadujaman
tagDiv Member

Can you send me lite speed cache plugin settings for Newspaper Themes.

simchris
tagDiv Member

Sorry, forgot to mention, Google has made it harder to do the ‘clear amp cache’ thing. SHould have been a button in the official wordpress for amp plugin, but nooooooo.
If you serve 404s for the AMP endpoints, or do optional 301 redirects, that should suffice. There are no penalties or anything with removing AMP forever. Do it! 🙂
(I don’t work here, just loooooong time user.)
__ Chris S.

simchris
tagDiv Member

My pleasure. Also, note that Google has actually made it harder to clear the amp cache. So, really, no need to bother with that as either the 404 amp endpoints, optional 301 redirects, and removing the rel= links in the post meta data will solve that. At some point they will just switch AMP off entirely as they really don’t care.

Anamaria
tagDiv Staff

Hi,

There are a lot of factors which can make your site slow. Make sure you use only some templates and fewer functionalities and options.
Some factors which you need to take into account are:
External factors: server speed, if you are using CDN or not, the external resources loaded by your website like ads, fonts, tracking scripts like Facebook Pixel, Google Analytics, Twitter analytics, Hotjar and so on.
Internal factors: the number of elements on the page, image size, image formats, if you are using mobile optimized layouts, console errors, if you are using the Standard Pack plugin or not, if you are using the PRO demo or a standard one.

Also, installing a demo doesn’t guarantee that you’ll achieve the same page speed as tested on our demos. You’ll need to perform optimizations. You can use caching plugins like Super Cache or the premium WP Rocket.

There are many optimization guides provided by our users here in the forum, some made by us; you could check some of them

https://forum.tagdiv.com/cache-plugin-install-and-configure/
https://forum.tagdiv.com/how-to-make-the-site-faster/
https://forum.tagdiv.com/topic/high-number-of-ajax-request/
https://www.infophilic.com/get-almost-100-pagespeed-newspaper-theme/
https://forum.tagdiv.com/topic/score-100100-pagespeed-with-newspaper-wordpress-theme/
https://www.andraware.com/wp-rocket-for-newspaper-theme/
https://spraythemes.com/newspaper-theme/how-to-speed-up-the-newspaper-wordpress-theme-using-wp-rocket/
https://forum.tagdiv.com/topic/page-speed-guide-for-2023-beginners-and-advanced/
https://forum.tagdiv.com/topic/newspaper-theme-speedify-your-website/
https://forum.tagdiv.com/topic/tutorial-chriss-custom-optimizations-for-functions-php-etc/
https://forum.tagdiv.com/cloudflare-cdn/
https://forum.tagdiv.com/topic/theme-causing-high-cpu-usage-2/
https://forum.tagdiv.com/topic/sql-querys-high-cpu/
https://forum.tagdiv.com/topic/newspaper-theme-slow-to-respond/
https://premium.wpmudev.org/blog/optimizing-your-wordpress-database-a-complete-guide/
https://underconstructionpage.com/optimize-wordpress-database/
https://crunchify.com/better-optimize-wordpress-database-all-in-one-guide/
Also, pagespeed is not covered by support -> https://forum.tagdiv.com/newspaper-theme-support/

Thank you!

Anamaria
tagDiv Staff

Hi,

I checked, and now it seems to work well. Please try to set the mobile cache -> https://developers.cloudflare.com/automatic-platform-optimization/reference/cache-device-type/

Thank you!

Bettina
tagDiv Staff

Hello Alex!

The toolbar should be there. It is possible to have a plugin that overwrites it: https://app.screencast.com/B8eOadSmR0WvQ
Make a test and deactivate all plugins except tagDiv ones. Also, if you are using a cache plugin, deactivate it, clear all cache, and try again.

Let me know if you mean anything else!

Thank you!

Anamaria
tagDiv Staff

Hello,

I think that the plugin has an object cache option, which is why it works when you are logged in.
Please check if you have an object cache file in wp-content, please delete it and try again to activate the license -> https://forum.tagdiv.com/general-options-may-interfere-newspaper-theme/

Thank you!

simchris
Participant
#0

Reminder to folks it’s time to fully retire use of AMP as another failed abandoned Google attempt to take over the web when it was pointless and stupid for many sites where a print ready page would have worked just as well for mobile. It was a money grab to track folks usage by loading your content on their server. Ugh.

At this point, more than a year after AMP was retired as “end of life,” it’s time to move on.

Requires three things
a) setup proper 301 redirects to keep links if you had lots of inbound traffic, but frankly Google recommends simple 404 so they stop caching the /amp or ?amp URL — keep in mind normal htaccess redirect of /amp –> not /amp is tricky in case you have a post url slug of mycontent/amplify-your-cake — would kill that URL.

You need to try something like this in your root htaccess file, then *test* a amp url to make sure it redirects

e.g.,
RewriteEngine On

# Removes "amp" (or "amp/") from the end of the URL-path
RewriteRule (.*)amp/?$ /$1 [R=301,L]

this code also shared quite a bit online
RewriteCond %{REQUEST_URI} (.+)/amp(.*)$
RewriteRule ^ %1/ [R=301,L]

2) deactivate any ‘AMP’ plugins in WordPress – which will remove the rel= link in your post headers; to remove a loop

3) clear AMP cache with Google: https://developers.google.com/amp/cache/update-cache

// I don’t work here, just started to do this last year, and catching up on final nail in the AMP coffin for our other sites this month //

*also posted in Newspaper forum; but copied here for all the rest of us //

simchris
Participant
#0

Reminder to folks it’s time to fully retire use of AMP as another failed abandoned Google attempt to take over the web when it was pointless and stupid for many sites where a print ready page would have worked just as well for mobile. It was a money grab to track folks usage by loading your content on their server. Ugh.

At this point, more than a year after AMP was retired as “end of life,” it’s time to move on.

Requires three things
a) setup proper 301 redirects to keep links if you had lots of inbound traffic, but frankly Google recommends simple 404 so they stop caching the /amp or ?amp URL — keep in mind normal htaccess redirect of /amp –> not /amp is tricky in case you have a post url slug of mycontent/amplify-your-cake — would kill that URL.

You need to try something like this in your root htaccess file, then *test* a amp url to make sure it redirects

e.g.,
RewriteEngine On

# Removes "amp" (or "amp/") from the end of the URL-path
RewriteRule (.*)amp/?$ /$1 [R=301,L]

this code also shared quite a bit online
RewriteCond %{REQUEST_URI} (.+)/amp(.*)$
RewriteRule ^ %1/ [R=301,L]

2) deactivate any ‘AMP’ plugins in WordPress – which will remove the rel= link in your post headers; to remove a loop

3) clear AMP cache with Google: https://developers.google.com/amp/cache/update-cache

// I don’t work here, just started to do this last year, and catching up on final nail in the AMP coffin for our other sites this month //

CarlG
tagDiv Member

Wp Super Cache, I followed the tutorial in the support section of this site. Yes, I added that file to be excluded. cleared everything. I turned JS optimization completely off, and cleared everything. reloaded. no fix.

Anamaria
tagDiv Staff

Hello,

We no longer recommend using AMP because it is deprecated https://developer.bigcommerce.com/docs/storefront/wordpress/platform-integration/enabling-amp
For mobile theme + Amp the content need to be added in Mobile Editor -> https://www.screencast.com/t/xbgZG8kH
Please check this topic where I explained each mobile version -> https://forum.tagdiv.com/topic/mobile-version-not-working-properly-2/ -> https://forum.tagdiv.com/topic/amp-pages-not-working-well-with-this-theme/ and choose what mobile version you want.
Also, please let me know what plugin for the cache you use now.

Thank you!

Anamaria
tagDiv Staff

Hi,

What plugin for cache do you use? Did you try to exclude the file from your plugin not to optimize the js?

Thank you!

CarlG
tagDiv Member

I just started using Autoptimize, the problem existed before I started using it. I still tried what you suggested. then clear all caches. The issue is still there. I have run out of places to look for the issue.

Viewing 25 results - 1,876 through 1,900 (of 29,810 total)