Magento

The 1-Click install provided by Media Temple seemed to go smooth. But once I attempted to make any changes on the back end I kept getting this error:

SQLSTATE[21000]: Cardinality violation: 1241 Operand should contain 1 column(s)

Any ideas? I’ve uninstalled and reinstalled only to get the same error.

Thanks for catching this issue. We’re looking into it and will post some more info soon.

We looked into this issue and we weren’t able to duplicate it in our test installation. Is there a specific action you’re trying to perform when you receive this error?

I’m trying to create a new Attribute. It looks like it attempts to write it to the db then fails and gives me the above error.

I have the same problem. I am on MediaTemple GS and did the install manually (didn’t see the 1-click option).

When I try to add a product attribute I get the error:

There has been an error processing your request.

SQLSTATE[21000]: Cardinality violation: 1241 Operand should contain 1 column(s)

Not sure if this is a Media Temple SQL specific problem or whether it’s a Magento / Zend Framework issue - I’m guessing a database configuration issue on Media Temple though?!

Thanks for the extra info. We’re working with Varien to get to the bottom on this issue. So far looks like a potential MySQL incompatibility issue but we’re still trying to find the specific query that triggers the error so we can analyze it further.

(mt) df - 01 April 2008 09:34 AM

Thanks for the extra info. We’re working with Varien to get to the bottom on this issue. So far looks like a potential MySQL incompatibility issue but we’re still trying to find the specific query that triggers the error so we can analyze it further.

That’s cool. If it’s any help the address bar shows: report/?id=120707254626&s;=admin

Even in debug mode I can’t get any information and it doesn’t seem to be saving log files.

I also find this error myself when trying to save attributes, please keep us posted

I am getting this error too trying to add attributes.  MediaTemple GridServer 1-click install :(

Hi,

Just testing V1 on Grid Server ‘one click’ - comments to make;

I have a SQL container enabled on this Grid account - however the v1 is sooooo slow it is unusable for a production site. Any one else experiencing this?

Just added my first product - went back to edit it and got:

Fatal error: Allowed memory size of 15728640 bytes exhausted (tried to allocate 1245184 bytes) in /home/7065/domains/inspirednetworking.co.uk/html/lib/Zend/Date.php on line 2554

Hope this helps MT sort out the issues.

Jeremy Timms - 02 April 2008 12:26 AM

Hi,

Just testing V1 on Grid Server ‘one click’ - comments to make;

I have a SQL container enabled on this Grid account - however the v1 is sooooo slow it is unusable for a production site. Any one else experiencing this?

Just added my first product - went back to edit it and got:

Fatal error: Allowed memory size of 15728640 bytes exhausted (tried to allocate 1245184 bytes) in /home/7065/domains/inspirednetworking.co.uk/html/lib/Zend/Date.php on line 2554

Hope this helps MT sort out the issues.

Hey there Jeremy, that fatal error is a PHP error and would suggest that the script is performing quite a heavy task to use over the default 16Mb allocated to PHP tasks. This seems crazy if it is for adding your first product, so let’s hope this isn’t a bigger problem.

Hi Jim,

Yup I know - tis indeed worrying. I just wanted to give it a full test now that V1 is out using the Grid Servers default settings/environment to see if the speed issues had been sorted from the betas.

And then boom - just viewing a created product in the admin section gives the FE. I shouldn’t really have to up the mem size in php.ini at this stage with a bare bones install....

MT should have a look into this - test URL is http://www.inspirednetworking.co.uk

UPDATE - I upped the mem on php.ini and that fixed the admin issue - but still it is dragging its heels massively on MT Grid Servers :(

I’m getting a problem with this as well. I’m trying to install at deltakarting.com/new-shop and after the 1-click installer has done it’s thing, I click on finish, it tries to go to http://deltakarting.com/report?id=120713053021.92&s;=default which gives a 404.

Might be an idea for all one click install users on MT to post their stats on front end and admin load times as well here. Clear browser caches and use Open DNS to get a fairer benchmark. Assume you have a couple of products added only.

Currently (with MySQL container enabled):

Location: UK

Front End Load Time: 14s

Admin sections : Products 12s - System Settings 14s - Edit and save a product - 20s

If we all follow the above format we can give feedback to MT/Varien to optimise this as it seems MT are looking at this thread.

As it currently stands it really cannot be used to run production sites at these speeds on Grid Server accounts. If it has to be on a DV to get decent load times, then lets find that out now.

Our company came to the conclusion that Magento couldn’t be used in cloud hosting environments like MediaTemple’s grid server and Mosso back in beta 0.8, and it appears it still holds true with version 1.0. General speed of the server didn’t seem to be the problem. It seems like it is a database access speed problem. We had similar results with both Mosso and MediaTemple’s grid server.

I hope the problem gets fixed, if possible, because grids/clouds have a lot of things going for them.

In the meantime, we had to go with a (dv) account.

We were going to switch from Avactis Shopping Cart to Magento Shopping Cart because avactis was very slow and programmed terribly.  I’m starting to get worried that despite the really nice look and feature rich lure of Magento maybe it wasnt programmed all that well?

I havent looked into the backend, so I cant tell if its actually handling the data in a bad way, but from what it seems like and what you guys are saying, I would say it’s probably programmed pretty messily.  It’s simply data.  Whether that data is accessed using more queries than expected or other problems, there really isnt an excuse to have pages that load so slowly these days. 

Is there anyone who knows more about the quality of programming that could offer some insight as to whether or not this will 1) slowly get worse as more orders and products are added and 2) if this is something that could be fixed soon with an update?

thanks