An Update on Postalicious

Posted on by

This week has been a bit crazy. I’ve been trying to get some things done (like the Chaotica release I’m always talking about), but I been spending quite some time everyday answering questions regarding Postalicious and fixing bugs. Don’t get me wrong, I don’t mind helping people and fixing bugs, it’s just that my vacation is running out and I still have a lot of things I want to get done before it’s over.

Anyway, a few notes to all Postalicious users:

  • Please update to the latest version. I’ve been fixing some pretty serious bugs this week and if you’re stuck with pretty much any version before 1.08, chances are you’re going to run into some sort of problem, most likely getting posts claiming to be your bookmarks from 1969.
  • Please read the FAQ, chances are Postalicious doesn’t work like you expect it to work. I’ve received several comments from people who say that nothing happens when they click the “Update Now” button. It does work, it just won’t do what you think it does. Because of this I decided to add a FAQ which explains how Postalicious works and the reasons why I decided to make it work that way.
  • Feel free to contact me if you have any problems with Postalicious, I’ll try to do everything I can think of to fix your problem. You can use the contact link at the bottom of my site or simply post a comment in this post.

Finally, this is a link to the Postalicious page where you can read the FAQ and download the newest version. Also, I would like to thank Martin from admartinator.de for letting me know about several bugs earlier version of Postalicious had.

5 thoughts on “An Update on Postalicious”

  1. Hi Pablo. Love Posttalicious – I am running v1.09 and I have a weird problem. I installed it day before yesterday and everything went well but for some reason, it created 5 copies of the same post for Feb 19th bookmarks. I might have restarted Apache a couple of times for some other issues and so I’m not sure if that accounted for that? Any ideas? Figure I would ask you before diving into the code. Thanks

  2. Hmmm…that seems like a very weird issue. Whether to add new posts or not is determined by doing some calculations based on the server time, and I’ve tested that code quite thoroughly so I don’t think there’s a problem with that. However restarting Apache might have had caused some weird side effects, although as long as the server’s date did not change I there shouldn’t be any problems. My guess is that you won’t have that problem anymore as long as you don’t keep restarting Apache, but if you do just let me know and i’ll try to help you figure it out.

  3. I just started using Postalicious on our members web site. Small problem: any member who logs in can view the plugin’s configuration page. Is there any way I can mod this plugin so that only the administrator can see it? Obviously, I’d like to avoid having some rogue member come in and change all of the settings.

  4. Rob:
    Replace the function neop_del_add_options found around line 362 for:

    function neop_del_add_options() {
	global $user_level;
	if($user_level >= 6) {
		if (function_exists('neop_del_options')) {
			add_options_page('Postalicious',
'Postalicious', 1, basename(__FILE__), 'neop_del_options');
		}
	}
}


    (Note: add_options_page should be in one single line, but I had to split it into to lines for display purposes) You can change the 6 after $user_level >= to any other user level you might want to allow/disallow from using Postalicious.
    PS. I just updated Postalicious version 1.21 to include this change.

Comments are closed.