thecodezombie

Well, you could’ve just started with a free trial. You had 30 days to make sure it’s running as expected.

Wow, only 9 months to answer this…congrats, that might be a record! ??

Well, no, not really. If you re-read what I posted, my issue isn’t with adding the ShareThis buttons; I’ve done this plenty of times. My issue is that even when you implement it on posts only, it still loads all your files (1 JS, 1 CSS)…if I’m not using ShareThis on this page, I don’t want its 13kb of files and 2 HTTP requests.

And because you hard-code the <script> in your plugin – instead of using the likes of wp_enqueue_script wp_enqueue_style (like you’re meant to) – I can’t use any WordPress functions / conditional logic to stop it from firing.

I know this plug-in is meant to cater for everyone, including the novices, but the way this plug-in works as a “install-and-forget” plug-in completely kills any possibility of using it in a real project.

Anyway, nevermind because I’m now using Socialite.js

So what you’re asking is how to scrape other sites for their content? And you’re asking this in a thread related to a social networking plug-in?

The content on their site is theirs; you copy it, you break copyright. Rather than investing time trying to find ways to scrape content from other people, why don’t you just invest the time writing unique content?

You’re not bringing anything new to the web by just scraping other people’s hard work.

There’s no way to disable the plug-in on specific areas.

What you need to do is disable it everywhere using the plug-ins settings (2 drop-downs, set both to no), then place the code into your theme, on the template pages you want it to appear on (e.g blog post = single.php).

Had the exact same problem as discern, installed the HotFix plug-in and it’s all good again.

Cheers esmi,

I did realise that it could be something as easy as this, it’s just it happened in such a particular place I had convinced myself it was a conflict.

64M was fine.

Closed.

Can confirm that the update does fix this issue (with WP 3.1.1)

Note: You need to go into your TinyMCE Advanced settings and re-save the layout for it to appear.

Hi John,

Cheers for the explanation.

I ended up putting an ‘events’ prefix on the Events C.P.T re-write in order to differentiate it from the normals.

Weird thing is, I’m using a ‘No Category Base’ plug-in to strip the normal pre-fix of ‘category/’, and it has stripped out the ‘event/’ too! So I’ve actually managed to get what I initially intended!

Seem to be having a similar scenario to cmurockstar.

Started work on a site, had two pages already created and built (/contact/ and /about/), then went to work on two C.P.T’s. I’ve got Clients (/clients/%clients%/ – normal) and I’ve got Events (/%category%/%event%/ – category-based)…using this plugin to re-write the Event URL.

Now my C.P.T’s are working as intended, but my pages are now broken (404). I need to retain nice URL’s (/contact), so putting /page/contact isn’t really an option.

Any help / tips / advice will be greatly appreciated.

Hi Andrew,

I’ve got WP 3.1 and TinyMCE Advanced 3.2.7

Just thought I’d let you know that the problem persists back in this version. Don’t know if it helps you with any changelog-ing etc.

Hey tbp278, I just found this support thread because of the exact same problem.

It does appear that its an issue having Custom Post Types and Custom Taxonomies that have the same name. I had ‘Portfolio’ for both and the posts where 404’ing, I’ve just changed the taxonomy to ‘Work’ and the posts are now working fine.

“And disrupts consistent brand experience”

Looking at an alternative solution to this problem, you could always brand up the login page.

@zimbrul – in answer to your second question…

I’ve just made the switch to Yoast’s WordPress SEO from All-in-One SEO, and found that it also made the ‘Google XML Sitemaps’ redundant.

The latter is admittedly, more configurable…but I’ve seldom used many of the additional options that it provides. I’d say go with the one built-in to Yoast’s, and if you find any additional configuration that you need, switch back and tell Yoast…he’ll probably include it in the next update.

To be honest, I think everyone should look into stopping Fancybox loading on certain pages. It loads scripts, CSS and images everytime, but in retrospect the majority of scenarios only need them for ‘posts’. From an optimisation perspective, it’s not great for load-times / bandwidth etc.

At the moment, I’m wanting to switch off Fancybox for category pages; because it’s disrupting a script I wrote.

I think it’s something to do with this:
https://beerpla.net/2010/01/13/wordpress-plugin-development-how-to-include-css-and-javascript-conditionally-and-only-when-needed-by-the-posts/

But I can’t be sure until I read into it properly…I’ll let you know how I get on.

Hi guys,

Just a heads up for those using the ‘Starkers’ theme as your foundation:

The filter you need to comment out appears at ~226, not 262 like in TwentyTen.

add_filter( 'wp_title', 'twentyten_filter_wp_title', 10, 2 );