Show Hide "more" with WordPress
Here is a plugin for wordpress using the latest version of the "show/hide" script (which lets you include other text inline, as well as opens up the doors to use the same function for comments) as seen here here. (Of course that post was written for MT)
Current Version: v. 1.4
Last Updated: 8/30/04 8:42 PM EST
See Bottom of post for changelog
Installation Instructions:
Step 1:
Download and "install" this plugin.
(ie. right-click and save that file with a .php extension. Then upload it to your plugins directory, which is located in your wordpress folder: wp-content/plugins)
Step 2: (optional)
I made that plugin for my own purposes with the text you see on this site. If you want the text to say something different – then you'll need to modify it.
(There was a step 3 – but it's not neccessary any more in ver 1.2 of this plugin)
Disclaimer: This is my first attempt to hack WP. The disclaimer in the sidebar VERY MUCH applies. I am NOT an expert. Especially when it comes to WP. So, go easy on me 
If you'd also like to do show/hide comments: see this post for ideas on how to edit your wp-comments and/or this post for a seperate file you can upload and use (wp-dropdown-comments.php)
An additional note I'll make here and on the show/hide more (comments) version:
Make sure you have the following in your template! (It's in the original WP index.php template, but if you're creating your own, you may have easily forgotten to include it) :
<?php wp_head(); ?>
That line would go in between your <HEAD> </HEAD> tags.
Change Log
new in ver 1.4
Bug fix for preview on edit post page (in the admin) thanks to Neil Stead
new in ver 1.3
Minor bug fixes thanks to Tormod
new in ver 1.2.2
Took Tormod's suggestions on code clean-up.
new in ver 1.2.1
echo was changed to return
priority added to add filter (thanks Kendra)
new in ver 1.2:
Added "add action" line (as suggested by Tormod) – so now you do not need to change your index template or any other plugins – use "the_content" as you normally would!
June 21st, 2004 at 6:24 pm
June 25th, 2004 at 7:34 pm
I finally installed my first WordPress plugin. Nothing major, just the show/hide more text one on scriptygoddess. So far, it seems a l [...]
May 20th, 2004 at 7:05 pm
Thank you! I was going to try to hack that one myself. It probably would have taken me days to get it working (I'm on a steep PHP learning curve at the moment.)
May 20th, 2004 at 8:19 pm
I was wondering… instead of putting the javascript in the head tags, could you put it in the quicktags.php file? It's located in wp-admin. If you have applied the wp-grins (smilies), you have to put that code in there, too.
May 20th, 2004 at 8:22 pm
I'm so glad you wrote this for WP! I had just fallen in love with this hack on MT and was hoping to find a good one for WP. Thank you, it works great!
May 20th, 2004 at 8:26 pm
waterlily – I admit to not knowing WP inside and out – but I think the quicktags.php is pulled into the ADMIN pages – not your content pages… but I could be wrong.
May 20th, 2004 at 8:36 pm
Thank you for the hack! After <div id='extText$id' style='display: none'> there needs to be a beginning paragraph tag for the code can be validated.
May 20th, 2004 at 8:43 pm
i'm not sure… i just know that with the wp-grins, you have to put some of your code in there… and then you have to put the same code (it's only one line) in edit-post.php and wp-comments.php
i'm just guessing…
can't wait to play with this plugin!
May 20th, 2004 at 8:54 pm
melissa – thanks! It's fixed now.
Waterlily – that makes sense – because wp-comments.php gets pulled on pages that show your comments form.
May 21st, 2004 at 12:36 am
You can eliminate step 3. Create a function in the plugin file that echoes out that code when called and call add_action('wp_head', 'yourfunction') in the plugin file.
May 21st, 2004 at 2:08 am
Something tells me that the latest exodus from MT to WP is really going to benefit the WP project. I'm definitely looking forward to your contributions. Now… if we could only get Brad Choate to convert.
"Hi, Brad… was just wondering if you could convert ALL of your plugins from Perl MT code to PHP WP code… I'll be your best friend!"
May 21st, 2004 at 2:54 am
WP just got very lucky. Great to see you here.
May 21st, 2004 at 7:43 am
Cool! Thanks Matt. I'll do that later tonight
Incidentally, is there somewhere that explains what "add_action" and "add_filter" actually do? My biggest hurdle in understanding everything is that documentation isn't terribly strong. I find myself actually going through the code in order to figure out what everything does.
May 21st, 2004 at 12:37 pm
Just want to chime in and say that I, too, am really happy to see you working on WP. So much so that I'm inclined to send a donation your way (not that I didn't value you before, but this really rocks
thanks for all your hard work and experimentation. It saves so many of us time, headaches and pain!
May 21st, 2004 at 4:04 pm
Yahoo! I've been using the hack and wanted this as a plugin instead so I wouldn't have to modify the regular code every time I update. I couldn't put my brain in gear to figure it out though. I'm so glad you turned it into a plugin!!! Glad you'll be digging into WP. We may end up with some great stuff.
May 21st, 2004 at 9:37 pm
Ok – I updated the plugin and the post. Now you just load it and call the new function!
May 22nd, 2004 at 12:08 pm
I can't get this to work for me. Do I need to put the javascript in the head? I've tried it with and without the javascript in the head and it still won't work for me. When I view source, it doesn't even show it in the source. I thought maybe it just wasn't showing up. Can anyone help?
May 22nd, 2004 at 1:48 pm
Two things –
Make sure you have the <?php wp_head(); ?> in your template (this is in the default template – and it appears after the <HEAD> tag but before the </HEAD> tag.
As well, make sure you've activated it through the "plug-ins" page in the admin interface…
May 22nd, 2004 at 5:38 pm
you so rock! thank you
May 23rd, 2004 at 6:38 am
Issue:
Because you are using a different function to display the content of the entry, any plugin which attempts to filter the output of the content of the entry won't work.
For example, at the bottom of the Google Hilight plugin:
add_filter('the_content', 'hilite');
This won't work, because you're not ever calling the_content()… you're calling the_contentshowhide().
So you'll have to add this line to the bottom of every plugin that is meant to modify the content of your entries:
add_filter('the_contentshowhide', 'function_name');
I'm not sure if there's another way around this, but that has worked for me.
May 23rd, 2004 at 8:50 am
Yeah – I don't think there's another way around it – as there is no way to override or redefine an existing function..
I'll update the post with that addition…
May 23rd, 2004 at 2:47 pm
I moved one of my other blogs to WP and couldn't be happier with it. So far I have the "Recent Posts" working. Am really glad to see this show/hide. Thank You.
I miss the Previous /Main/ Next on the individual posts. Going to start playing with that as well.
Love not having to rebuild.
May 23rd, 2004 at 2:51 pm
Charlene – that's really easy to to do – I'll make a post explaining it…
May 23rd, 2004 at 7:41 pm
Thanks for a great plug-in! I need to update the tutorial for the "read more" as it doesn't work with the latest WP version.
I cannot get the page to validate now that I have this installed though. I have tried everything and I still get these errors:
Below are the results of attempting to parse this document with an SGML parser.
1.
Line 120, column 3: end tag for element "p" which is not open
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element beeing used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
2.
Line 155, column 3: end tag for element "p" which is not open
No matter what I do, I have the error, any help would be great!
May 23rd, 2004 at 7:50 pm
Make sure you have the latest version of the plugin. There was a mistake that caused validation errors the first time I posted about the plugin…
May 23rd, 2004 at 7:52 pm
Yes, I just downloaded it and installed it about an hour ago.
May 23rd, 2004 at 10:31 pm
Plugin updated with what was causing the validation problem.
May 25th, 2004 at 2:28 pm
This works great, thanks! I was just wondering, were you planning on making a plugin for the "show more comments" feature, or is there an easy way to modify this plugin to do that as well?
May 25th, 2004 at 4:31 pm
It would make sense to combine them (especially since you only need the one javascript function – already being output by this plugin)… I will most likely do that… but honestly, my priority will first be to create a comment subscription feature for WordPress so that I can officially move this blog over. (That is now the one remaining item on my to do list before I can make the switch final)
May 25th, 2004 at 8:08 pm
Yea that's kinda what I figured. Rather than mess around with it and probably get nowhere, I think I'll wait and see if you work on it. I'm like you–just trying to see if I can get everything working the way it did on MT before switching.
Anyway good luck with the comment subscription feature! I know a lot of people are very grateful for all your hard work.
May 27th, 2004 at 8:31 am
Hi,
I am fiddling with trying to get the javascript to work as a wrapper around a comment block section which I have created.
I am looking at the code on my MT site (from you) and the new WP plugin. I have managed to get things 90% right BUT when I click on the 'show' link, it shows the comments (as it should) and then tries to load the linked page as well. Now I looked at the mouseover text in the browser for both sites (MT/WP) the constructed links look similar so I figure it must be something silly that I am doing.
Unfortunately the code is somewhat complicated to try and post. I was hoping that (a) you would recognise my stupidity from the description or (b) you would not mind me emailing the relevant section.
This is all running on my test server (which is not very stable yet). It may be visible at the same location but on port 88. Unfortunately I do not have WP running in production (yet).
May 27th, 2004 at 1:40 pm
Thank you ScriptyGoddess! I love the "more" plug in. You're awesome!
May 27th, 2004 at 9:02 pm
Jen, I took the tutorial off of Ten-Sixteen, please update this entry and remove the link, thanks!
May 29th, 2004 at 5:03 pm
hello jennifer! i'm sorry to sound so clueless with my question but i did everything in your steps, i uploaded the plugin and activated in in wp1.2. how do i actually use it? do i have to edit some code in my index.php? do i have to write some code when i write an post?
May 29th, 2004 at 5:04 pm
hello jennifer! i'm sorry to sound so clueless with my question but i did everything in your steps, i uploaded the plugin and activated it in wp1.2. how do i actually use it? do i have to edit some code in my index.php? do i have to write some code when i write an post?
May 29th, 2004 at 9:04 pm
got it to work, thank you!
May 31st, 2004 at 9:40 pm
hmmm, I wrote a comment yesterday thanking you for getting this working with the new WP version but I don't see it. I don't think I'm able to comment here.
June 2nd, 2004 at 11:49 am
As Matt said earlier: if you add the line:
add_action('the_content', 'the_contentshowhide');
just above or below the other line starting with add_action in the plugin, you don't need to change _anything_ in index.php, or any other plugins.
May 20th, 2004 at 7:44 pm
Scriptygoddess has four steps to using her WordPress 'more…' plugin. She uses javascript to hide the rest of entry. WordPress also has a built-in 'more…' ability which is a little simpler, but less flexible. The built-in feature may only be …
May 21st, 2004 at 5:33 pm
Congrats to my good friend the Scriptygoddess — she created…
May 27th, 2004 at 4:57 am
Since I use code by Scriptygoddess and other, I would now like to thank Scriptygoddess and the others.
May 27th, 2004 at 9:09 am
As you may have realised, I am working flat out on the WordPress migration. I have nice coloured comment boxes again. I have pull-quotes. I have blog statistics and a comment leader board. All sorts of features that you have come to know and love. I ev…
May 31st, 2004 at 5:34 pm
A slew of WP bookmarks, plugins, etc. as seen on Scriptygoddess:
July 6th, 2004 at 7:04 pm
July 12th, 2004 at 10:03 pm
testing show hide "more"
okay, one more to play with. it works!
chatt [...]
July 19th, 2004 at 10:54 am
July 20th, 2004 at 1:48 am
August 25th, 2004 at 7:59 am
August 23rd, 2004 at 7:18 pm
July 24th, 2004 at 5:21 am
August 16th, 2004 at 1:11 pm
August 8th, 2004 at 3:40 am
August 14th, 2004 at 9:58 am
August 1st, 2004 at 7:48 pm
September 18th, 2004 at 2:21 am
September 27th, 2004 at 1:42 pm
October 7th, 2004 at 5:20 am
October 21st, 2004 at 8:06 am
October 22nd, 2004 at 11:54 am
October 24th, 2004 at 5:32 pm
December 26th, 2004 at 8:30 pm
June 21st, 2004 at 10:24 pm
Or at least, it soon will be. I have decided that I AM going to switch my blog to WordPress….
June 21st, 2004 at 11:02 pm
Jennifer, thanks for the great work!
Unfortunately, I'm getting a Parse error on Line 15. I'm not sure what's going on, because this is a vanilla install of WP 1.2, version 1.2.2 of your plug-in and setting it up so yours is the only plug-in that's activated makes no difference. Help!
June 22nd, 2004 at 11:31 am
Or at least, it soon will be. I have decided that I AM going to switch my blog to WordPress….
June 22nd, 2004 at 11:39 am
Jen – I just wanted to say thanks for this plugin. I was using your 'show/hide' script on my MT blog. I'm working on customizing my new WP blog and things couldn't be easier with this plugin.
June 23rd, 2004 at 1:01 am
Working on hacking this blog to make it better.
Added Alex King's Clickable Smilies, so that I can add smilies to my post just by clicking on them and you can add smilies to your comments with a single click
(click!)
Also added ScriptyGod…
June 23rd, 2004 at 9:22 pm
Plugin updated to v 1.3 (thanks to Tormod!)
June 24th, 2004 at 4:46 pm
Okay.. this is now causing me errors which I am sure is due to the fact that I installed the first verison where you had to make the change in index.php.
Can you tell me what that change WAS so I can put it back so that I can get this new version to work for me please? Thanks!
June 25th, 2004 at 3:45 pm
I've installed the most recent version, and all was fine until I went to write a post. I got this message come up:
Warning: Cannot modify header information - headers already sent by (output started at /home/notsweet/public_html/words/wp-content/plugins/getContentforShowHide.php:112) in /home/notsweet/public_html/words/wp-admin/post.php on line 146The post still went through okay though?
June 25th, 2004 at 4:02 pm
That "Can't modify header" type error is usually a copy/paste error. Usually means there must be a space before the <?php or after the ?> in the plugin file itself. Check the file to make sure there are NO SPACES (or even returns) after that last ?>
June 25th, 2004 at 7:22 pm
Just an additional note: The "Can't modify header" information can also happen when you have two or more "things" (plugins, etc) that require you to wrap them in <? -and- ?> before the start of <html> – In my case, when I first tried to skin my site when I switched to WP I had code that looked something like this:
<?
require_once {'wp-blog-header.php');
?>
<?
include ('cookiecheck.php');
?>
I had to modify that, because once the very FIRST request is made (in my case, the require_once('wp-blog-header.php'); code) for "headers" you cannot make another request for them.
I altered the code and it worked fine after that. The end result was this:
<?
require_once('wp-blog-header.php');
include ('cookiecheck.php');
?>
June 25th, 2004 at 9:38 pm
Hi Jennifer,
First Thank you for the show/hide plug in.
Here is the bad part that I don't know if you want to solve or not.
If you have the MarkDown 1.0b4 activated at the same time as this new version of the plug-in, the xhtml does not validate. It did validate with MarkDown 1.0b4 activated and version 1.2.2 of the show/hide. I am not a php person at all, so I can't offer any ideas on why its happening, but I thought you might want to know.
Again thank you for the plug-in; in a effort to help out I will leave the MarkDown plugin activated with version 1.3 of show/hide activated in case anyone wants to see the xhtml errors.
June 26th, 2004 at 2:42 am
I installed your show/hide plugin version 1.3 on my WP nightly build installation and it is generating an error preventing me from loging into or out of my WP installation. Disabling the plugin enables me to login and logout though.
Warning: Cannot modify header information – headers already sent by (output started at /home/"accountname"/public_html/wp/wp-content/plugins/show-hide.php:110) in /home/"accountname"/public_html/wp/wp-login.php on line 44
Warning: Cannot modify header information – headers already sent by (output started at /home/"accountname"/public_html/wp/wp-content/plugins/show-hide.php:110) in /home/"accountname"/public_html/wp/wp-login.php on line 45
Warning: Cannot modify header information – headers already sent by (output started at /home/"accountname"/public_html/wp/wp-content/plugins/show-hide.php:110) in /home/"accountname"/public_html/wp/wp-login.php on line 46
Warning: Cannot modify header information – headers already sent by (output started at /home/"accountname"/public_html/wp/wp-content/plugins/show-hide.php:110) in /home/"accountname"/public_html/wp/wp-login.php on line 47
Warning: Cannot modify header information – headers already sent by (output started at /home/"accountname"/public_html/wp/wp-content/plugins/show-hide.php:110) in /home/"accountname"/public_html/wp/wp-login.php on line 48
Warning: Cannot modify header information – headers already sent by (output started at /home/"accountname"/public_html/wp/wp-content/plugins/show-hide.php:110) in /home/"accountname"/public_html/wp/wp-login.php on line 49
Warning: Cannot modify header information – headers already sent by (output started at /home/"accountname"/public_html/wp/wp-content/plugins/show-hide.php:110) in /home/"accountname"/public_html/wp/wp-login.php on line 53
June 26th, 2004 at 2:51 am
Ooops. Looks like I jumped the gun. I looked at my plugin code in HomeSite and found an extra space after the closing ?>. The plugin works perfectly now after I deleted the space, and I can login/logout now. Thanks for a great plugin.
June 26th, 2004 at 6:56 pm
Regarding the MarkDown plug-in and the show/hide plug-in being used at the same time:
After working with Jennifer last night, (read Jennifer telling me what to change and me doing it) the conclusion has been reached that MarkDown, when used at the same time as the Show/Hide script, will make the xhtml invaild due to the fact that MarkDown stips out <p> tags.
Just so there is no misunderstanding:
Show/hide without MarkDown will give you vaild xhtml.
MarkDown without show/hide will give you vaild xhtml.
Show/hide + MarkDown = invaild xhtml
June 27th, 2004 at 3:21 am
Rachel-G: This should be easy enough to fix. At least… in theory. See, when you make a plugin in WordPress to modify something, like the content of your entry, it has a priority. Priorities range from 0 to 10, and lower numbered functions are carried out first. Jennifer has given her show/hide plugin a priority of 0, meaning that it will be done first. If you open up the Markdown plugin file, you see this at the bottom.
remove_filter('the_content', 'wpautop');
remove_filter('the_excerpt', 'wpautop');
remove_filter('comment_text', 'wpautop');
add_filter('the_content', 'Markdown');
add_filter('the_excerpt', 'Markdown');
remove_filter('comment_text', 'Markdown');
No priority has been given to the Markdown filter added to the_content and the_excerpt. This means that it has been assigned the default priority of 10.
What you need to do is assign each of the plugins a new priority. Change the hide/show plugin to a priority of 5 or so, and change Markdown to a priority of 4. You may have to play around with this… if you have multiple plugins modifying the same text, you might have to close your eyes and grit your teeth to visualize the proper flow of the raw text through the filters. But setting Markdown to a lower priority number than Jennifer's plugin should be your first step. If all else fails, you can make a plugin to look for the particular error and fix it (set with a priority of 10, of course). WordPress's wpautop filter doesn't always produce valid code, so I had to make some preg macros to tidy those cases.
June 27th, 2004 at 6:55 am
I did have her play around with that – but it didn't make a difference. The problem is that MarkDown removes the ending P tag before the "more…" text – places the "more…" stuff inline – and THEN puts the ending P tag. Whether my script is run first or last – it will still do this. When it does this – the code becomes in valid because the drop down more stuff is in a DIV ID which can't live inside a P block.
Personally – I'm not sure why MarkDown is putting the P AFTER the "more…" text – but I guess it's a personal style issue of the plugin author. To fix it requires a (probably significant) change to the MarkDown plugin directly. (Which I wasn't going to get into) Or a change to my plugin JUST FOR MAKRDOWN – which I didn't want to get into either.
June 27th, 2004 at 7:27 am
Heh… now you know why I have a plugin filled with this crap to fix funky interactions between wpautop, your show/hide script, and other misc stuff.
$pattern7 = '</p></p>';
$pattern8 = '</div>nn</p>';
$pattern9 = '/</div>[s]{0,20}</p>/i';
$pattern10 = '&&59;& ';
$pattern11 = '</blockquote></p>';
$text = str_replace($pattern7,'</p>',$text);
$text = str_replace($pattern8,'</div><!– show more /p fixed –>',$text);
$text = preg_replace($pattern9,'</div>',$text);
$text = str_replace($pattern10,'&&59;&&59; ',$text);
$text = str_replace($pattern11,'</blockquote>',$text);
June 27th, 2004 at 4:55 pm
show/hide WP…
June 28th, 2004 at 1:12 am
It's probably just something stupid – I have the plugin working and all… but my plugins page (ie the page you activate them on) is all mess up, showing the code that's in the plugin's file on the page. I had this happen before with another plugin and fixed it somehow – but I can't rememebr how!
June 28th, 2004 at 1:16 am
Oh and also, when I post an entry now, I get the error
Warning: Cannot modify header information - headers already sent by (output started at /home/httpd/vhosts/littlelioness.net/httpdocs/wp-content/plugins/getContentforShowHide.php:101) in /home/httpd/vhosts/littlelioness.net/httpdocs/wp-admin/post.php on line 340any clues?
June 28th, 2004 at 1:19 am
At what age would you consider someone to be an adult? If you consider yourself an adult now, when did you start thinking that way? Was it at a certain age, such as the legal "adult" age in your state, or was it when you passed certain milestones, li…
June 28th, 2004 at 7:35 am
Fiona – please see highlighted comments above yours about the "headers already sent" type errors.
June 28th, 2004 at 10:00 pm
Cool
thanks for that 
(I really should learn to read previous comments properly! 0.0
July 5th, 2004 at 7:09 pm
Ooh, I like this plugin…thanks Jenn.
July 6th, 2004 at 3:36 am
I'm getting a validation error on my page – there is no attribute "onClick".
Since this seems to be integral to the way showHide works, I guess it must be something I'm doing wrong.
See: http://www.glug.co.uk/newsite/index.php
Any help much appreciated!
Neil.
July 6th, 2004 at 3:40 am
Just figured it out… somewhere along the line "onclick got changed to onClick. Sometimes I hate case-sensitivity!
Neil.
July 6th, 2004 at 3:43 am
Niel,
Open up the plugin, and search for "onClick".
Replace all instances of "onClick" with "onclick".
XHTML requires lowercase.
<a HREF="test.com">test</> would also generate an error, because it wouldn't recognize "HREF".
July 6th, 2004 at 3:46 am
Sorry, a little late on that one.
Glad you figured it out.
July 6th, 2004 at 12:57 pm
Arrrrggghhhh! Worked out how the "onclick" got changed to "onClick" – it's Dreamweaver MX, which I've been using for HTML for years. Apparently it won't produce compliant XHTML unless there's an appropriate DTD at the top of the file – even if you've got the "Produce valid XHTML" option selected!!
July 7th, 2004 at 2:02 pm
I'm having a problem with this. Since I upgraded to Mingus, I can get my open/close comments to work with this plugin, however, show/hide entries won't work. I'm taken to the main page of the post just as if I didn't have the plugin activated.
I can't figure out why one would work and not the other. I do have the snippet of code between the head tags also.
July 7th, 2004 at 5:54 pm
I'm sorry to ask yet another newbie question. I followed the steps. plugin wp_head, etc. What I just don't get and don't seem to find anywhere is how the call the script?
Instead of , what do I type after the line I want it to showHide?
I would really appreciate your help.
July 7th, 2004 at 6:45 pm
Marius – you don't need to do anything special. You just use the normal the_content() call, and it will do the hide/show more links for the "more" text.
Gina – Unfortunately, the plugin doesn't take "customized" text for the link. If someone has a way to do it without modifying the plugin itself, please let me know – otherwise, if you want custom text for the "show hide" link – you'll need to modify the plugin – Line 93 for the "Read more or read more right here" link. Line 99 for the "hide it" link.
July 8th, 2004 at 5:43 pm
I'm sorry Jennifer, I realize the sidebar disclaimer applies to me, but I so much luv this pice of code, I hope you can bear with me on this.
I have the_content() call in place as well as the plugin activated. I also made sure the wp_head is in place. However I see no difference on my page.
oomsonline.com
I'm also using my-hacks.php. Could that throw off the plugin?
July 24th, 2004 at 3:39 pm
I implemented the show/hide feature after taking some time and carefully reading some articles over at Scriptygoddess' website. Thanks, Jennifer!
Here's what I did…
1. I went to Scriptygoddess' article and installed her plugin getCont…
July 24th, 2004 at 3:57 pm
Love the plugins/hacks. Love your site! You are very talented!
July 26th, 2004 at 2:51 am
Hello, when I activate this plugin I get the following error:
Parse error: parse error, unexpected T_VARIABLE in /home/mysite/public_html/felixe/wp-content/plugins/getContentforShowHide.php on line 125
What could be the cause? I reinstalled it several times and checked the code but still nothing.
Thanks,
Felixe.
July 26th, 2004 at 11:58 am
here's my "more" code:
onclick="showHide($id,'".get_permalink()."',this,'entry');return false;">more
why isn't the rest of the entry popping up? i get forwarded to the permalink instead
July 26th, 2004 at 11:58 am
reposted, oops
<a href='".get_permalink()."' name='ext$id'
onclick="showHide($id,'".get_permalink()."',this,'entry');return false;">more</a>
August 1st, 2004 at 11:08 pm
As mentioned by some of the others, I am having the problem of all the code from this plugin showing on my plugins page. Once the plugin is activated, the code from the first half of the plugin also shows on my page, above the title bar. After checking the plugin file and fiddling with a few other things, I am stumped! Any suggestions? I left the plugin activated on my page so it would show what is happening. Thanks for any advice!
August 7th, 2004 at 1:36 pm
Finallly got the plugin to work and descovered that it breaks post preview in wp admin. Post preview will now only show the title and the catergory. Did the newbie break something again?
TIA
DA Williams
Tech Blog
August 10th, 2004 at 2:41 pm
Hey, I tried to go through all the comments looking for this one but I kinda zoned out after 50 or so…
Will this slow down the initial loading of my page much, if at all?
Thanks!
August 15th, 2004 at 6:45 pm
I finally installed your Show More plugin today. So basically, this adds a
Read more… or Read more right here… » right?
Is it possible to separate those two? In some of my entries I like the having the first type of Read more only and in others,i like using the 2nd type only. I don't want to give my blog readers the option of choosing one of them.
August 18th, 2004 at 3:51 pm
Great plugins Jennifer. I'm having a problem with this one in particular though, as well as a couple of others. I have downloaded the plugin and uploaded it to my server as the instructions explain. Before uploading I have cleared any and all white space at the tail end of the script as required for successful use.
The problem that I have is that when I activate this plugin, the script itself displays at the top of my home page. I have tried trial and error of just about everything on this topic and have yet to find a fix. Any help on this is much appreciated.
August 21st, 2004 at 1:12 pm
I had the same problem as Chad and others, with the code appearing on my site. I originally installed the plugin by rightclicking the plugin and saving it as a php file, only to have it display a massive chunk of code on my admin and index pages.
HOWEVER, I installed it a second time by clicking the file to load in my browser, then selecting everything and copypasting it to a new php file. I uploaded it, and the problem was solved. I don't know what exactly caused it, but the most obvious difference between the two files is the lack of coloring and line breaks.
When using this method, I later got the Cannot Get Header error, which Zack already posted a solution to (make sure all spaces and returns after the last characters are eliminated).
August 29th, 2004 at 1:18 pm
Jennifer – as mentioned above, the plugin breaks the Preview on the Edit page – the content isn't displayed.
I'm sure it should be possible to put a check in to see whether the current page is the Edit page, I'm not sure how.
August 29th, 2004 at 9:02 pm
I hadn't noticed the previous comment, nor the fact that this plugin was causing that problem. I will work on fixing it, but due to some personal issues going on at the current moment, it will have to take the backseat. So… it may be a little while before it's fixed… but suffice to say, it's on my radar now.
August 30th, 2004 at 8:47 pm
Plugin updated to 1.4 (bug fix thanks to Neil!!)
August 30th, 2004 at 8:52 pm
Pei's been lurking around in Squeak (gone!) and Journal form……. but it seems the Toothpaste Addict is back! *and there was much rejoicing*
The show/hide more plugin for wordpress has been updated to
September 1st, 2004 at 5:09 pm
great plugin again!
but somehow I get xhtml validation errors
<p><div id='extLink47'>
= document type does not allow element "div" here
any ideas?
September 2nd, 2004 at 4:25 pm
hmm, nm .. seems there's a conflict with Markdown plugin
I read your comment a couple of 'comments' ago
September 3rd, 2004 at 8:31 am
problem:
i installed the plugin , activated it and inserted the line into the index.php, but i get this when i try to post a new entry,
Warning: Cannot add header information – headers already sent by (output started at /srv/www/htdocs/wp-content/plugins/getContentforShowHide.php:1) in /srv/www/htdocs/wp-admin/post.php on line 146
did i miss a step, btw it is WP 1.2
September 4th, 2004 at 5:46 pm
Hey Jennifer, would it be possible to have this plug on individual entry pages as well? I'm building a site with an archive of magazine articles and I wouldn't like comments to appear under the article before they're "opened". Is that possible?
Thanks:)
September 13th, 2004 at 6:24 am
I run on WP ver 1.2 mingus and have installed the dropdown "more" plugin.
In attempting to activate the plugin I receive the following message:
"Sorry, you need to enable sending referrers, for this feature to work."
I have checked both my browser and firewall (Zone Alarm) and everything "seems" OK. Any suggestions.
September 13th, 2004 at 12:24 pm
Marc, this is due to settings in your firewall software, which are preventing your computer from sending information about the previous page you visited.
If you're using Norton, you can find this on the "Web Content" tab of the Options page.
September 13th, 2004 at 12:25 pm
Whoops – just noticed you said you were using Zone Alarm, not Norton. I'm pretty sure it's a firewall problem – I've had exactly the same thing with other plugins.
September 13th, 2004 at 6:07 pm
It could also be a browser setting. I think some browsers can disble referrer sending. I know that I have problems with referrer sending features in the admin when I use my T-Mobile SideKick's browser.
September 14th, 2004 at 10:25 pm
As per my last post I have solved the referer problem. It was a browser setting. I still haven't found the setting in IE6, but it works when useing Firebird.
Since activating the plugin I noticed another problem When useing the function in IE6 it work OK. BUT when viewing the page in Firebird and clicking on "read more here," it will monetarly open the extended entry then a couple seconds later the display will shift to the individual entry archive. In other words the same as clicking the "read more" link.
You can view the results here: Cranial Cavity
September 15th, 2004 at 8:35 pm
In ref to my last (comment #86)I have disabled the plugin. I have discovered that with it enabled I am unable to use the "login" line in the sidebar, or the "edit" link in each post. They both return an error on parsing the plugin.
Has anyone else had this problem.
September 15th, 2004 at 9:56 pm
Strange:
Now the "edit this" link works (both in IE6 and Firebird) with the plugin activated.
But the "login" link in the side bar returns this:
" Warning: Cannot modify header information – headers already sent by (output started at /home/cranial/public_html/wordpress/wp-content/plugins/showhide.php:119) in /home/cranial/public_html/wordpress/wp-login.php on line 257
Warning: Cannot modify header information – headers already sent by (output started at /home/cranial/public_html/wordpress/wp-content/plugins/showhide.php:119) in /home/cranial/public_html/wordpress/wp-login.php on line 258
Warning: Cannot modify header information – headers already sent by (output started at /home/cranial/public_html/wordpress/wp-content/plugins/showhide.php:119) in /home/cranial/public_html/wordpress/wp-login.php on line 259
Warning: Cannot modify header information – headers already sent by (output started at /home/cranial/public_html/wordpress/wp-content/plugins/showhide.php:119) in /home/cranial/public_html/wordpress/wp-login.php on line 260
Warning: Cannot modify header information – headers already sent by (output started at /home/cranial/public_html/wordpress/wp-content/plugins/showhide.php:119) in /home/cranial/public_html/wordpress/wp-login.php on line 261"
September 15th, 2004 at 10:00 pm
The above error is also returned when I attempt to access via the normal the login page. (ie enter login and password)
September 22nd, 2004 at 11:26 am
Okay I know this is a bit unrelated, but this is the only place I can think of where I've seen this right now.
I want to be able to do something like this show/hide more but outside WordPress, just in a normal page.
Do you have any links to point me to? It would be greatly appreciated. Thanks!!
September 22nd, 2004 at 11:44 am
show/hide anything
September 22nd, 2004 at 11:45 am
I should add that I haven't gotten around to updating that show/hide anything version of the script to the latest. So until I do – while, it still works, it MAY cause your page not to validate…
September 22nd, 2004 at 12:34 pm
Thanks, Jennifer! (Please excuse my ignorance)
I'm not worried about the validation, I can never validate anyway (besides css) because if for no other reason, I have a habit of doing br instead of br /. lol
Thanks!
September 29th, 2004 at 9:27 pm
I'm blind. How do I actually use this thing? (plugin already installed)
Can it be configured to automatically place "more…" after a specified amount of text characters?
September 29th, 2004 at 11:34 pm
eRRaTiK, click the "more" quicktag, or just type: <!–more–>
This will set the break point on the main page, but on the individual archive, it'll show the whole thing as continuous.
P.S. Don't put the "more" before the end of a tag or anything… in fact, it's a good idea to do a line break before and after it just to be sure that the paragraph formatting will look right.
September 30th, 2004 at 12:52 am
right. i officially need to have my eyes checked.
thanks once again Mark.
September 30th, 2004 at 10:55 am
I'm having the same issue marc is in regards to the header out put. I checked the file for extra spaces and returns, deleted them and reuploaded. I still get the warning for header output in regards to lines 257-261. Any other ideas of conflicts and where to look to modify. I spent a good while trying to troubleshoot, but nothing's working.
October 11th, 2004 at 5:32 pm
Well, I've taken the plunge, sorta. Again. Whatever. I've migrated from b2 to WordPress. Let's face it, b2 was defunct. Development had officially stopped, and it was quickly falling behind.
WordPress offered regular updates, and flexibility…
October 22nd, 2004 at 4:46 am
i tried it again from scratch and i got it working …. thanks for this plugin !!
October 24th, 2004 at 1:16 pm
Great script! I really wish WP would follow established blogware standards and put things like this in automatically, but this is the next best thing.
One thing, though: When I click on the "hide" link, the text does scroll back up, but I also get a separate popup of my blog front page. Any way to eliminate this? (I realize popup blockers will kill this, but I want to eliminate it altogether.)
The only hack I'm made to the getContentforShowHide file is to delete the "Read more or" permalink, and re-worded the "Read more here" and "Hide" links.
December 23rd, 2004 at 10:38 am
Has anyone found a way to get this plugin to work with markdown?
January 2nd, 2005 at 3:44 am
Some people have posted issues about this plugin — the "more" link taking them to the Permalink after briefly displaying the extended entry.
I'm having the same problem. Has anyone figured out how to resolve this issue?
January 5th, 2005 at 1:48 am
For those of you wanting to change how the 'hide comments' procedure works so the browser does not scroll back up the permalink, I have two options that work on firefox and IE6 and I think are still valid XHTML.
Open up the wp-dropdown-comments.php and find this line (line 29 if you haven't edited the original):
<a href="#com<?php the_ID() ?>" onclick="showHide(<?php the_ID() ?>,0,this,'comments');return true;">Hide Comments</a>
and change it to:
<a class="hideComs" onclick="showHide(<?php the_ID() ?>,0,this,'comments');return true;">Hide Comments</a>
You will also need to add the following CSS:
a.hideComs {
cursor: pointer;
}
This basically removes the href completely and the CSS causes it to behave as if it was a 'link'. Beware if older browser support is important.Use/test at your own risk, just wanted to share my solution.
January 5th, 2005 at 10:39 am
It did not work.
January 26th, 2005 at 1:19 pm
How can I change it to show another saying. So instead of reading "(more…)" it would read "read more…" I tried changing all the references of "(more…)", but it isn't working.
Also, Gerry, I'd like it so the focus did not change to the permalink, but stayed right where it was on. It worked well on MT.
January 27th, 2005 at 1:28 pm
When I use the show/hide plugin in wordpress 1.2.2 in the middle of a sentence, it cuts that part of the sentence and starts whats after <!–more–> on a new line. I'm also having problems with it changing the font after the more line also until I use the <br /> or <p>
January 27th, 2005 at 1:35 pm
The script wasn't designed to be used in midsentence. It would probably take a little hacking to get it to work like you want.
January 27th, 2005 at 10:10 pm
Is there a hack or workaround so that the screen doesn't scroll down when you use "hide it"? so that it just stays in the same view as when you clicked it to show? and what is the #ex5 and #ex3 I get when hiding the content? Thank you for such a quick reply by the way.
January 27th, 2005 at 11:05 pm
I think comment #102 will help
February 28th, 2005 at 7:06 pm
I have wordpress 1.5 installed, and followed your instructions, yet I don't see any way to post where some of my post can be hidden like I could in mt. Is this plugin compatable with 1.5?
March 4th, 2005 at 6:21 pm
I can't get this to work with WP 1.5 Is it a compatability issue? When I include the header tag, like instructed in the script, I get errors about the header info already being sent out. Any help would be appreciated!
March 5th, 2005 at 8:38 am
I have actually gotten it to work as is in 1.5. Those "headers already sent" errors are usually tell-tale signs that there is a space before the first <?php or after the last >? in your plugin file that you uploaded. You may not even see it. So make sure there's no extra line returns or spaces in there…
March 6th, 2005 at 2:59 am
I tried installing it in WP1.5 but my layout loses its formatting. (sidebars end up at the bottom of the page and the main column extends the full width of the window. I've checked for spaces before and after < ?php and after >? and there is nothing. It was working fine in WP1.2.2. What could be the problem?
March 6th, 2005 at 9:33 am
Sounds like more of a css/html/layout issue. I would suggest viewing source on the page that is displayed in your browser and checking it from there. (Or try validating the page – it may find any unclosed tags – or too many closing tags – you have in your layout)
March 8th, 2005 at 7:23 am
Thank you. It's working now!
April 1st, 2005 at 2:06 am
I really need some help getting the Show Hide plugin working on my WP 1.5 site.
The part I guess I'm really missing is what file the <?php wp_head(); ?> goes into? My index.php (located under my wp-content/themes directory) has no <head></head> tags so the plugin javascript isn't getting called.
Any idea where this is supposed to go?
Baden
April 1st, 2005 at 8:57 am
If you don't have head tags there – then you probably have a "header.php" file somewhere with your theme… (Although, I'll have to check, because I don't remember – but I think that should be in there by *default*)
April 1st, 2005 at 8:59 am
"but I think that should be in there by *default*"
Just to clarify – I meant that the <?php wp_head(); ?> should be in there by default…
April 1st, 2005 at 10:21 am
Just an FYI for anyone using the Miniblog plugin, something tres weird happens when you have that and Jennifer's show hide more plugin.
For some reason, the mini blog plugin will pull from a WP blog entry as plug it into the mini blogs a few times over. The S/H will function though..it also won't play nice with the nextpage tag either, but I suspect that's something to do with the theme [Wuhan].
Haven't had much chance to look at it, and I've disabled the S/H plugin until I can see what's what. Just thought I'd mention it, cause I really like the more tag behaving this way than as is.
April 18th, 2005 at 2:38 am
Great plugin, it took me hours to find it, and of course it's on the most obvious site!
When I use the "read more right here" option, it doesn't open up inside the same page as it does on your site. Any ideas why this might be? Is that a different script altogether?
May 19th, 2005 at 5:56 pm
Just installed the read/hide plug in –THANK YOU! Works like a charm. I even went in and took out the Read here or line and had no problems.
May 30th, 2007 at 11:55 pm
[...] Pluginé…布元:Content with show/hide javascript for "more" [...]
July 13th, 2007 at 2:00 am
[...] Visit [...]
December 8th, 2007 at 6:59 am
[...] Google??????????????????????? scriptygoddess » Blog Archive » Show Hide “more” with WordPress [...]