terry777

Thank you so much for pointing me in the right direction – RSS feeds didn’t even cross my mind. Looking at plugins now.

I would like to know this as well, thanks.

Are you talking about the Activity Log of the person who clicks the “Like” button, or the Activity Log of the facebook page of the page on which the “Like” button appears? or both?

It took me awhile, but I think I finally figured this one out. When you put a like button on a page and the code generates a like for that page, rather than a facebook page, it shows up in the facebook timeline, but does NOT increment the number of “likes” for the facebook page. It is only when a like button “points to” a facebook page that the number increments. So, when generating “like button” code on facebook’s support area, you have to supply a url to “like”. If you specify a facebook page (but put the code on any page, wordpress or not), when the user presses the “like” button, it generates both a post on the liked facebook page, and increments the facebook page’s counter. If it’s a non-facebook page the code is generated for, only the post appears on the facebook page, and the number of likes on the facebook page does not increment, and the number that appears on the wordpress page next to the like button has no correlation to the number of likes on the facebook page. I think the same is true if the code is generated by a plugin.
Uh, I’m not sure that clarifies, but I’m hoping it does.

so it’s sort of both a “like” and a “share”

I don’t know if it’s a coincidence, but since I didn’t get any replies, I looked around a bit at others’ problems with the upgrade, in case I missed something that was related, and one mentioned something about refreshing the permalinks because they were getting 404s for all their blog pages. So, I did that, and then set the number of images per page back to 20, and voila, it’s paging correctly now, no 404 when I try to view the 2nd or 3rd gallery page. Just wanted to post this in case someone else has a similar issue. Of course, if it IS just a coincidence…

I should have added: Is there any clever way to get around this? Is there a way to force a password even when the user uses the BACK button to return to the page?

I found that the code from MickeyRoush worked as long as I didn’t use the BACK button to navigate back to the page, although in Safari it worked then too. Is that because using the BACK button causes the cached page to display, whereas typing the address into the address bar re-loads the page?

Since my last post, under the file structure which mimics the old blog I created a directory for each of the original blog slugs, and put a default.html file in there to tell them where to go to find the new blog page. This is only a temporary solution, so they don’t get the 500 Internal Server Error, and only works for those slugs. So, if someone has bookmarked the post, at least they can find the new blog page.

However, if I mistype a word and the directory doesn’t exist, I don’t want to get the 500 error, I at least want to get a 404.

Since the new blog pages and posts work perfectly fine, is it unlikely to be a plugin incompatibility? From what I understand, the 500 error is pretty generic, so I can only go by what I think might be causing it.

I also deleted the .htaccess which resides in the top level of the site and created a new one by updating my permalinks, to make sure I didn’t get anything funky in there.

Do I need an additional .htaccess for the subdirectory/subdomain called “blog”, or do I do it all in the one for the main domain?

So right now, I have nothing in the .htaccess to tell the search engines where the new pages are.

Does it matter where I put the redirects in the .htaccess – before or after the code generated by updating the permalinks?

I too am looking for an easy way to add an employee schedule – either with a theme or plugin

Today I also tried using id= instead of name=, with the same result – works in Firefox, not in Safari. I know name= work in a regular html page in Safari, just not in WordPress.

I should have said that I search within the forum for Bytesforall, which created Atahualpa and didn’t find the issue there.

I also searched the forum for Atahualpa with no success

My Safari is 5.0.4, but the person who alerted me to this problem is also using Safari on a MAC, and I don’t know what version. I have tried Firefox, IE and Chrome, and they all work.