lomara

I have also not been able to get my wordpress site to connect with tumblr in this plugin, and have been trying everything in this thread without success.

I enabled debug logging, and found this in my log:

[25-Oct-2014 05:50:59 UTC] PHP Warning:  Unknown: open(/var/php_sessions/sess_6d0319c1dcdea40d28c5473c652466b0, O_RDWR) failed: No such file or directory (2) in Unknown on line 0
[25-Oct-2014 05:50:59 UTC] PHP Warning:  Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/var/php_sessions) in Unknown on line 0

I don’t have shell access on my host, so I can’t access /var, or anything outside of my /home directory. I can only access my /home folder.

However, my host does allow me to edit php.ini. (I’m on ipower, and this is found under “CGI and scripted language support > PHP Scripting”. My host is running PHP 5.3.13)

I changed this line in php.ini:

session.save_path = "/var/php_sessions"

to reflect a path that already had a phpsessions directory I had access to in my /root path. It looks like an older version of php used it, and was no longer used when my host upgraded PHP.

Changing this session.save_path fixed my issue, and now the plugin can connect to tumblr, shows my tumblelog, and everything seems to work as intended.

I wanted to share my solution, in case it could help someone else.

Thanks for the clarification podz.

According to this article at Cnet, there is a new Linux worm which exploits this vulnerability. Symantec and McAfee each have posted descriptions of this worm which show it is attacking the xmlrpc.php file in WordPress. I take it that those of us running 1.5.1.3 or the current release are now immune to this?

Updated WP-Gallery 1.0 (Now called WP-GalleryUpload) by ChuckG at Blindmuse.com has been updated to work on WordPress 1.5 by me.

This plugin integrates image uploading from your Gallery(https://gallery.sourceforge.net) installation directly into WordPress 1.5.

Get the plugin here

It is working fine on my WP 1.5 install. Just unpack the zip file and follow the instructions in the ReadMe.txt file. I wrote the instructions from scratch, so feel free to correct anything I left out!

chuckg, if you still read these threads, I’ve updated this plugin for use with WP 1.5 and would like permission to release it. Check your email! ??

Same here. Seems like an epidemic.

Happy Birthday Matt! May you have a very memorable birthday, and may you be sober enough to remember it all! ??

Cutter
LJ Plugins
Hope this helps.

Disregard my last post – I found that I edited a tag to accomodate a plugin, so I had to edit the exhibit plugin to use my custom tag (the_contentshowhide instead of the_content) and now it works great.

https://www.danvine.com/icapture
Try this to view any URL inside one of two versions of Safari.
I just submitted it, but it is very busy and is now in the queue. It should come up soon.

I just got word from Fahim that the fix is here: https://weblogtoolscollection.com/archives/2004/06/04/wpblacklist-121-released/
I’m going to try it out now.

I’m getting the same error as well. WP 1.2 , blacklist v.1.2 as well.

southerngal, just make the edits in the script to point at your database, choose the age of comments you want to close, and load the page in a browser window. It will run just by calling it with a browser.
Podz, you could add it as an entry in menu.php, then run it periodically from the admin screen. That’s one option. If you are running 3 blogs in a single database, then you would probably have to make 3 copies of the script, and edit the table references to point at each blog post/comment table individually. It would be clunky, but it could work.
I’m sure if others have better suggestions they’ll let us know. I’m still a newbie at php.

I’m another one of those that switched from MT to WP in the recent ruckus. It wasn’t because of the licensing fiasco, but because it wasn’t such a big update over the previous version, and I got tired of waiting for 2 minutes for a mere 200 posts to rebuild. I’ve always enjoyed the dynamic nature of PHP more.

Ditto here. I have been looking at PHP CMS’s off and on for a while now, and i guess the hoopla with MT3.0 helped me make a solid decision to switch to something PHP based. The rebuild issue is a big deal to me. Plus I hated the fact that if I deleted an entry from MT, the script would not delete the static archive page as well. You had to delete the page and do yet another rebuild. It was a slow clunky way to do things IMO.
The other CMS I was looking at was Textism, and while I still like that one, there seemed to be more participation with the WP community, especially when it came to hacks & plugins. Granted I only tested Textism out for a couple of days, so I guess I’ll find out if I’ve made a hasty decision. But so far I’m quite happy with WP.
Especially the wp-gallery hack! I LOVE that thing. I can’t wait until someone integrates it better than I did in 1.2. It’s brilliant.

I don’t have any categories that have the text “fit anywhere else” in them, so I’m not sure what field your script is choking on. I’ll start surfing my sql tables and see what’s up, but I’m a novice at this and it’ll take time. I’ll let you know once I find it.