Hi,
I just find this little bug.
Look at this print screen : `http://dl.dropbox.com/u/33602932/Capture.jpg`

The red square show the unwanted display. It's only appear on the first page. When i go in the full article the div disapear

You can see it live here : `http://www.latitudes-photos.com/news`

I tested with ZP 1.4.2.2, 1.4.2.3 and the last trunk 2012-04-18.

Regards,
Laurent

Try the nightly build, that is an encoding issue that is fixed there.

Excellent,
I will try that.

Thank you

Laurent

Hi
I upgrade to version 1.4.2.3 [9900] and i have the bug.
I try the zenpage theme and my own theme.

Cdlt
Laurent

The div is automatically inserted if you use tinyZenpage to embed images (see the docs on it). The bug is fixed but the div is now encoded as text thus visible. I fear you will need to either manually delete it or re-embed the image to fix this as it is saved that way in the database.

Ok, i understand now.
I'll try that.

Thanks for the answer

Laurent

Sorry to bother about that, but i have the same behaviour.
I edit my articles, delete this articles in the database.
When i put some picture, the `<div class="zenpage_wrapper">` are print.

Laurent

Edit : I do some other test. If I insert only one picture, the `div` doesn't appear. But if I insert more than one picture the `div` is print.

Please present us with the exact options you select when inserting the picture. We will then try to reproduce the issure.

Ok, thank for your investigation.

Step 1 : I select New/Articles then i select : New article
Step 2 : I select The TinyZenpage Button
Step 3 : I navigate to the desire folder
Step 4 : In what to include --> Image
Step 5 : In image size --> 600px in custom size
Step 6 : In Title and description --> Show Title
Step 7 : In Link type --> No Link
Step 8 : In Text wrap --> No Wrap
Step 9 : I Select the picture in the right.

This work fine for the first image, but i select more than one picture, the Div code is printed.

Hope this help.
Laurent

I have tried to follow exactly your steps above using version 1.4.2.3 [9925] and the Zenpage theme. I even attempted to insert the second picture before the title of the first one. I do not get the DIV to show up.

I run the 1.4.2.3 [9900] I will upgrade to the last soon.
According to you, do you think that it maybe a database problem.
If yes, can you give me some advise for tracking this error ?

Laurent

The data in the database almost certainly is already html encoded. That should not be the case. Of course, if the strings are already wrong in the database changing releases will make no difference. The correction must be to the data.

Ok,

I update to the last build : version 1.4.2.3 [9960].
I have the same behaviour, so i made a new installation with a new database : it's work.
So i decided to copy and paste the content of the news/content field of the "test" database into my "official" database. That don't work but i notice that a backslash as been insert into the code.
Seen capture of my official database here : http://dl.dropbox.com/u/33602932/Capture01.PNG

and my beta database here :

http://dl.dropbox.com/u/33602932/Capture02.PNG

Laurent

PS : both database are in ut8_unicode_ci

I delete the backslash in the database it doesn't change anything. So i delete all the div tag with the html editor in tinymce. It's work.

But when i create a new article, the div tag come back. So i have to delete them again in order to have a correct display ...

I continue to search ...

Laurent

Again the div itself is correct and should appear. It should however not appear in the text as such.

If you get backslashes you probably have magic_quotes enabled on your server. You really should turn that of. Although Zenphoto should work with that we don't really test it as it is an deprecated php function and should really be off.

No,
My magic_quotes are disable.
I do a fresh install with a new database on my serveur, it works like a charm.
The problem is with my actual installation and database.
I have to find where is the mistake because i have plenty of data in my database.

Laurent

Ok, this encoding stuff can be really bugging.