Forum Replies Created
-
Posts
-
OK; before we do anything else can you try deactivating W3 Total Cache and also remove (or comment out) any extra lines of code that W3TC may have inserted into your .htaccess file, which is normally found in the root of your WordPress installation (make a backup of this file first of all to be safe).
After that, test again and please also take the time to flush your browser cache also.
The /%postname%/ format is probably the safest bet. Existing links should continue to work and/or will be updated automatically, depending on the context.
… Just to confirm – is it possible the URL you posted was truncated by our forum software? We do often experience that sort of problem when people post code, etc.
OK, I’d certainly expect a longer access token, something like this would be more typical:
https://graph.facebook.com/456712346789234?access_token=123456789012345|a1b2c3d4e5f6g7h8i9j10k11l12m
What I’m going to do if possible is refer this to one of the developers who worked on the plugin as they can probably track this down more quickly than I can.
I would ask for your patience however as response times may be slower than usual at this time of year.
OK, I appreciate that this is a live site and you probably don’t want to cause further disruption there, but do you have a testing/staging environment where you have been able to replicate this problem that we might play with?
Yes, if you send an email to [email protected] (and if you could please mark it for my attention and include a link to this thread, that would be greatly appreciated).
You might need to look at your taxonomy queries, they should be in the form of an array of arrays.
Right; I mean it could be that Google is figuring out that the URLs map to dates and is intelligently trying to determine the date range since presumably nothing is linking to those URLs.
I can’t imagine it is indexing non-existent content, though, so is there a real problem here?
James: do you mean that this problem is occurring in the Appearance > Widgets admin screen, or on the front end (or both)?
Actually, I didn’t look far enough. You could do this by working with the tribe_settings_after_content_tab_additional-fields hook and making some changes so that your own code replaces Tribe’s.
You would however need to find your own way in terms of building your customization.
I see: sorry for the misunderstanding. Unfortunately I can’t help there, the field types are hard-coded in place and unless I’m mistaken there is no straightforward way to change that by normal means such as filtering or overriding.
That leaves an alternative of modifying core plugin code – however you’d really need to steam ahead and make that sort of change on your own, it’s not an approach we generally recommend or endorse.
I’m afraid there’s not a lot else I can offer up at this point.
