HallMarc

@mrppp They are still visible and editable on the posts/pages that have them set prior to the upgrade.

@mrppp Glad you asked that question. I ran the updater again and then checked my redirect pages – they are not only still redirecting BUT I still see the 301 redirect field. This field seems to only appear only pages that already had it set prior to the update. All others do not have the 301 field showing.

Secondly, I looked at the Details screen where we can read about the changes in v 2.3 it does say that this feature has been removed/moved to premium. So we were given warning.

Just to clarify, redirects still work and are still visible editable if they were created before the 2.3 upgrade.

I have one other site to test these findings on and will post if I find anything different.

@mrppp I didn’t check if they where still redirecting after the feature was removed. Sorry.

Interesting… My first comment seems to have vaporized.

I find this to be in very bad form. No warning on a change that will cause the community that doesn’t want or maybe can’t purchase the pro version to get this back. The simple fact that you have essentially taken a feature many of us are dependant upon as hostage until we pay $69. I will be looking for a new plugin. Thanks for the years that this plugin was helpful.

Personally, I have a copy of the previous version and pushed this back to the server. The redirects reappeared so at least they weren’t removed from the database during the upgrade.

For my site this error message was a false positive and from what I see wasn’t meant to be seen. A plugin I have; ZoomFolio also has a css class declaration for .hidden and this was overwriting the WP style and showing the error meant to be hidden.

As they have said and if you haven’t already, check your theme and plugins for issues like this. Inspect Element may help you pin point the trouble maker.

I have found that the error was showing even though it was meant to be hidden by css because a plugin css declaration was overwriting the WP default for .hidden class. The plugin causing it for me is ZoomFolio portfolio plugin.

Make sure you check all of your plugins for conflicts.

Ok I have found that the Layer Slider has a style that is overwriting a style that would normally hide that error statement. If you inspect element, you may notice that the div block it is appearing in has a class of hidden. If so then you aren’t meant to see this. As the admins have been saying, check you plugins and theme.

@jan and @esmi we are all correct….

@yogachikitsa I see an attempt to create a child theme has been made. Look at the header info in the css and you will see why I said it was prpoerly child-themed. I kept missing that the path to the css file was proving otherwise.

You essentially have your own custom theme that will not benefit from any updates from the original authors. Not a death knell by any means. What you could do is try to download a fresh copy of the twentyeleven theme and then follow the codex for the proper way to do this. The part that seems to have been missed for your theme is the part where you create a new theme folder (i.e name it twentytwelve-child), create a new css file in it named style.css and go from there.

@esmi – Look before you leap. yogachikitsa has a properly set-up child theme already. Easily determined by looking at the css header.

I would look at the WordPress Codex for using conditionals. I will post back shortly. Just got called away. esmi could show you to the section or maybe show a sample is_front_page() usage.

@esmi Yes, I am a full-time freelancer; have been for 11 years. I am not attempting anything nefarious; just trying to help this person out.

Hmmmm… I’d bet dollars to donuts that it is server side. I have to take off for now; dinner time here, and I would like to take a look. [Moderator note: These forums are not to be used for soliciting work]

Yes, BP is a learning curve and it needs to have a BP friendly (BP compatible/ready) theme or it won’t work.

I don’t have much experience with the multi-site aspect of WordPress so I can’t be of much use past this point.

You could try this plugin though; Front-End Users.

Please post back if you find a solution.

Do you have the skills to edit your header.php file?

What is the address? Who are you hosted by? When did this start? What changed before the problem began?

Are you using the BuddyPress plugin?