WolfieZero

So to give an overview of what I’ve been doing and why it’s taking it’s time.

I use a script to pull in the WordPress functions and settings so that external files can use them. The script is

$wpRoot = $_SERVER['DOCUMENT_ROOT'];

	if (file_exists($wpRoot.'/wp-load.php'))
		require_once($wpRoot.'/wp-load.php');
	else
		require_once($wpRoot.'/wp-config.php');

The issue is that it doesn’t work so well when it comes to multi-site installs as it loses the settings for a particular site; so the database prefixes and folder/domain names resolve back to the main domain.

I’m wondering if anybody knows of any other way to grab the WP functions and settings for external files that will work for a multi-site setup?

Not yet, just been caught up with a few other bits. On the job at the moment though. Thanks ??

I’m back online and working on the plugin.

I noticed that I’ve not done some of the file locations correctly so I’m now working on getting all those correctly done. I’m working on a local setup that’s running a multisite with sub-folders so I should get this right but I’ll do a setup where it’s a single WP in a sub-folder; so trying to cover all angles here!

Odd, the script isn’t sending any data back from the first ajax request. I think I know what the issue is and it’s to do with the subdomain.

I’m going to be offline for the rest of the night, but I’ll setup a local environment tomorrow and get that issue replicated and thus fix it. I can let you know the fixes involved as well if you like?

You can take those console.log() functions out now. Thanks for being helpful trying to solve this issue; I will try and get the fix up tomorrow.

Hmm, to better check something I’ll need you to add a line to the code.

Go to /simply-poll/script/simplypoll.js and on line 48 can you add console.log(data); and on line 56 add console.log(html); then we can see if we are getting an AJAX response and what’s coming back.

I use Chrome, which has one built in, but Firefox you’ll need the Firebug add on to get the console.

haha goes in hand with the name.

It’s still the wrong URL according to console. You’ll eliminate a few steps in testing by keeping the console open as chances are any issues are Javascript based.

Ah, that will be it then! It’s not picking up the real full path. I have presumed the WP install is always root.

I won’t be able to do it today but I’ll try and push an update tomorrow to tackle that very issue.

Good spot! I use a mu installation as well, but my sites are setup to run via a sub-domain so I’m always working from root.

Ah, you are missing a file for some reason. The error the console is giving me is

POST https://www.shaunnelson.com/wp-content/plugins/simply-poll/page/user/poll-submit.php 404 (Not Found)

Try uninstalling and installing the plugin again. If that doesn’t work then try and download the plugin and manually upload it to your plugins folder and see if that works.

If none of that works then I might need to specifically check the plugin against the WP and PHP versions you specified.

I’ve tried to replicated the issue on my local machine but to no avail. The issues appears to be something with the Javascript (jQuery).

I think it’s hitting the $.ajax() function and failing there; I’m not sure if it’s the call back it will have an issue with or the returned results. Are you able to show the page where you have installed SP that I can have access too?

(I will put a note in to add some debugging features in a future update)

Looks like a possible issue with Windows or global constants; can I ask you to check you have the very latest version?

(Sorry for the delay in response!)

Where the content is outputted in the theme, you need to wrap the output var in do_shortcode() (see codex). For some odd reason, by default that filter is only applied to the post/page content by default.

So you need to have something like <?php echo do_shortcode($sideContent); ?> or varient of.

I’ve had a few people ask me how to fix this and I’m thinking I might widget it for the next version.

Hope that helps!

Thanks for spotting that, I’ll fix that up in the next version ??

Sorry for the delay in response, can I check that you are using the latest version, 1.3.4?

I’ll have a look at the issue in closer detail in the next few days for you.

Awesome! Thanks for testing that. I’ll still try and have a look at that compatibility issue just in case people want to use both.

Thanks again!