Arunas Liuiza

Ok, on the other site WP Super Cache is the culprit. It is adding a line <!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! --> to the output of everything and that makes Gust’s json unreadable. Make that message go away (by fixing WP Super Cache or getting rid of it completely) and things should run smoothly. If you use caching, make sure Gust is not being cached (by white-listing /gust/* and /api/*)

On your personal site I see a 500 error on some API calls. Problem is, the errors are not detailed. I would need to see server log file to find actual error.

hi,
Gust is meant as en editing platform, so uneditable pieces of content are not shown by design.
I’ll have to look into possible solutions for your problem. In the meantime, you should note, that wp-admin panel is still accessible if gust is enabled, so you could still link your authors there for the help and tutorials.

Hi,

parsererror generally means there is some additional output on the API call response. could you give me a screenshot of the error?

v0.4.0 supports CPTs, so this is resolved.

Hi,

There will be an update. As it has been pointed out before, the original code is quite a mess, so I am now in the process of cleaning it up and making a better structure for later updates. I want to do that before I add any more features, as that would make for much more cleaning afterwards.

The problem with your site is that your theme loads a second copy of jQuery and related scripts in the footer, and it does not do that in proper “WordPress way” – via wp_enqueue_script.

My plugin enqueues jQuery and after that loads a jQuery extension – noUiSlider. Your theme then loads a second copy of jQuery, which overrides the first one and drops noUiSlider in the process, so in the end you have jQuery, but no slider.

Solution: Removing line
<script type="text/javascript" src="http://www.incomemesh.com/wp-content/themes/codilight/js/jquery.js?ver=1.8.3"></script>
from your themes footer.php (or wherever it is put) should solve this problem (and probably for some other plugins, if they rely on jQuery extensions), and your theme should still be working the same way, as jQuery will be present. It is a bad practice to manually include a copy of jQuery in a theme/plugin. WordPress has jQuery, jQuery UI and a lot of other JavaScript libraries built-in and You should use those whenever possible. You can find documentation of wp_enqueue_script and a list of available libraries here: http://codex.wordpress.org/Function_Reference/wp_enqueue_script

Hope this helps, if not – please let me know again.

Hi, thanks for the report.

I’ll try to replicate that and get back to you. I have a hunch it might be IIS related, as I haven’t tested on it before.