Raam Dev
Forum Replies Created
-
@stacyabarnes Thanks so much for the great 5-star review! π
@angrymog From what I can tell, the Just TinyMCE Custom Styles plugin is not designed to change the front-end styles, only the styles in the editor itself. If you wanted to change the front-end styles (i.e., what you see what you hit Preview or when you Publish the post), you’d need to use something like Jetpack’s Edit CSS module or edit the theme’s
style.cssfile to add custom CSS styles that modify the theme’s default styles.Forum: Reviews
In reply to: [Comet Cache] Best Caching Plugin Period@sire64 Thanks so much for the fantastic 5-star review and for taking the time to write one for us! π I’m thrilled that you’ve found Comet Cache so useful.
Forum: Plugins
In reply to: [Comet Cache] Comet Cache related price error on WC product page@hectornado Hey Johan,
Comet Cache does include integration with WooCommerce to ensure that the cache for the Product Page gets cleared when certain events occur. It sounds to me like this issue might be related to the theme you’re using, but it also might be something that we need to improve in Comet Cache.
Comet Cache does not exclude Product Pages from the cache, but if you wanted to do that you could use the URI Exclusion Patterns (see Comet Cache β Plugin Options β URI Exclusion Patterns).
Is this problem occurring when you change the product price from the Dashboard for a product that is already live (i.e., a product that might have a Product Page that has already been cached)? Any more information you can give me would be helpful.
Forum: Themes and Templates
In reply to: [Independent Publisher] Word count for non-Roman languagesHey @agfare,
Unfortunately I’m not at all familiar with non-Roman languages so I don’t have any advice, but hopefully someone else will chime in here with some suggestions! If there’s anything I can do to improve this in the Independent Publisher theme, I’d be happy to do so.
Forum: Themes and Templates
In reply to: [Independent Publisher] Mobile images centre@anilvanderzee Independent Publisher 2 is not the same as the original Independent Publisher themeβitβs a fork of the original theme designed for WordPress.com users. The original IP theme was published here on ww.wp.xz.cn and then Automattic took the original theme and created a version for WordPress.com. Please see http://independentpublisher.me/2016/getting-support-for-independent-publisher-on-wordpress-com/
You can get support for Independent Publisher 2 here.
- This reply was modified 9 years, 1 month ago by Raam Dev. Reason: Add link to IP2 support
Forum: Plugins
In reply to: [Comet Cache] Mini Cart Getting CachedHey @andrew1977,
Comet Cache is a page caching plugin, which means that it takes the entire contents of what WordPress generates and then caches that to a static HTML file, which is then served upon future requests to save unnecessary database and PHP requests, thereby increasing the speed of serving the page and reducing the impact on server resources.
Since each page is cached in its entirety, it’s not possible to ‘exclude’ a specific portion of a page from the cache (e.g., the mini cart in your header). There is a technical way around this with what we call dynamic fragmentation, but there are lots of security issues related to such a feature, so we haven’t implemented it. There’s a feature request here that you can read more about this and leave a comment to show your vote for this feature if desired: https://github.com/websharks/comet-cache/issues/222
The best way around the issue you’re having is to have the cart feature powered by JavaScript instead of PHP, that way server-side page caching has no effect on the cart. That’s how most shopping cart features are programmed. They use Client-Side JavaScript to fetch the status of the cart, thereby ensuring that the contents of the cart stay updated even if the page itself is cached. You’ll need to consult with your site developer, or with the plugin developer for the cart/theme you’re using, to see if they can update the cart to use JavaScript, which would make it compatible with WordPress caching plugins like Comet Cache.
Forum: Themes and Templates
In reply to: [Independent Publisher] Independent Publisher 2 – Social menu?@rebecka Independent Publisher 2 is not the same as the original Independent Publisher themeβit’s a fork of the original theme designed for WordPress.com users. The original IP theme was published here on ww.wp.xz.cn and then Automattic took the original theme and created a version for WordPress.com. Please see http://independentpublisher.me/2016/getting-support-for-independent-publisher-on-wordpress-com/
You can get support for Independent Publisher 2 here.
- This reply was modified 9 years, 1 month ago by Raam Dev. Reason: Add link to IP2 support
Forum: Plugins
In reply to: [Comet Cache] ERR_EMPTY_RESPONSE on settings save@son9ne The
ERR_EMPTY_RESPONSEerror is something that the browser displays when it has unexpected trouble loading a page. Please see this Google Chrome article for a few ideas for how you might be able to solve the problem.If that doesn’t help and your web hosting service uses a server-side cache like Varnish, you might want to try purging the Varnish cache to see if that helps.
Forum: Reviews
In reply to: [Comet Cache] Awesome!@fleeky Thanks so much for the 5-star review! π β€οΈ
Forum: Plugins
In reply to: [Comet Cache] long filename issues@sjlevy Thanks for the update. I’m noting the Comet Cache GitHub issue that you opened regarding this issue so that others can follow along: https://github.com/websharks/comet-cache/issues/888
Forum: Reviews
In reply to: [Comet Cache] A fantastic and easy-to-use caching plugin@clocksaysnow Thanks so much for the awesome 5-star review! We put a lot of effort into making Comet Cache as easy-to-use as possible and as widely-compatible as possible, so I’m so happy to hear that’s how you found it. π
Forum: Plugins
In reply to: [Comet Cache] Countdown/up timer not refreshing@mikeg64 The only types of dynamically updating timers that will work with WordPress caching plugins are those that use JavaScript to update. WordPress caching plugins capture the output from WordPress and serve that cached HTML to future visitors. If the timer that you’re using relies on the output of WordPress to update, then it most likely won’t work with WordPress caching plugins, including Comet Cache.
I recommend checking with the developer of the timer plugin you’re using to see if it will work with WordPress caching plugins, or you might try another timer like what @christianboyce mentioned above.
I hope this helps! π
Forum: Plugins
In reply to: [Comet Cache] long filename issues@sjlevy writes…
the root path and the 22 char comet cache generated tmp extension will put these cache files over the limit and causes them to fail to write to disk.
The error message you included in your response doesn’t say anything about a maximum filename length, rather it just says “failed to write cache file”. How are you determining that the failure was caused by a long filename and not by something else?
I was reviewing the Wikipedia page on limits for NTFS:
The pathname can be up to 32,767 unicode characters in length, with each path component (directory or filename) up to 255 characters.
The example filename you provided above, even with the
-tmpsuffix, is only 169 characters long, well under the 255-maximum for NTFS.Forum: Plugins
In reply to: [Comet Cache] long filename issues@sjlevy A few years ago we worked in a fix for overly long filenames (see this GitHub issue):
Any
http://host/path/[component]/that is longer than200chars is converted tolpc-sha1([component]). Any overallhttp://host/[path]that is longer than2000chars, is converted tolp-sha1([path]).See this section of code where long paths and compoents are compacted.
It sounds like you might need to tweak the maximum path length and/or the maximum component length, is that correct? If you could try playing around with those and see if that solves your issue and then report back, that would be great. If that does it for you, I’ll see about getting a filter in the next release that allows you to customize that without modifying core plugin files.