Thread

Bit of a weird one: every time a new entry is created a second duplicate entry is created with an incremental id, eg 469 and 470. The weird bit is that this only happens for one weblog, the others weblogs work fine. The dodgy weblog has two custom fields: a textarea and a FF Matrix field. These are ‘Gypsy’ fields (Brandon Kelly), and are used by other weblogs without problem.

My first thought was corrupt db or mysql 4 bug; but why would it affect just this one weblog? Entry data is all stored in the same tables regardless of weblog so it’s perplexing.

The live site is deployed on a server at a large firm and is only for internal use (so no external access), and I only have access to my development version where I am unable to replicate the problem. If I had access to the live site I could step through the whole entry saving process with a debugger, but as I don’t I’m left to guessing.

The live site is running EE 1.6.8 on IIS, PHP 5 and MySQL 4 (sorry don’t know exact versions).

Installed extensions:
Gypsy (v.1.0.6)
HD Newsletters (v.1.0.0)
LG Member Form Customiser (v.1.1.0)
LG Add Sitename (v.1.2.0)
LG Live Look (v.1.0.4)
Publish Tweeks (v.0.8)
jQuery for the Control Panel (v.1.1.1)
MD Live Search (v.1.2.1)
FieldFrame (v.1.3.5)
Low Seg2Cat (v.1.2)
LDAP authentication (v.1.0.0)
NP View Counts (v.1.0)
Category Checkboxes (v.1.1.5)
Edit Menu (v.1.0.2)
LG Image Preview (v.1.0.0)
Simple Tags (v.1.7.3)

Any ideas?

About the only thing we can suggest is see if normal fields act the same way. Especially since you can’t recreate it yourself. Other troubleshooting techniques would be to turn off all extensions and test that way.

We’ve tried this and the JS error still occurs. After a bit of searching I think I have the culprit:
https://support.ellislab.com/bugs/detail/12203/

What I think is happening is the page is getting saved but the js error stops the page from refreshing; user thinks nothing has happened and tries saving again, causing two entries to be created.

I’ve patched cp.publish.php as suggetsed at the end of the bug report linked above and I’ll let you know if it works.

Sounds good, let us know what you find out. We’ll be here.