Magento

Could it have anything to do with the fact that Magento has a feature requirement for MySQL 4.1.20 or newer, and MT is running 4.1.11?

That’s a pretty obvious discrepancy. Why MT has even added it as a 1-Click install is odd considering the System Requirements.

I’m having the same trouble with 1-click install; I can’t add product attributes without getting this error:

I have put in a support request into MT to hopefully allow some digging to find out the root cause of all this.

Will post back answers - they have upped it to the higher echelons of the team.

Same here, I can’t add any attributes using Magento on MT’s grid server either.  Same error.

I suggest that perhaps you all with problems make MT support aware of the issues you have experienced so that MT/Varien are aware of these.

I’ve installed 1.0 with 1-click .. gotten the error.
I uninstalled.
Then manually installed via FTP then the HTTP.. same error.

I don’t think this is a MT problem because the previous beta version was working fine. Had it installed on MT GS and things were running smooth. Added attributes / attribute sets no problem. Didn’t get too far into it as it was a beta.

Does someone have this installed somewhere where this error doesn’t occur?
If so, what SQL version?

justjay202 - 05 April 2008 08:54 AM

Does someone have this installed somewhere where this error doesn’t occur?
If so, what SQL version?

We have everything running fine with MySQL Ver 14.12 Distrib 5.0.45.

I think it is a combined error of Varien/MT rolling it out via one click without a lot more testing first. The system requirements for Magento for instance fall short on the GS. Something is happening here.

I think the question to ask therefore is anyone on MT’s grid servers working without the issues on this thread??????

Anyone???

{MT} would have made a 1-click Install for Magento, because many people signed up to the Grid Service thinking it might be a nice platform to run Magento on. 

Since others have already deviated off the topic at hand (the Attribute error), I feel the urge to add my own 2 cents about cloud hosting… And it’s this - unless a fairly significant gains are made in speeding up Magento or the “grid”, I’m not convinced such environments are up to the task. 

Why?  Here are some timings with Magento v1.0 today on my Grid Service account:

-- Browser: Mozilla Firefox --
Site was loaded early this morning, so no one would have been using the site for hours overnight, thus the cache is completely gone…

* Initial Front-end page load: 62.859 seconds

Please note this was timed by the FasterFox extension, which, I didn’t think of at the time, is on the default of Turbo Charged, which most likely is reducing the page load times… On older builds of Magento, an initial load time of about 74 seconds was common.

* Clicked on “My Cart”: 47.437s

* Clicked on “My Wishlist”: 2.828s

* Clicked on “Magento Demo Store” logo: 4.89s

* Clicked on “My Account”: 8.296s

* Click on “My Cart” (again): 24.594s

-- 2 hours later --
* Not sure what I clicked on, but I believe it was the store logo: 14.470s

--2 hours later--
* Clicked same again: 14.156s

* Clicked on it again, immediately: 2.5s

--2 hours later--
* Clicked again: 18.78s

* Clicked “Advanced Search”: 4.657s

* Started the search for “test”: 7.937s

* Clicked on “Test Product”: 6.2s

-- Switched browser to Internet Explorer --
Loaded front-end initial page: ~17 seconds

So, the key is keeping the system cached.  With so many sites running on the Grid Service, the Magento code is cleared from the cache every couple hours, which makes your website very slow for visitors if you’re site is not yet popular (I’m thinking _many_ of us will fit into this category).

I find some amusement in the thought that I’d need to create a script to visit the primary landing pages (and account pages, etcetera) every hour in order to keep them in the cache…

To be fair, I took advantage of Media Temple’s $89/1st year Grid Service Lite offer, so I only paid about $7.50 a month for the Grid Service.  That said, I’m wondering if it’s even fast enough to be be used as a development site.

Throw in the Attribute error, and I’m thinking of trying a unmanaged VPS instead… I could get a 320MiB (RAM) VPS for $20/month (with a very established company), which is the same as the normal price for the “grid.” It would be interesting to see if that would be faster than the grid (anyone?).  I’ll let you know if I do decide to give it a try.

In summary, many thanks to the Varien team, without them I’d probably still be fussing around with Zencart.
Magento is a good thing.  However, much like trying to run Vista on older hardware, I think we need to be realistic with Magento as well.

Cheers,
...Donovan

Same error here when trying to create attributes (magento on media temple)

We are getting the same error too:

There has been an error processing your request.
SQLSTATE[21000]: Cardinality violation: 1241 Operand should contain 1 column(s)

Is there an ETA on this fix?

Has anyone been able to hack this issue? We are at a stand still and are not able to load products. We could launch, but have no products loaded into the system! =/

Insidedesign - 08 April 2008 07:52 AM

Has anyone been able to hack this issue? We are at a stand still and are not able to load products. We could launch, but have no products loaded into the system! =/

I’m afraid I have had no joy. I’m in the process of moving the site to a new hosting company as time is of the essence.

does anyone know if the magento team or media temple at working on a fix?

Ugh, we couldn’t wait any longer. Moved to MediaLayer.com Problem solved and it is blazing fast!