Yes, I had this issue at the weekend. What I found is that if I exported the XML, then tried to import it into 2.0.5, it was generating all new ID's for my posts, and posts that contained images, the images were being converted to posts. No image, just the title and description.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mr. Dew Sent: 27 November 2006 15:52 To: [email protected] Subject: [wp-testers] Importing of pages in Wordpress XML file notfunctioning right Importing of pages in Wordpress XML file not functioning right. As it imports, new IDs are being generated due to the auto incremental number. Child pages go missing as the parent pages that they refer to are not longer present. You can reproduce this problem by exporting your blog with child pages and delete all pages and reimporting it back. Note that all your child pages are likely to go missing. You might want to back up before you do this. Best regards, Mr. Dew On 11/27/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Send wp-testers mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.automattic.com/mailman/listinfo/wp-testers > or, via email, send a message with subject or body 'help' to > [EMAIL PROTECTED] > > You can reach the person managing the list at > [EMAIL PROTECTED] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of wp-testers digest..." > > > Today's Topics: > > 1. RE: UTF-8 problem (Rimas Abromavi?ius) > 2. Re: UTF-8 problem (Kimmo Suominen) > 3. RE: UTF-8 problem ([EMAIL PROTECTED]) > 4. Dashboard issues (John D Parker) > 5. RE: Dashboard issues (Brian Layman) > 6. RE: Dashboard issues (John D Parker) > 7. Searching a space results in error (Mr. Dew) > 8. RE: Dashboard issues (Skeddy) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 26 Nov 2006 14:09:54 +0200 > From: Rimas Abromavi?ius <[EMAIL PROTECTED]> > Subject: RE: [wp-testers] UTF-8 problem > To: <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="windows-1257" > > The tables were created etirely by WordPress (clean WP2.1alpha3 install). > I'm using MySQL 4.1.13a-nt and now that you noticed, I checked > global DB variables and there's a default "latin1" for "character set > connection" :) > I suppose that causes the problem, as it uses latin1 for connections unless > told to use utf8. > Nevertheless, I think WP should define the 'set names' parameter to whatever > charset is used blog-wide (bloginfo('charset'); 'UTF8' in most cases), as > many of > default mysql installations will be using 'latin1' by default. > > -- > </Chionsas> > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Peter Westwood > Sent: Sunday, November 26, 2006 1:53 PM > To: [email protected] > Subject: Re: [wp-testers] UTF-8 problem > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Rimas Abromavièius wrote: > > Hello, > > > > I'm using WP2.1alpha3 and I'm having problems with some > > specific character display (while writing in Lithuanian, > > particularly character è [U+010D - latin c with caron]). > > The problem lies in WP using latin1 connection for chatting > > with DB. I don't notice this problem with WP2.05 somehow > > and that is quite strange, because it should exhibit the > > exact same behavior, as I don't see any 'set names utf8' there ;) > > > > When I put: > > $this->query('SET NAMES UTF8'); > > in line 57 of wp-includes/wp-db.php, it fixes the problem > > because the DB connection then uses UTF-8 not just for storing, > > but also for transferring the data. I'm not a MySQL nor PHP > > guru, but I suppose this is a bug and should be fixed using > > 'set names' or some other method. > > > > I think this is more likely a mysql configuration issue. > > Are the tables in the database latin1 or utf8? > > westi > - -- > Peter Westwood > http://blog.ftwr.co.uk > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.2 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFFaYA4VPRdzag0AcURAhE8AJ9lYDkeDKEpSLrjYad1F4ttNLzSZwCeMMxg > VIerFHbpoh4eYtDBdKOXF5k= > =lDmy > -----END PGP SIGNATURE----- > _______________________________________________ > wp-testers mailing list > [email protected] > http://lists.automattic.com/mailman/listinfo/wp-testers > > > > ------------------------------ > > Message: 2 > Date: Sun, 26 Nov 2006 21:26:23 +0200 > From: Kimmo Suominen <[EMAIL PROTECTED]> > Subject: Re: [wp-testers] UTF-8 problem > To: [email protected] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=us-ascii > > On Sun, Nov 26, 2006 at 02:09:54PM +0200, Rimas Abromavi?ius wrote: > > Nevertheless, I think WP should define the 'set names' parameter to > > whatever charset is used blog-wide (bloginfo('charset'); 'UTF8' in > > most cases), as many of default mysql installations will be using > > 'latin1' by default. > > I always take care to create the database as UTF-8, so the tables > inherit this when created by WP. > > It would be good if WP used "set names" to match the charset used by > the blog. This way the data would be automatically converted correctly > by MySQL. > > Having apps just rely on the MySQL configuration makes life difficult > when the apps have to disagree on the charset used. > > It would also be great to have a hook in the wpdb class constructor to > run extra queries like "set names". > > Best regards, > + Kimmo > -- > <A HREF="http://kimmo.suominen.com/";>Kimmo Suominen</A> > > > > ------------------------------ > > Message: 3 > Date: Sun, 26 Nov 2006 20:39:42 +0100 > From: <[EMAIL PROTECTED]> > Subject: RE: [wp-testers] UTF-8 problem > To: <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="us-ascii" > > >> Nevertheless, I think WP should define the 'set names' parameter to > >> whatever charset is used blog-wide (bloginfo('charset'); 'UTF8' in > >> most cases), as many of default mysql installations will be using > >> 'latin1' by default. > >I always take care to create the database as UTF-8, so the tables > >inherit this when created by WP. > > > >It would be good if WP used "set names" to match the charset used by > >the blog. This way the data would be automatically converted correctly > >by MySQL. > Unfortunately, the value for the charset used by the blog is stored in the > database. This makes it kind of a chicken<->egg problem. > > >Having apps just rely on the MySQL configuration makes life difficult > >when the apps have to disagree on the charset used. > > > >It would also be great to have a hook in the wpdb class constructor to > >run extra queries like "set names". > There are already a couple of tickets in Trac related to SET NAMES. (3184, > 2942 and 2828) > If (one of) those get(s) "fixed" this issue should be resolved. > > Regards, > Bas Bosman (Nazgul) > > > > ------------------------------ > > Message: 4 > Date: Sun, 26 Nov 2006 14:09:40 -0800 (PST) > From: John D Parker <[EMAIL PROTECTED]> > Subject: [wp-testers] Dashboard issues > To: [email protected] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=iso-8859-1 > > turned out to be operator error. I cleared the rss entries from the wp_options table and all reloaded properly. I seem to remember a century date problem along about time change. I think the dashboard would have been fine in about 30 years... <grin> > > John > > > --------------------------------- > Cheap Talk? Check out Yahoo! Messenger's low PC-to-Phone call rates. > > ------------------------------ > > Message: 5 > Date: Sun, 26 Nov 2006 21:44:18 -0500 > From: "Brian Layman" <[EMAIL PROTECTED]> > Subject: RE: [wp-testers] Dashboard issues > To: <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="us-ascii" > > Thanks for sharing the solution. Who knows when another of us might > have the same problem. Now we know one place to look. And maybe the > next person who asks will get a better response from us... > > > > ------------------------------ > > Message: 6 > Date: Sun, 26 Nov 2006 18:52:00 -0800 (PST) > From: John D Parker <[EMAIL PROTECTED]> > Subject: RE: [wp-testers] Dashboard issues > To: [email protected] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=iso-8859-1 > > Yeah, apparently, magpie which is the rss piece inside of wp caches in the mysql database(forgive me if you already knew this). I seem to remember adjusting the time by some number of minutes around time change. That'll teach me to use ntp. and Later I discovered that several posts were listed as publish later in the year 2030... my rss planet.wordpress.org feed went the same place as my posts... far into the future. Made me feel like a noob... I nuked the rss entries and magpie faithfully wrote new ones dated this year... nifty. > > John > > Brian Layman <[EMAIL PROTECTED]> wrote: Thanks for sharing the solution. Who knows when another of us might > have the same problem. Now we know one place to look. And maybe the > next person who asks will get a better response from us... > > _______________________________________________ > wp-testers mailing list > [email protected] > http://lists.automattic.com/mailman/listinfo/wp-testers > > > > --------------------------------- > Access over 1 million songs - Yahoo! Music Unlimited. > > ------------------------------ > > Message: 7 > Date: Mon, 27 Nov 2006 16:25:59 +0800 > From: "Mr. Dew" <[EMAIL PROTECTED]> > Subject: [wp-testers] Searching a space results in error > To: [email protected] > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Search ' ', a space, results in error in Page Management > (wp-admin/edit-pages.php). I do not have any pages. I am using the Nov > 27 build. > > Page Management > > > WordPress database error: [You have an error in your SQL syntax; check > the manual that corresponds to your MySQL server version for the right > syntax to use near ') AND (post_type = 'page' AND (post_status = > 'publish' OR post_status = 'future' at line 1] > SELECT wp_posts.* FROM wp_posts WHERE 1=1 AND () AND (post_type = > 'page' AND (post_status = 'publish' OR post_status = 'future' OR > post_status = 'draft' OR post_status = 'private')) ORDER BY menu_order > DESC > > No pages yet. > Create New Page » > > Likewise, searching a space ' ' in the Manage post or anywhere in the > blog itself results in a MySQL error. > > > On 11/26/06, [EMAIL PROTECTED] > <[EMAIL PROTECTED]> wrote: > > Send wp-testers mailing list submissions to > > [email protected] > > > > To subscribe or unsubscribe via the World Wide Web, visit > > http://lists.automattic.com/mailman/listinfo/wp-testers > > or, via email, send a message with subject or body 'help' to > > [EMAIL PROTECTED] > > > > You can reach the person managing the list at > > [EMAIL PROTECTED] > > > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of wp-testers digest..." > > > > > > Today's Topics: > > > > 1. UTF-8 problem (Rimas Abromavi?ius) > > 2. Re: UTF-8 problem (Peter Westwood) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Sun, 26 Nov 2006 13:41:34 +0200 > > From: Rimas Abromavi?ius <[EMAIL PROTECTED]> > > Subject: [wp-testers] UTF-8 problem > > To: <[email protected]> > > Message-ID: <[EMAIL PROTECTED]> > > Content-Type: text/plain; charset="windows-1257" > > > > Hello, > > > > I'm using WP2.1alpha3 and I'm having problems with some > > specific character display (while writing in Lithuanian, > > particularly character è [U+010D - latin c with caron]). > > The problem lies in WP using latin1 connection for chatting > > with DB. I don't notice this problem with WP2.05 somehow > > and that is quite strange, because it should exhibit the > > exact same behavior, as I don't see any 'set names utf8' there ;) > > > > When I put: > > $this->query('SET NAMES UTF8'); > > in line 57 of wp-includes/wp-db.php, it fixes the problem > > because the DB connection then uses UTF-8 not just for storing, > > but also for transferring the data. I'm not a MySQL nor PHP > > guru, but I suppose this is a bug and should be fixed using > > 'set names' or some other method. > > > > -- > > </Chionsas> > > > > > > > > > > ------------------------------ > > > > Message: 2 > > Date: Sun, 26 Nov 2006 11:53:28 +0000 > > From: Peter Westwood <[EMAIL PROTECTED]> > > Subject: Re: [wp-testers] UTF-8 problem > > To: [email protected] > > Message-ID: <[EMAIL PROTECTED]> > > Content-Type: text/plain; charset=windows-1257 > > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Rimas Abromavièius wrote: > > > Hello, > > > > > > I'm using WP2.1alpha3 and I'm having problems with some > > > specific character display (while writing in Lithuanian, > > > particularly character è [U+010D - latin c with caron]). > > > The problem lies in WP using latin1 connection for chatting > > > with DB. I don't notice this problem with WP2.05 somehow > > > and that is quite strange, because it should exhibit the > > > exact same behavior, as I don't see any 'set names utf8' there ;) > > > > > > When I put: > > > $this->query('SET NAMES UTF8'); > > > in line 57 of wp-includes/wp-db.php, it fixes the problem > > > because the DB connection then uses UTF-8 not just for storing, > > > but also for transferring the data. I'm not a MySQL nor PHP > > > guru, but I suppose this is a bug and should be fixed using > > > 'set names' or some other method. > > > > > > > I think this is more likely a mysql configuration issue. > > > > Are the tables in the database latin1 or utf8? > > > > westi > > - -- > > Peter Westwood > > http://blog.ftwr.co.uk > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v1.4.2 (MingW32) > > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > > > iD8DBQFFaYA4VPRdzag0AcURAhE8AJ9lYDkeDKEpSLrjYad1F4ttNLzSZwCeMMxg > > VIerFHbpoh4eYtDBdKOXF5k= > > =lDmy > > -----END PGP SIGNATURE----- > > > > > > ------------------------------ > > > > _______________________________________________ > > wp-testers mailing list > > [email protected] > > http://lists.automattic.com/mailman/listinfo/wp-testers > > > > > > End of wp-testers Digest, Vol 21, Issue 27 > > ****************************************** > > > > > -- > > > > > This e-mail is provided "AS IS" with no warranties, and confers no rights. > > > ------------------------------ > > Message: 8 > Date: Mon, 27 Nov 2006 08:40:39 -0000 > From: "Skeddy" <[EMAIL PROTECTED]> > Subject: RE: [wp-testers] Dashboard issues > To: <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="us-ascii" > > Is this the solution to the problem I'm having? Currently getting the > following message 3 times when I log into my dashboard: > > Fatal error: Cannot redeclare class magpierss in > /homepages/14/d174375701/htdocs/wp/wp-includes/rss.php on line 14 > > I get it once in the box on the right with my comments and spam etc etc, > then twice below. > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of John D Parker > Sent: 27 November 2006 02:52 > To: [email protected] > Subject: RE: [wp-testers] Dashboard issues > > Yeah, apparently, magpie which is the rss piece inside of wp caches in the > mysql database(forgive me if you already knew this). I seem to remember > adjusting the time by some number of minutes around time change. That'll > teach me to use ntp. and Later I discovered that several posts were listed > as publish later in the year 2030... my rss planet.wordpress.org feed went > the same place as my posts... far into the future. Made me feel like a > noob... I nuked the rss entries and magpie faithfully wrote new ones dated > this year... nifty. > > John > > Brian Layman <[EMAIL PROTECTED]> wrote: Thanks for sharing the solution. > Who knows when another of us might > have the same problem. Now we know one place to look. And maybe the > next person who asks will get a better response from us... > > _______________________________________________ > wp-testers mailing list > [email protected] > http://lists.automattic.com/mailman/listinfo/wp-testers > > > > --------------------------------- > Access over 1 million songs - Yahoo! Music Unlimited. > _______________________________________________ > wp-testers mailing list > [email protected] > http://lists.automattic.com/mailman/listinfo/wp-testers > > > > > ------------------------------ > > _______________________________________________ > wp-testers mailing list > [email protected] > http://lists.automattic.com/mailman/listinfo/wp-testers > > > End of wp-testers Digest, Vol 21, Issue 28 > ****************************************** > -- This e-mail is provided "AS IS" with no warranties, and confers no rights. _______________________________________________ wp-testers mailing list [email protected] http://lists.automattic.com/mailman/listinfo/wp-testers _______________________________________________ wp-testers mailing list [email protected] http://lists.automattic.com/mailman/listinfo/wp-testers
