Announcing the ‘Read More Right Here’ Wordpress Plugin
I’m releasing the first of what I hope are many plugins for Wordpress. All of the details are at the new “WP Plugins” page here at wooliet.
If you’re reading this on the wooliet main page (with multiple posts listed), you can see it in action by clicking the link below. If the is the “single post page” display then..well….there’s nothing to see! Just go to Wooliet and find an entry with a link to more content.
(Updated with official WP plugin link)
I’ve tried to make it a very quick and easy plugin that can easily be thrown in and activated on any standard Wordpress installation. Another goal was to keep it ‘unobtrusive’ in that, once deactivated, there would be no trace left behind in the Wordpress database. Of course, at some point (if enough people use it), additional options might be necessary and beneficial. But we’ll see.
I’m still in the process of getting it listed and hosted with the official Wordpress plugins repository, but at the moment, the new subversion area for the code doesn’t yet seem to be available (anyone know how long that should take?). It took three days for the Subversion path to become active. The plugin should be available at the official location, which is right here.
As an aside and helpful tip for anyone else considering submitting their plugin to the official Wordpress listings: they have a “readme.txt” validator you can use to verify the correct syntax and content of the required “readme.txt” file. It was extremely helpful for me.
11 Comments
Congrats! It’s such a simple concept that you’d almost expect it to be the default behavior for WordPress. Maybe if you’re plugin is popular enough, it will be.
I can’t wait to see the next one.
hi, i just found your plugin yesterday, i love it. I have a problem though, I can only get it to work if my wordpress install is in the root folder (in that case it works flawlessly), and not, as i have it now, one level down.
I’ve installed wordpress in the /wordpress folder, and moved the index.php into the root folder, in order to keep things separated (as described here: http://wordpress.org/support/topic/168827).
I guess this messes with the paths for the ajax call, but I can’t figure out what to change to make the difference.
If you can help me out, I’d appreciate it a lot. (I’ll be donating once I solve this issue, because I figure I’ll be using this plugin a lot in future projects.)
thanks, Thijs
solved it… i should’ve looked in the php file that creates the plugin instead, all i had to change was line 52, where it says ‘get_bloginfo(‘url’)', and replace that with ‘get_bloginfo(‘wpurl’)', which produces the location of the actual wordpress install, rather than the blogs homepage location…
Perhaps you can change this in a next version.
in any case, cheers for this neat plugin! great work.
(my previous comment seems not to have arrived, i thought it was under moderation…)
To sum it up… i have my site running on WP, and i have the WP system files in a folder below the root level, yet i have the homepage of my site being generated by WP (as described here: http://wordpress.org/support/topic/168827). Basically this means the two settings for “wordpress address” and “blog address” (under ‘Settings’ in the admin area) are two different locations. Your plugin presupposes that the two are the same, it uses get_bloginfo(‘url’), so it does not load if like me you have wordpress one level down in its own folder.
Wow, nice work thijs. I’m sorry you had that problem, it’s not something I had considered.
I just tested out your change (after reproducing the problem) and it does work. However, there still exists another problem: the path to the “loading” image used (“ajax-loader.gif”) is now incorrect. The path to that file is constructed in the plugin’s javascript file (“js/wt_rmrh.js”).
To workaround this (for now), do two things:
1. In “read-more-right-here.php”, line 43, change “wt_rmrh.js” to “wt_rmrh-debug.js”
2. In “js/wt_rmrh-debug.js”, line 29 in the “getPluginUrl” function, modify the path to include the wordpress install directory
I’m going to see if I can’t fix the javascript problem. Once that’s done I’ll update the official plugin.
Thanks again for your help!
You’re welcome, thank you for taking a look. I’ll try your workaround and check back later for the update.
Have a nice weekend!
Is it possible to update the text of the link after clicking? I mean, before click it’s “Full variant” and after click it should be “Short variant”.
No, sorry, it’s not currently possible. That’s one of many little improvements I’d like to add at some point. The only issue is that I’s like this plugin to remain light-weight in the sense that it doesn’t muck with the WP database or alter behavior such that, when it’s deactivated, there’s all sorts of cruft left behind.
So something like “text to display after link clicked” might be implemented with a separate javascript file that contains nothing but configurable options the users can set. It’s either that or add a nice control area for the plugin in the WP admin area, which I guess is a possibility.
Great plug-in. I agree, it should have been standard out of the box for WP. One small question, though, how do you modify the font characteristics in “read-more-right-here/read-more-right-here.php” file for the “read less” text? I just want to make it bold so it is highlighted against the copy.
Thanks
Dean
@Dean Morrison
With the next release, I’ll have a couple CSS classes that get toggled on the ‘more-link’ anchor element. So you could style them (using your theme’s style.css) with something like:
a.rmrh-show-more { font-weight: normal }a.rmrh-show-less { font-weight: bold }
I’ll try and get that out within the next couple of days.
Alright, the latest version (1.1.4) adds ‘rmrh-read-more’ as a class value to all ‘read more’ links. When clicked, that class is removed and the class ‘rmrh-read-less’ is added. These classes toggle back and forth when the link is clicked.
So you can, for example, make the ‘read less’ link bold with the following CSS:
a.rmrh-read-less { font-weight: bold; }I hope this helps.