Actually, let me change that - it doesn’t look like I get the error on adding attributes anymore. However, I am still having difficulty editing attributes. This edit behavior is the same as pre-patch, which is what led me to believe the patch didn’t work.
When I try to save after an edit, the page perma-loads for around 25 minutes, and then Firefox times out. The only two settings I attempted to change are:
Values Required: No --> Yes
Visible on Catalog Pages on Front-end: No --> Yes
When I save after an edit, could it be trying to update all of my 6,000 SKU’s, hence the timeout? None of the SKU’s make use of the attribute yet, however.
Some more information that may help finding a solution.
I don’t know when it started but in the beginning it was no problem at all to insert/modify attributes. After a while of entering data into the system the well known SQL error occurs when changing an attribute in the admin panel.
Since that the layered navigation in the frontend is also not working correctly anymore. It only shows the categories together with the quantiy, but it does not show any of the other attributes anymore (it worked before for sure!).
Right now even if I open an attribute (e.g. price) and click immediately on the save-button, the error
SQLSTATE[21000]: Cardinality violation: 1241 Operand should contain 1 column(s)
occures.
I tried to export the not-working database and import it to another installation where the attribute thing was working. Just changed the dbname in the local.xml file and tried the same thing as above and - voila - the same error occurs.
Therefore I think that the problem is bound to the database content somehow.
If one of the magento-developers want a dump of the database, feel free to contact me at .