Stephen Cronin

Hi Lee,

Hmm, good question. I have no idea why I left that out now. I can look at adding it in a future version – I think it really needs to be added! Thanks for pointing this out.

Cheers,
Stephen

Hi Pjrfigueiredo,

Thanks!

Sorry about not selling the Redirect extension to EU Residents. As of 1 January this year, I’d have to start collecting EU VAT (for the country you are in) and then submit it to the EU. At the moment, because it’s a fairly niche plugin (ie not a huge amount of sales), it’s not worth dealing with the tax overhead. ??

It is on my list to work out a solution for this (maybe through Taxamo). But I need to investigate further so can’t promise a timeframe.

In the short term, the easiest thing to do was to simply prevent anyone with an IP address in the EU from buying it.

I know that sucks! I’m really sorry.

Cheers,
Stephen

Hi Rob,

Sorry for the delay. That’s really strange! Did you remove the following line from getexchangerate.php:

require_once(ABSPATH . 'wp-settings.php');

If that’s been removed then that would confirm that the error isn’t coming from there. Although the error message itself says it’s coming from wp-config’s require_once, not from LocalCurrency’s require_once, so that probably doesn’t matter.

Where does the error message actually show up? If it’s coming from LocalCurrency, then it should only appear in getexchangerate.php (that’s the only time it requires wp-config or wp-settings). But getexchangerate.php doesn’t output anything to the page itself, it only returns some values to an Ajax call, so you wouldn’t see that error on the actual page load. You’d see it in the returned HTTP request for the Ajax call, which would only show up in something like HTTPFox or Chrome Web Developer tools (or maybe the error_log).

Or does it appear when you load getexchangerate.php directly in the browser?

If the error appears in once of those places, then we’ll keep digging. If it appears somewhere else, then it may not be coming from LocalCurrency at all (in which case, please deactivate LocalCurrency and see whether the problem still occurs).

I’ll wait to hear back where it shows up! Thanks.

Cheers,
Stephen

Hi Rob,

How embarrassing! I need to update the plugin so that it doesn’t do Ajax calls to the server that way. There are now more robust ways to handle this, that probably wouldn’t have given you any problem, but I wrote the plugin before they existed. I have plans to do a major update to address this and other things, but probably not until the end of the year now.

Anyway, let’s try to get you going with the current version. The wp-settings.php file is in the root folder, as you point out. Of course, getexchangerate.php has the following line:

require_once(ABSPATH . 'wp-settings.php');

However, this is redundant in most cases because the same line is now normally included in wp-config.php as well. The wp-config line will fire first and it is using require_once (so it will only load that file once, the first time it is called). That means the line in getexchangerate.php will not actually do anything.

To clear up things while we are troubleshooting, please remove that line from getexchangerate.php. I expect you will get the same error message. If you do, then we know this is coming from wp-config.php. I’m pretty confident this is the case as the error message actually tells us this – it is saying the error happens “in /var/www/booqs.net/wp-config.php on line 84”.

So please go to line 84 in wp-config and see what it says. It will probably be the same as the line I asked you to remove. It looks like it is calling wp-settings.php in the booqs.net folder (ie the level above root). So perhaps you just need to tweak the path it is using. However, it’s probably using the ABSPATH constant.

If you look higher up in wp-config, you’ll probably see something like this:

if ( !defined('ABSPATH') )
	define('ABSPATH', dirname(__FILE__) . '/');

This is where ABSPATH is defined and it is basically saying “if it’s not already defined, then use the current directory”. The error message fits ABSPATH being set to the current directory, ie the directory that wp-config is in, which is of course wrong! So you probably need to replace

dirname(__FILE__) . '/'

with the actual path.

If I’m right, that will fix the problem! All the signs point to this being the cause, except….

If ABSPATH is set to the wrong directory, then things will be breaking all over the place, not just in LocalCurrency. This is used by many plugins and themes and most importantly, by WordPress itself.

Anyway, please have a look at wp-config and see what’s on line 84. Thanks!

Cheers,
Stephen

Hi RickySEO,

Sorry, there was an 11 hour period where there was a problem with the download. It was fixed not long after you reported this. I discussed it in this thread, but didn’t leave an update here (sorry!).

Cheers,
Stephen

Hi Kimzaidem,

I’ll mark this as resolved this seeing you haven’t come back on this. If you do come back, I’ll ‘re-open’ it. Thanks.

Cheers,
Stephen

Hi Kimzaidem,

Sorry I missed this post. I can’t seem to make this happen. The ‘delete’ buttons for each item disappear until you hover over the row. You can see that in this very short video: https://cloudup.com/ctOK1qZmv_Q

You can click Keep: Oldest or Newest and then click Apply.

Or are you talking about something else? If so, please give me some more information about just where the problem is. Thanks!

Cheers,
Stephen

Hi Kelicia,

Sorry, I’m really busy at the moment, but I’ll try to look at this over the next week or so. Hopefully I can compe up with something, but I’ll let you know.

Chers,
Stephen

Hi Kelicia,

Sorry for the delay in responding. At the moment it will only work with exact match title (ie it won’t take the variations into account).

If you can give me a couple of example titles you want to match, I can look into how much work it would be to add that as a parameter.

I think it would be a great feature for the plugin. If it’s relatively quick to add, I can do it in the next week or two. If it turns out to be a bigger job, I’ll have to schedule it and it could be a while before it’s done.

Cheers,
Stephen

Hi to anyone who had this problem (Fix Duplicates has disappeared and you can’t reinstall it as described above).

The safest way to fix this is to manually FTP into your server and delete the fix-duplicates folder and then re-install the plugin.

If you are not comfortable with doing this, I have another option for you. However, it requires editing functions.php and if you make a mistake you may break your site, so please be very careful. In fact, I recommend doing a site backup before trying this.

To use this work around, please got to Appearance > Editor and locate Theme Functions (functions.php) in the long list of files on the right. Click that and that file will open.

Double check that it says Theme Functions (functions.php) above the code editor area. If so, click in the code editor and scroll right to the very bottom (you probably won’t be able to see it at first until you scroll all the way down).

Open this file in a different window and copy the code. Return to the code editor and paste the code, checking that it is exactly the same.

Then click Update Plugin. The page will refresh and a list will appear at the top of the page with 3 steps for you to follow:

1. Click the link in the first point to force the plugin to update itself to the latest version.
2. That will take you to a new page. Once the plugin has finished updating, you will be give a link to Activate Plugin. Click it.
3. That will take you back to the plugin screen. Click the link in the third point, which will take you back to editing functions.php and remove the code we added above.

If all has gone well, you should fixed the plugin, activated it and removed the temporay list of steps.

Cheers,
Stephen

Hi Yoramzara,

Unfortunately the plugin file was bad for about 11 hours after the new version (1.0.2) was released.

If the plugin does not show up on the Plugins screen (ie the screen that lists all the plugins on your site), then it is likely that the bad file has updated over the top of the previous version and now WordPress does not see it as a plugin anymore. However, the folder is still there, so it won’t let you reinstall the plugin by uploading the zip file. ??

To fix this, you need to FTP into your server and delete the fix-duplicates folder and then you can install it again. Sorry for the inconvenience.

I’ll look into whether there is an easier way to fix this..

Cheers,
Stephen

Hi All,

This is now fixed. Apologies to all for the confusion and delay.

For those interested in the technical explanation:

I tracked the problem down to something weird in the SVN repository. Somehow the 1.0.2 tag included the entire repo! I am not sure how I managed to do that – I guess I tagged it at the wrong level.

After committing, I doubled checked that trunk had the correct files, but didn’t double check the tag. Lesson learned for next time! I’m far more familiar with Git than SVN these days…

Anyway, apologies again. And thanks for letting me know.

Cheers,
Stephen

Hi All,

Investigating this ASAP. The plugin files appear to be on www.ads-software.com’s servers:

https://plugins.trac.www.ads-software.com/browser/fix-duplicates/trunk?order=name

But the zip file seems to include the entire SVN directory rather then the plugin files themselves.

At this point it looks like www.ads-software.com is messing up and serving the wrong thing. I’ll see what I can do.

Cheers,
Stephen

Hi Matt,

Sorry, took longer than anticipated to get to it, but 1.0.2 been released now using delete_pages, so that should work for you. Let me know if there are any further problems.

Thanks!

Cheers,
Stephen

Hi Matt,

I’ve been considering this further as it has some flow on effects for the premium Redirection extension. I have decided that just managing duplicates (free plugin) should require delete_pages, while settings and redirects (extension) should require something higher (I’ll go with manage_options instead of update_plugins now I know that’s a problem for some users!).

It’s a trivial change to make, but it’s the weekend here, so I may not get it out until Monday. Anyway, I’ll update here when it’s done.

Cheers,
Stephen