dansinch

I tried saving the contents of that pastebin to hashes-3.6.php and uploading it to the root of the WP installation but the plugin still reports it as missing. Am I doing something wrong?

Is it possible the version of PHP I’m running would cause any issues?

I started having problems with another calendar plugin that was throwing an error saying it couldn’t create certain directories because this server is running 5.2.x and 5.3 is required. I’m not sure how it worked before but I’m looking for something else now.

This is a client site so I’m not really familiar with the hosting company or how old PHP 5.2 is. They allow switching between PHP 4 and 5 but nothing more specific than that.

+5000 Seriously, this needs to happen.

The weird thing is I’m pretty sure I did the automatic upgrade from 2.9 to 2.9.1

Like I said before the upgrade doesn’t appear to be failing, it just stops after the first step because javascript doesn’t appear to be working on the upgrade page.

Yes let’s hope. Anyone? Just a hint maybe?

Also just noticed that after I get the “Downloading update from https://www.ads-software.com/wordpress-2.9.2.zip.” message, none of the javascript-y things work on that page (expanding menus, clicking the Help tab, etc)

I’m assuming the upgrade uses some kind of JS/AJAX type thing to complete all the steps without leaving the page. Why wouldn’t the correct scripts be loaded here?

After the upgrade failed, I noticed that there was a file in /wp-content

wordpress-2.tmp (0 bytes)

If I delete that file and try again, it just comes back. If I don’t delete the file and try again, it creates a new one called wordpress-21.tmp

Any ideas?

Would it make sense to make a copy of the album template like you would any other custom template? Anything custom that you put into your theme/nggallery/ folder would have to be patched on an upgrade anyway right?

That’s probably what I’ll do for now unless there’s a better way.

Also instead of trying to put everything into shortcodes you could allow each gallery to be associated with a custom template on the admin side (like how you can choose a page).

Deleting the domain cookies seems to have fixed the issue. I could log in and clean up the wpau files and reactivate plugins.

Deleting the cookies seems to have worked for me.

Are you adding the class to the posts themselves?

I think the basic idea would be that you set up a conditional for adding the class. First count the number of posts that are going to be displayed, and then start a counter to keep track of how many times you add the class to a post. When you get to the last one, don’t add it.

There are a bunch of ways to do this, so it depends on how you want to write it. If it’s not something you can come up with on your own, I can probably give you an example.

Sorry… the OS and DB versions should be exactly the same. Both sites are actually on the same server, just different domains. The main site is domain.com and the dev site is dev.domain.com

I actually realized that once I push the new site live, I can probably just hook them up to the same database. But right now, they’re using separate DBs.

So, really I just need to do a one time synch up to merge the DBs and keep all the newest stuff. I think all I really need to do is import the posts, comments and links/blogroll from the live site. Everything else can stay the same.

No one has an ideas on this? Any help would be much appreciated.

Thanks

I’m having the exact same issue. I’m assuming it has something to do with the way you acheive this effect. I’m not sure what you did, but I have a file called blog.php that is used as the blog template, and a Page called “Blog” with a slug of “blog”

Then, I have permalinks set up to use the name based URLs and have added ‘/blog/’ to the beginning of the custom blog url.

When a page is loaded it doesn’t use the long blog URL and correctly loads the right page. But then the blog is loaded, I’m guessing it’s using the custom permalink URL and not acually loading the “Blog” page.

Or I could be completely wrong, but either way, the current_page_item class is not being applied properly.

Anyone have any ideas why this would be happening? I use custom templates on other pages and they work fine.

That’s what I was trying to do. If you have something that would make that work, I’d love to see it.

Thanks!