flipdeluxe

OK

Update for those who experience a similar issue with reimporting a database and find that their Text Ex widgets were not re-imported with the rest of the db

In the end I was able to manually reconstruct the Text Ex widgets by searching through the exported sql file for some of the html code I remembered being in one or two of them.

I found the relevant sections in the sql file, copied them out and removed all the line break escape chars , filter code etc, then from the resulting html code recreated the Text Ex widgets in WP and paste the code in, and saved.

I have also created a little code library with copies of all the Text Ex widgets in case the deb needs to bere-imported in the future.

I am not sure if this problem occurred because I used a phpmyadmin export file to reimport or if it was an sql file exported via a backup plugin in WordPress itself.

As I said the widgets were there in the db export file, they just didn’t get included on re-import.

Hope this helps.

Looking through the imported sql file, there is d3efinitely reference to “widget_textex” instances.

Andrea

Thanks for the reply, what I’m saying is the Text Ex widgets don;t show up under the sidebars in Widgets admin screen.

The search and replace should only have changed any url’s in them, not affected the widgets themselves (since the Posts Query Ex widgets came across).

I’m thinking the Text Ex widgets must be referenced from elsewhere in WordPress and the that linkage is no longer valid somehow. Not sure why tho.

Update: it appears the missing widgets are all Text Ex widgets.

A whole stack of Posts Query Ex widgets came across fine.

Weird.

OK email addy to distribution list it is.

Thx

Thanks Andrea, my experience confirms everything you said.

I am looking at perhaps a redirection plugin as a last resort. So set the static front page, then have it redirect to the post page.

Cheers and beers.

I should be more clear – the site needs to be just a single post and comments on it, all visible as soon as page loads. No links to anywhere else, just the post + comments.

Hope that clarifies a bit.

I think the issue may be that the client trashed the default “About” page in some way so as to cause and Auto Draft to show up.

The temp fix is to edit the list pages call in the header to exclude the Auto Save page’s id.

Other pages newly created don’t seem to have this problem.

Still a weird one though. Anyone stumbling on this post in future with a clue as to how to clean the db of this “phantom” auto-saved page would be appreciated.

Thanks Andrea.

I did that before posting here.

There’s no “Trash” link up top of the Page edit screen, just “All” and “Published”.

They show all three normal and correct pages, but Auto Save still shows up on the live site.

Weird. Could it be a cache issue?