Replies

It is very odd for plugin not to work, because it is used on hundreds of websites. But, I guess, it is hard to account for every type of server or configuration quirk that some servers might have.

Important thing is that you can use plugin on another server.

I plan to release new update in the early may with some improvements and some new cleanup tools.

Milan

Yeah, VPS usually doesn’t limit anything. But, the lack of errors points to some limit that is not logged as error.

In any case, if you can’t make it work, please open the refund request, and I will issue the refund.

So far, the only reason for this to happen was the limitation on the hosting site that causes process to timeout. Some operations, in some cases might use more resources, so plugin attempts to increase PHP limit and timeout to make sure it works. But, some (less reputable, in my experience) hosting companies impose the hard limit to PHP memory, and if the plugin runs into that, it fails, and there is no errors logged, because, technically, it is not an error, it is hosting imposed limit. So far, I have seen such problems on some GoDaddy, HostGator and BlueHost shared hostings, and there is nothing I can do to remedy that, that is hosting imposed limit that there is no way getting around.

Error 404, means that page is not found, I don’t see any specific error. Plugin is not using exec or url_fopen functions, all cleanup is done through the WordPress database object, nothing else.

Since no one else reported this, and I am using plugin every few days on different websites, I am 100% it is all OK, whatever is wrong on your end, I can help only if you provide me with PHP error that is causing the problem (server error log).

Right now that is not supported. I plan to add support for that in the future updates.

A tag in the line (at the very end) is not closed:

[scode lang=”html”]

[/scode]

Should be:

[scode lang=”html”]

[/scode]

But, you need to put something inside the A tag, or it is useless, maybe you had some image to put there (based on DIV class).

Milan

Hi

Problem is that you have made an error in the content you have in the sidebar. One of the A tags inside

DIV is not closed, so everything that comes after that behaves as part of the link. Fix the HTML in the content, and it will be fine.

Milan

Hi,

I responded on CodeCanyon also, I don’t understand this question, can you post example image or explain better?

Milan

Hi,

I am using Chrome daily, and test everything in it, and I can’t see such problem. I contacted a friend with Mac and Safari, and he also can’t see any issues (tested on my websites with the shortcode in use). It is possible that you have something else on your page causing issues (conflicting jQuery plugin maybe or some extensions).

Milan

Hi,

This is currently not a feature of the plugin. But, I have added it to the list for the next plugins version.

Regards,
Milan

Just upload new files and rewrite the old plugin, no settings will be lost.

Version 2.7 is ready with the fixed issue. It should be available later today when the update gets approved on CodeCanyon.

That might be the problem. I will investigate this, and issue the fix in the next day or two.

It is very likely that plugin can’t detect your front page as front page. How is the front page set up in WordPress Settings -> Reading: as a blog or static page?

I have answered this here: http://forum.smartplugins.info/forums/topic/using-jquery-for-page-specific-action/#post-3250