migs
Forum Replies Created
-
AuthorPosts
-
Hi Stiofan
Sorry for the delay, I try not to work weekends 😉
I tried again, and it still didn’t work, so I downloaded a fresh copy of the GD package, uploaded the core language .po, edited it in poedit and uploaded the .mo to wp-content/languages/geodirectory.
That time, it worked perfectly. It seems either there was an issue with the original .po I had, or at least with the .mo that was being created from it by poedit.
Whatever it was, it’s fine now 🙂
This is one area where Joomla outshines WP. Why someone ever thought language files should be compiled is a mystery I’ll never figure out.
migs
Thanks Simone
No cache plugin, wp-config tried with define(‘WPLANG’, ‘en_GB’); both included and not, as it’s supposed to be deprecated in WP4?
Ah, I suppose the category box issue makes sense. I don’t use it in the sidebar, so it never occurred to me.
I’ll put the feature request in, thanks.
Hi Simone, yes they are named correctly.
Typo Edit: Path used was wp-content/languages/geodirectory/
Just to add to what Paolo said…
X has been WP4 compatible since v2.40 was released a few weeks ago, so that shouldn’t break either way.
Personally, I always update WP first, simply because you will know straight away if any plugins break with the update, and you can then reinstall the backup you obviously made before doing a major WP update 😉
Hey Paolo
It wasn’t the update that caused it. At the same time as I applied the update, I deleted the default place categories and created new ones. This meant, of course, that the place listings didn’t have categories assigned. As soon as I assigned them to one of the new categories, the problem went away.
As a test, I then removed all the listings from the category I’d put them in, but the problem didn’t reappear.
It looks like a listing can be removed from a category, once it has been added, but if it’s never been in one of the listed categories in the first place, then the details page breaks.
Thanks
migs
I can only assume your days are much longer than ours 😉
The only reason I ask about the changelog is that GD works perfectly well for me already. Unless there are serious security issues addressed or new features added that would be useful, I might give the update a miss this time.
Assuming I don’t update the core, how would that affect the addons with regards to updating (or not) those?
It’s great that the work continues, despite the setback.
The changelog page hasn’t been updated since v1.1.7. Is it possible to see the changelog for v1.2.0?
Thanks John
Just to confirm that adding the if statement works perfectly.
Yep, exactly
Hi John
I didn’t have the breadcrumbs issue until I updated the plugin. Adding the above line doesn’t make any difference.
Cheers
migs
Hmmm, I thought I’d tried that, but I obviously missed something, as it’s just worked 🙂
Thanks John (again)
I think there’s another issue.
The footer is definitely not right on on the GD pages. All non-GD pages are fine.
I didn’t have the footer active originally, so it’s only just come to light. Screenshots attached of both gd and non-gd pages.
migs
-
AuthorPosts