Raam Dev
Forum Replies Created
-
Forum: Plugins
In reply to: [Comet Cache] PHP 7 compatability@taastrategies Comet Cache is fully compatible with PHP 7 and we’re running it on many PHP 7 servers in production. The PHP 7 compatibility checker that WP Engine is using is incorrectly reporting false-positives. Please see this article draft for a technical explanation about why those issues being reported are invalid.
Forum: Plugins
In reply to: [Comet Cache] Device or resource busythey said, verbatim, the plugin seems to be configured in a peculiar way.
@googlebot Comet Cache is not configured in a peculiar way. It uses standard PHP functions for reading and writing to the file system.
Here’s a link to the line in the source code where that error is being thrown:
https://github.com/websharks/comet-cache/blob/dev/src/includes/traits/Shared/CacheDirUtils.php#L156And here’s the PHP function that Comet Cache is using:
http://php.net/manual/en/function.rename.php@redhorsemountain @googlebot I suggest contacting your hosting company with the above information. A “Device or resource busy” message indicates that the web server is lacking enough resources for your site.
Forum: Plugins
In reply to: [Comet Cache] Clearing the cache way to much…?this is absurd, that Comet Cache clears the cache even when I just visit the backend,
That doesn’t happen on the majority of all sites. It happens on your site because you have a theme or plugin installed that is incorrectly calling a WordPress Core hook or filter every time you load the Dashboard and that call is making Comet Cache think that a change occurred that requires it clear the cache.
This is a reality in WordPress: Plugins and Themes can call hooks and filters that can change the behavior of other plugins. That’s why it’s important to only run themes and plugins whose source code has been audited and reviewed by experienced WordPress developers.
If you’d like to read more about how the WordPress Plugins API (and hooks and filters work), see this article: https://codex.ww.wp.xz.cn/Plugin_API
when you are so disingenuous and unhelpful even here in these stages…?
How am I being disingenuous and unhelpful? I’m sorry that you feel that way but I’m doing whatever I can to help. What you are describing is simply not a bug in Comet Cache but a conflict with another plugin you have installed on your site. See also this article: Testing Comet Cache in a Clean WordPress Installation
Easy enough but equally absurd that I have to enter code to change that, and finally even more absurd as well as manipulative and counter to the spirit of WordPress that I have to buy a pro version even to enter the code…
The feature that I’m referring to is not designed to “fix” problems like you’re describing. It’s designed for site owners who have an advanced configuration and require more control over Comet Cache’s behavior. In your case, the issue is that you have another plugin causing this problem (or possibly your theme, however this sort of issue is usually caused by a poorly-coded plugin). The proper fix in your case is to deactivate the plugin that is causing problems.
- This reply was modified 9 years, 6 months ago by Raam Dev.
Forum: Plugins
In reply to: [Comet Cache] Unable to copy files while updating to Comet Cache 161119@adopted3
.htaccess.bakis not a file that Comet Cache creates or has as part of its plugin files, so it sounds like you either had another plugin (such as a security plugin) add/modify that file, or your web hosting company modified or added it.Forum: Themes and Templates
In reply to: [Independent Publisher] Sidebar moved to bottom of page@rjalexander When you resize the browser to less than 1200px, the layout automatically changes so that the sidebar widgets show up at the bottom. I just took a look at both of the sites you mentioned and the sidebar correctly appears on the left side when my browser is > 1200px wide.
@badjohnny You can enable that option in WordPress Dashboard → Appearance → Customize → General Options → Overlay Post Title on Post Cover.
Forum: Plugins
In reply to: [Comment Mail] Work with WP REST API?@mgozdiskowski Thank you very much for the additional details. We’ll work on getting this tested and will update the GitHub issue and we’ll post an update here too.
Forum: Plugins
In reply to: [Comet Cache] Device or resource busy@googlebot The “Device or resource busy” message is coming from the filesystem on your server and is likely the result of a server that is out of resources. I suggest contacting your web hosting with that message.
Forum: Plugins
In reply to: [Comment Mail] Work with WP REST API?@mgozdiskowski Thanks for the report. I was not aware of any issues with comments submitted via the REST API, but I’ve gone ahead and opened a bug report so that we can investigate: https://github.com/websharks/comment-mail/issues/321
Are you using another application to post comments via the REST API, or is this something custom that you’re using? (I’m asking so that we can reproduce the issue on our end; knowing what you’re using will help us with testing.)
Forum: Plugins
In reply to: [Comet Cache] PHP Fatal error: Uncaught Error@massimod It could be related, yes. I’ve added a note to the new GitHub issue. Thanks!
Forum: Plugins
In reply to: [Comet Cache] PHP Fatal error: Uncaught Error@massimod Thank you for the updates. I’ve opened a GitHub issue for this. If you have any further updates, a comment on that GitHub issue would be great. 🙂
Forum: Plugins
In reply to: [Comet Cache] PHP Fatal error: Uncaught Error@massimod Thanks for the report! At first glance, this does look like it might be a conflict with Postman, but Postman is a plugin that lets you configure an SMTP server for email, which doesn’t seem like it would be related to anything with WordPress Feeds.
Can you tell me how this error was generated? Was the error the result of some action, or did you just see it appear in your error log?
Also, this path doesn’t look complete:
#6 /home/wp-content/plugins/postman-smtp/Postman/Postman-Email-LoIs there anything that comes after
/Postman-Email-Lo?Forum: Plugins
In reply to: [Comet Cache] cloudflare include@poetaster That is a file that is only used in the Pro version (for a Cache Stats and Charts feature); it was mistakenly enqueued in the Lite version. We have an update coming in the next week that fixes this bug. See https://github.com/websharks/comet-cache/issues/830
Forum: Themes and Templates
In reply to: [Independent Publisher] Old Version of theme@scottb4744 Yes, you can find a list of all prior releases here: https://github.com/raamdev/independent-publisher/releases
Forum: Plugins
In reply to: [Comet Cache] mkdir error message from Comet Cache@nathan-adams In that case it sounds like iThemes Security might be causing this problem. Comet Cache cleans up things on its own and recreates things all the time in the cache directory, and if iThemes Security is somehow preventing the deletion of a directory that Comet Cache is trying to clean up and then recreate, you could see errors like that.
If possible, can you exclude the
wp-content/cache/directory from iThemes Security altogether?