Forum Replies Created

Viewing 15 replies - 106 through 120 (of 138 total)
  • Thread Starter pickme

    (@pickme)

    @vmarko,

    Thank you very much.

    I will give an update on the next uploaded image on instagram.

    Thread Starter pickme

    (@pickme)

    @vmarko hello!

    I have chosen to setup Cache Preload.

    The XML sitemap of the website has 22 pages.

    With an
    Update Interval = 900 seconds (15 minutes)
    and
    Page per interval = 22
    means every 15 minutes the cache of the entire website (all 22 pages) will be purged (22 pages per 900 sec = 15 minutes).

    With an
    Update Interval = 900 seconds (15 minutes)
    and
    Page per interval = 1
    means in 5 hours and 30 minutes (900×22 = 19800sec) the cache of the entire website will be purged (1 page per 900 sec = 19800 sec when having 22 pages).

    I am thinking to set up the following:

    Update Interval = 86400 seconds (24 hours)
    Page per interval = 22

    Will that work? > All 22 pages will have their cache purged every 24 hours.

    I don’t really understand the difference between terms: Cache Preload / Prime Cache / Purge Cache.

    What does ‘prime the page cache’ mean?

    Thanks!

    • This reply was modified 6 years, 2 months ago by pickme.
    • This reply was modified 6 years, 2 months ago by pickme.
    • This reply was modified 6 years, 2 months ago by pickme.
    • This reply was modified 6 years, 2 months ago by pickme.
    • This reply was modified 6 years, 2 months ago by pickme.
    • This reply was modified 6 years, 2 months ago by pickme.
    Thread Starter pickme

    (@pickme)

    @vmarko hello!

    A new photo has been uploaded on Instagram 14 hours ago and has not been displayed on the feed.

    On browser cache:

    For CSS&JS I have checked:

    Set expires header
    Expires header lifetime: 5184000
    Set entity tag (ETag)
    Enable HTTP (gzip) compression
    Remove query strings from static resources
    Disable cookies for static files

    For HTML&XML I have checked:

    Set expires header
    Expires header lifetime: 3600
    Set entity tag (ETag)
    Enable HTTP (gzip) compression

    For Media & Other Files I have checked:

    Set expires header
    Expires header lifetime: 31536000
    Set entity tag (ETag)
    Enable HTTP (gzip) compression
    Remove query strings from static resources
    Disable cookies for static files

    • This reply was modified 6 years, 2 months ago by pickme.
    Thread Starter pickme

    (@pickme)

    All set.

    I will give an update.

    Thank you for you help @vmarko !

    • This reply was modified 6 years, 2 months ago by pickme.
    Thread Starter pickme

    (@pickme)

    Checked > Compatibility mode = I have checked this because of the comment: Decreases performance by ~20% at scale in exchange for increasing interoperability with more hosting environments and WordPress idiosyncrasies. This option should be enabled for most sites. < I unchecked it!

    Browser cache > HTML & XML:

    Unchecked > Set Last-Modified header

    Unchecked > Set expires header

    Expires header lifetime > 10800 seconds

    Checked > Set cache control header

    Cache Control policy: cache with max-age (“public, max-age=EXPIRES_SECONDS”)

    Checked > Set entity tag (ETag)

    Checked > Set W3 Total Cache header

    Checked > Enable HTTP (gzip) compression

    Unchecked > Enable HTTP (brotli) compression

    Thread Starter pickme

    (@pickme)

    General:

    Checked > Cache posts page

    Don’t cache front page

    Checked > Cache feeds: site, categories, tags, comments

    Checked > Cache SSL (HTTPS) requests

    Cache URIs with query string variables

    Checked > Cache 404 (not found) pages

    Don’t cache pages for logged in users

    Checked > Don’t cache pages for following user roles

    Purge Policy: Page Cache:

    Checked > Front page

    Checked > Posts page

    Checked > Post page

    Checked > Blog feed

    Checked > rss2 (default)

    Purge limit: 10

    REST API > Don’t Cache

    Advanced:

    Checked > Compatibility mode

    Garbage collection interval: 10800

    Comment cookie lifetime: 1800

    Handle XML mime type > Checked > Handle XML mime type

    Thread Starter pickme

    (@pickme)

    Hello @vmarko

    I waited 24 hours to see if the new image uploaded on instagram will be displayed in the feed. It did not. Therefore, I then purged the cache in W3 Total Cache and new image appeared in the feed.

    Thread Starter pickme

    (@pickme)

    Thank you @deip

    Thread Starter pickme

    (@pickme)

    It is not a widget.

    The feed can be provided either with a shortcode or with a WPBakery Page Builder custom element.

    https://www.p56.gr/en/ > Please scroll down towards the bottom of page to view the instagram feed.

    Thank you

    Thread Starter pickme

    (@pickme)

    Their follow up reply:

    ‘The instagram cache and W3 Total Cache are 2 different things.

    Once you post on instagram, your feed should be updated automatically and the cache flushed after about an hour, so you shouldn’t have to worry about it except if you want to force to update the images.

    For W3 Total Cache I suggest setting it to flush the cache in regular interval like one or twice a day.’

    According to their reply, which setting in W3 Total Cache should purge the cache in regular intervals?

    Thank you!

    • This reply was modified 6 years, 2 months ago by pickme.
    Thread Starter pickme

    (@pickme)

    Hi!

    Their reply is this:

    ‘Instagram requires to implement a cache in every app. But if you go in the instagram settings panel and hit the save button, it should flush the cache.’

    I am using Wolf Gram. It’s a plugin developed by the theme developer.

    I will keep you updated. I’ve asked them for clarifications as to if I need to hit save every time there is a new uplodaed photo or the process will be fixed.

    • This reply was modified 6 years, 2 months ago by pickme.
    • This reply was modified 6 years, 2 months ago by pickme.
    • This reply was modified 6 years, 2 months ago by pickme.
    • This reply was modified 6 years, 2 months ago by pickme.
    • This reply was modified 6 years, 2 months ago by pickme.
    • This reply was modified 6 years, 2 months ago by pickme.
    Thread Starter pickme

    (@pickme)

    Hello,

    I have contacted the plugin’s support because there is no such setting for this plugin. I will provide an update for the topic.

    Thank you for your answer. Please don’t close the topic yet.

    Regards

    • This reply was modified 6 years, 2 months ago by pickme.
    Thread Starter pickme

    (@pickme)

    It appears, that if I add a language with loco translate plugin and choose location ‘System’ and not ‘Custom’, translations do work.

    Please elaborate on the issue why 100% translations for the Italian language do not appear.

    • This reply was modified 6 years, 2 months ago by pickme.
    Thread Starter pickme

    (@pickme)

    Hi,

    The plugin has folder name wpcf7-recaptcha and not ReCaptcha v2 for Contact Form 7 within wp-content/plugins.

    Within wpcf7-recaptcha folder there is no wpcf7-recaptcha.pot template file. I had to create it with Loco.

    From within Loco Translate I have no author languages and therefore no translations. Where is the Italian translated 100% from the author?

    I have completed all the steps you mentioned, of course on custom languages I had to add because there are no author languages in loco.

    There are 41 strings for the Italian which none are translated, even after I click Sync in Loco for that language.

    • This reply was modified 6 years, 2 months ago by pickme.
    • This reply was modified 6 years, 2 months ago by pickme.
    Thread Starter pickme

    (@pickme)

    On another topic I found this filter:

    /**
     * Modify the WPCF7 ReCaptcha translations
     * 
     * @param String $translation		- What the text should be translated to
     * @param String $text				- Original text to be translated
     * @param String $domain			- Translation text domain of the plugin
     * 
     * @return String $translation
     */
    function prefix_gettext_modifications( $translation, $text, $domain ) {
    	
    	if( 'wpcf7-recaptcha' === $domain && false !== strpos( $text, 'you are not a robot' ) ) {
    		$translation = 'Translation Here';
    	}
    	
    	return $translation;
    	
    }
    add_filter( 'gettext', 'prefix_gettext_modifications', 10, 3 );

    That filter displays the translated text both on default Italian page and secondary English page, whereas the translated text should be displayed only on the Italian page.

    • This reply was modified 6 years, 2 months ago by pickme.
    • This reply was modified 6 years, 2 months ago by pickme.
    • This reply was modified 6 years, 2 months ago by pickme.
Viewing 15 replies - 106 through 120 (of 138 total)