Pat K
Forum Replies Created
-
Forum: Plugins
In reply to: [NextCellent Gallery - NextGEN Legacy] thickbox conflict with wordpress 3.9Thanks ds123!!!
I AM using a custom nggallery.css file and your fix worked perfectly. Saved me a bunch of time trying to figure this out. Thanks for sharing your solution!
Cheers
Hi Joe,
Thanks for the quick response! The 2 sites are:
http://blog.reversegearinc.com/
http://mindfulnesspeterborough.ca/…I rolled both of them back to 2.3.5 so you won’t see the problem. If you need me to update one of them so you can see the problem, let me know.
Cheers
A bit more information: one of the sites that updated ok is ALSO a child theme of Twenty Ten, and both Twenty Ten child theme sites (one that updated ok and one that didn’t) are located on the same server. It’s also worth mentioning, the Twenty Ten child theme site that updated ok has been much more heavily modified. Weird.
Forum: Plugins
In reply to: [Twitget] URL's in tweet not parsingThanks for following up Boštjan!
Forum: Hacks
In reply to: Native gallery shortcode output- title attributeHi chachalady! You officially helped someone! Thanks for sharing this. Works like a charm.
🙂
Forum: Plugins
In reply to: [Twitget] URL's in tweet not parsingSome links are working some aren’t. Some links to external sites (retweets) work, but not links back to Twitter.
Any idea what the problem is Boštjan?
Forum: Plugins
In reply to: [Twitget] URL's in tweet not parsingSame problem.
WP v3.8.1
Twitget v3.3.1 using the Twiget Widget (Appearance > Widgets)
URL: http://www.feetessentials.comThe shortened URLs are visible but there is no anchor tag.
NOTE: in case this matters; I tried checking “Show full URLs” and clicked Update Options and the t.co URLs continued to be displayed (no change). I WAS able to modify the number of tweets displayed, so the Update Options function seems to be working…just not with respect to the URL setting.
Great plugin by the way – very configurable!
Forum: Plugins
In reply to: [Collapse-O-Matic] Roll-your-own and rel attributeHello! Great plugin!!! I too have been having the problem with rel attribute being stripped out by the Visual Editor when clients switch between it and Text mode. I searched for an found this:
https://snipt.net/jamesw/prevent-tinymce-from-stripping-schemaorg-attributes-in-wordpress/I’ve been testing it and it seems to be working great. Just added the snippet to my functions.php file and voila! No more stripping!
…if it breaks something horribly I’ll re-post.
Cheers,
PK @ BlackCapDesignFollow-up to this:
There was more going on here than I realized. Despite the change I made (above), I continued to get 403 Forbidden messages when following links from Google. I tried removing all instances of %27 (single quote) from the BPS root .htaccess file and the forbidden errors stopped completely.I have since determined the offending single quote was in the Site Title (Dashboard > Settings > General Settings > Site Title) …as in “Bob’s Website”. I replaced ‘ with ’ and once the change is reflected on Google, I’ll try replacing all instance of %27 in the root .htaccess file.
Any idea why a single quote in the Site Title would trigger the BPS filter? And do you think replacing ‘ with ’ will do the trick?
Thanks again for a great plugin!
Problem resolved!
The problem was NOT the BPS plugin – rather an email obfuscation plugin that works fine in HTML 4 but throws header errors in HTML 5. The combination of BPS and CSF firewall were catching this and directing traffic to the forbidden page. I THOUGHT I had disabled the obfuscation plugin during testing – but clearly I did not. If anyone’s interested, I replaced the OLD email obfuscation plugin with the Email Encoder Bundle plugin and it works great with BPS.
Thanks again for BPS; excellent plugin and stellar support.
PK
BlackCapDesignI checked the links using Firebug (in Firefox) and there are no special characters. There is a JavaScript onmousedown event:
<a href="...">…but the URL itself if clean and uses this format:
href=”http://www.sitename.com/”
href=”http://www.sitename.com/about/”I have a sneaking suspicion this is going to be something dead-simple and I will soon be smacking my forehead….
Thanks again for your suggestions!
PK
BlackCapDesignRe: Redirects; thanks – the problem was happening before I installed the Redirects plugin. I tried the Custom Code method already (I use it on other sites). The reason I’m using the Redirects plugin is because I’ve had to disable BulletProof Mode on the root directory – because of the weird broken link problem.
Makes sense, although when I was testing this yesterday, I deactivated the Redirection plugin, and it made no difference; following Google links to the Home page – the index.php file in the root directory – were resulting a “Forbidden” page – even with the Redirects plugin deactivated. Disabling BulletProof Mode in the root directory caused the links to start working again.
After I received your message(today), I reactivated BulletProof Mode and turned on Error Logging – no errors have been logged.
I do have a firewall on the server (CSF – LFD)…I’m wondering if something in BPS is triggering the Firewall to throw the forbidden error …although if that were the case it should be affecting other sites on the server too, and it’s not.
Thanks for your suggestions!
PK
BlackCapDesignThanks for the quick response! No, the directories are the equivalent of /%postname%/ (Pretty Permalinks). They all resolve to WordPress pages.
The ‘old’ site structure was similar to the current WordPress structure: http://www.site-name.com/directory-name/index.php, and in some cases the directory name of the ‘new’ site match the old site ( example: /contact/ ) but most of the directory names are different, hence the need for redirects.
Strangely, even the link to the home page http://www.site-name.com results in a “forbidden” error message when I activate BPS in the root directory. As soon as I switch to Default Mode, the Google links work fine.
Something else: if I click the Google link, it resolves to the Forbidden page, but if I place my cursor in the address bar and hit enter, the browser resolves to the correct page. So it’s something to do with the inbound link from Google….
Ideas….?
Thanks again!
PK
BlackCapDesignGreetings Frank! I too am receiving the same error upon installation:
Warning: join() [function.join]: Invalid arguments passed in /home/xxxx/xxx/wp-content/plugins/wp-maintenance-mode/inc/wp-maintenance-mode-settings.php on line 228
There is nothing in the Exclude field; it’s blank. I have uninstalled and reinstalled your plugin. I disabled a few other plugins (Bulletproof Security for one) and it didn’t make any difference. What’s odd is I have used this plugin on other sites and it has worked fine.
In the warning message (which appears directly above the Exclude field) the words “function.join” are a hyperlink to a “page not found”: http://site-address.com/wp-admin/function.join
If I check my preferences and click ‘save’, the Preview button displays the same “page not found” error. Odd. Hope you can figure this out…