[SOLVED] 404 error with wp-print and wp-email
 

Excellent theme. Thank you for the hard work. Clap, clap, clap! (already sent money :))

Using Wordpress 2.7 and the latest download of Atahualpa 3.1.3. with updated (2.40) wp-email, wp-print plug-ins I am getting a 404 message (“Not Found - Sorry, but you are looking for something that isn't here.”) when I click on the footer entries “Print This Post” and “Email This Post”.

The post filename string being generated is good . . . up to the “/print/” at the end.

Should I be hunting for a mis-setup on my part . . . or could it be a bug?

Here is the string being generated:

“http://www.beautyprpro.com/merry-chr...ew-year/print/

Thanks again.

Alex Irving

It's doing that in WP 2.7 with permalinks on. WP 2.7 doesn't seem to add a trailing slash to permalinks. It may be related to that. I am looking into it.

It works with the new versions (2.40) of both WP-Print and WP-Email http://lesterchan.net/portfolio/programming/php/

Edit: I just saw that you ARE using version 2.40 of the plugin. After you installed the new versions you'd have to save the permalinks again. That's a general requirement for these plugins and not related to the theme.

You also seem to miss the trailing slash in your permalinks (unless you left them out on purpose). I was able to get them back by disabling and re-activating a few plugins and saving the permalinks again. I could not track it down to a specific plugin though. It may have been the outdated WP-Print/WP-Email plugins or not. It does not seem to be caused by the theme. The missing slash used to happen with the default theme too

The missing trailing slash on WP 2.7 permalinks seem to be caused by the WPG2 plugin

Did you read the instructions ...

... http://lesterchan.net/wordpress/readme/wp-print.html
... http://lesterchan.net/wordpress/readme/wp-email.html

Thank you both (Flynn and Chris) I am doing my homework. I appreciate the concern.

Alex

Trailing slashes OK and all works like a charm after following suggestions. RTDM (Read the darn manual <g>).

Thank you

Alex

you are welcome ... I have had the same issue last week and was about to start a thread ... but I found the instructions and it solved the problem ;)