Raam Dev
Forum Replies Created
-
Forum: Plugins
In reply to: [Comet Cache] Comet Cache has disappeared from menu@beniellis Ah, I see. Yeah, the latest version of Comet Cache requires PHP 5.4+. We did have a bug in the part of the code that checks if you’re running the right version of PHP (that bug will be fixed in the next release). It could be that you were affected by that bug when Comet Cache failed to properly detect that your PHP version did not meet the minimum requirements.
Forum: Plugins
In reply to: [Comet Cache] Comet Cache has disappeared from menu@beniellis If reinstalling Comet Cache doesn’t get the plugin to show up in the WordPress Dashboard, I suggest contacting your web hosting company and asking them about that. It could be the hosting company did something that is preventing Comet Cache from loading properly (although I have no idea what that might be).
If it’s possible to set up a second WordPress installation on the same server, you might try doing that to see if it’s something specific to your site, or if it’s happening on any site on that server.
Forum: Plugins
In reply to: [Comet Cache] Popular posts widget problem1) So how can I get that kind of widgets work and update itself without caching? I can’t get them over ajax, as it would break my SEO process etc..
@127001-1 Unfortunately, you cannot. The only option would be to use a caching plugin that supports dynamic fragmentation, where specific portions of page are allowed to remain dynamic while the rest of the page is cached.
There are all sorts of security implications with such a feature (I believe W3TC and/or WP Super Cache were affected by such issues and, if I’m not mistaken, disabled by default or removed that functionality at some point in the past).
We have a Comet Cache feature request open for dynamic fragmentation that explains more of the technical details about why such a feature is difficult to implement properly. It’s still a feature we want to explore, but it’s not currently a high priority. I encourage you to leave a vote and/or comments on the feature request if you’re interested in seeing this in a future version of Comet Cache.
2) I use ‘… ago’ type of datetime representation for the post’s publish time. In other words, when I publish a post and view it, I see ‘published 4 minutes ago’ word. So the page is cached with that and even you visit the post 5 days ago, you still see ‘4 minutes ago’ thing. I don’t know how can I fix these kind of issues
This would also require dynamic fragmentation, as explained above. Another option in this case would be to set your cache expiration time to something lower, like 12 hours. Then at least the “XX time ago…” dates won’t be more than 12 hours off.
Forum: Plugins
In reply to: [Comet Cache] Comet Cache has disappeared from menu@beniellis Hmm, that sounds like a larger issue with your WordPress installation. Have you tried deactivating all other plugins and enabling a default theme (e.g., Twenty Sixteen)?
Forum: Plugins
In reply to: [Comment Mail] Fatal error@gretchenlouise Please open a ticket using this (expires in 48 hours) link and include the URL to this support thread in the message. 🙂
Forum: Plugins
In reply to: [Comet Cache] Warning message when loading front page@emellina We have a patch coming in the next release that should resolve this (see this GitHub issue). However, if that’s your production website I recommend logging PHP errors to a log file instead of displaying them on the front-end of the website (you can check with your web hosting company for instructions on changing that).
Forum: Reviews
In reply to: [Comet Cache] It. Just. Works.@kaplunkiigirl Thanks so much for the awesome 5-star review! And thanks for sticking around since the Quick Cache days. 🙂 We work really hard to make Comet Cache play as nicely as possible with the rest of the WordPress ecosystem, so I’m really happy to hear that has been your experience.
My only request? An easy and intuitive way to clear a specific page, post or URL from the cache via the admin console, without having to either update my post or clear the entire cache.
We actually have that feature in the Pro version. In the Pro version, there’s a button with a menu added to the Admin Toolbar that lets you clear a specific URL, clear the cache for the current page, etc. Here’s a screenshot: https://cloudup.com/cZtvc1NMRZP
Forum: Plugins
In reply to: [Comment Mail] Error message received when replying to comments on blog@verushka23 Comment Mail v160824 has been released that includes a fix for the fatal error you reported. Please let me know if you run into any other issues.
https://ww.wp.xz.cn/plugins/comment-mail/changelog/
– Bug Fix: Fixed a bug that was generating a fatal error when replying to comments. This bug only affected the Lite version of Comment Mail and was introduced by the previous release (v160818) where work was done to strip out unused Pro-only code from the Lite codebase. A few references to Pro-only functions were missed and that resulted in fatal errors for the Lite version in some scenarios. See Issue #297.
Forum: Plugins
In reply to: [Comment Mail] Error Replying to Comments When Logged in to wp-admin@dcdlm As I mentioned in the other thread, Comment Mail v160824 has been released that includes a fix for the fatal error you reported. Please let me know if you run into any other issues.
https://ww.wp.xz.cn/plugins/comment-mail/changelog/
– Bug Fix: Fixed a bug that was generating a fatal error when replying to comments. This bug only affected the Lite version of Comment Mail and was introduced by the previous release (v160818) where work was done to strip out unused Pro-only code from the Lite codebase. A few references to Pro-only functions were missed and that resulted in fatal errors for the Lite version in some scenarios. See Issue #297.
Forum: Plugins
In reply to: [Comment Mail] Fatal error@gretchenlouise Comment Mail v160824 has been released that includes a fix for the fatal error you reported. Please let me know if you run into any other issues. If you see that error related to SQL again after updating to v160824, please let me know exactly how you reproduce it—I haven’t been been able to reproduce that specific error at all.
https://ww.wp.xz.cn/plugins/comment-mail/changelog/
– Bug Fix: Fixed a bug that was generating a fatal error when replying to comments. This bug only affected the Lite version of Comment Mail and was introduced by the previous release (v160818) where work was done to strip out unused Pro-only code from the Lite codebase. A few references to Pro-only functions were missed and that resulted in fatal errors for the Lite version in some scenarios. See Issue #297.
Forum: Reviews
In reply to: [Comet Cache] Great!@darko-a7 Thanks so much for the 5-star review and for all the feedback! 🙂
1. Mobile Phone Accessibility (android, latest chrome browser app)
Yes, we have [a GitHub issue](https://github.com/websharks/comet-cache/issues/699) open for this and it’s high on our list of priorities. 🙂
2. CLEAR CACHE – URL shortcut option?
The Pro version includes a little menu in the Admin Toolbar, accessible from anywhere on the site, that allows you to clear the entire cache, clear the cache for a Specific URL, clear the PHP OPCache, or clear Expired Transients.
3. Drop-Down Option Menus…
We’ve had a GitHub issue open for this for awhile, but we haven’t done anything with it yet mostly because we haven’t had enough complaints about the UI and have instead chosen to focus on improving the software itself. That said, we’re long overdue for a UI refresh so it’s very much still on the plate. 🙂
Forum: Plugins
In reply to: [Comet Cache] What are the so called "Custom Term Archives"?@kent-brockman Right. Those are archive views for any Custom Taxonomies that might’ve been created for use with a Custom Post Type. For example, Categories and Tags are two default Taxonomies and you can view Category and Tag archives on the front-end (e.g.,
/category/my-category/or/tag/my-tag/). That archive view will then be cached by Comet Cache (and the cache file will be deleted automatically so that it can be regenerated when necessary, e.g., when you publish or delete a post in that category or with that tag).If you have a Custom Post Type that creates a new taxonomy, for example a ‘Product’ Custom Post Type that creates a ‘Brand’ taxonomy, you might have a Brand archive view accessible at something like
/brand/apple/that lists all Products of the brand ‘Apple’. Comet Cache would cache that archive view.The “Clear Custom Term Archives Too?” option is referring to clearing those front-end-accessible archive views for custom taxonomies.
Note that not all Custom Taxonomies have front-end-accessible archive views. You probably can’t access an archive view for a ‘Shipping Address’ Custom Taxonomy, for example. An archive view is anything that lists all of something grouped by a taxonomy (all posts in Category A, all posts with Tag X, all products with Brand Y).
Does that answer your question?
@sylefel You can add the following to your Child Theme’s
functions.phpfile to tell Independent Publisher not to apply the enhancements that hide the form and show the button:function independent_publisher_enhanced_comment_form() { return; }Forum: Themes and Templates
In reply to: [Independent Publisher] Widgets on right side of website@arvind2213 This theme only supports widgets on the left side, not the right side.
Forum: Reviews
In reply to: [Comment Mail] Really a powerful plugin!@master412160 I’m afraid not, no. We do have the idea in our queue for new plugins to build though.