Magento

Just updated to 1.1.3 from 1.1.2 on our recently completed store. We did have to attempt the upgrade 3 times with the downloader (stalled out). After re-attempting everything went smoothly, I hope

Your Estimated shipping rates might return an error: Simple Fix
see here - http://www.magentocommerce.com/boards/viewthread/13178/

Thank you Magento

Still Waiting on the following ::
1) deleting specific orders and have all remnants of that order deleted.
2) ups shipping labels
3) Gift Certificates

I look forwards to all the future advancements of this e-commerce solution.

Thanks Magento.

Tanks Magento

Thanks a lot its great ... but can you guys do anything about the reeeeal speed improvement ?

What is the Extension Key for Magento Connect Manager?

found it ... magento-core/Mage_All_Latest

Thanks Magento for a speedy update.  I’ve been using osCommerce before now and that core hasn’t been updated in years.

Let’s hope the next update brings improvements to the Google Checkout Module.

Thank you all Magento team members! But it`s planned to do anything to improve the Speed of the Magento on a Shared Hosting? Man… I’m using it on Dreamhost and it’s really nice, but really really slow.

Thanks! Good Job!

this may be a request that is out of place, but Is it still a current bug fix requirement to get the email notification system working? Or is this working for everyone else? See my post here: http://www.magentocommerce.com/boards/viewthread/14825/

I can’t imagine this to be a small issue. Any takers?

L

All we need now is for ‘out of stock’ products to be removed automaticly from the front end.

Thanks for the inventory fix.

Update would not work all day.  Finally just worked but broke everything.  It keeps setting the incorrect permissions on index.php.  This is a known problem. 

If you encounter this, ftp or ssh into your site and change the perms on your index.php so it’s not writeable by “group” or 755 I guess it is.  This should fix it.

Nigel

I wonder if there is any compliance issues with the IDARK theme?

I cant update to 1.13 from Magento Connect Manager I dont see any update to install :(

I have 1.1.2 version. What to do to get this update

What’s the modern theme checkout error?
I had no such error with it,or maybe I didn’t notice it(thus lose orders).
Can someone explain so I can verify if i am affected?

@00christian00
http://www.magentocommerce.com/bug-tracking/issue?issue=2556

Thanks Anton,strangely i am not affected.
I had trouble with the modern theme when i first upgraded to 1.1 but it was fixed by upgrading the theme to the latest version.

I have version 1.1.2 and I can’t find the the update to 1.1.3 through the connect manager!

How can I get the upgrade?

Use this extension key : magento-core/Mage_All_Latest

Thanks it worked fine!

But now I have a new problem. Just finished the upgrade when I did “refresh” got a “500 Internal error” - “Apache/2.2.8 (Unix) mod_ssl/2.2.8 OpenSSL/0.9.8b mod_auth_passthrough/2.1 mod_bwlimited/1.4 Server”

Anyone can help?

I also get the 500 error… to restore to v 1.1.2 all I needed to do was rename my backup copy and delete the 1.1.3 version.  I’ll await a response to see what causes the 500 error.  I seem to get that error every time I use downloader to upgrade.  I’m guessing it has to do with a protection issue.... but I’m clueless as to where.

Anyone out there able to help????

Usually, when I get the 500 Internal Error, I turn to the “Mage.php” file and check the Mage.run() line.
I then change it to
Mage.run(’default’)

Maybe you can try this?

I will try that next time… this time I just followed the upgrade process I mentioned elsewhere on the Forums…

all you need to do when you get a 500 internal error after upgrading is resetting your file permissions.

Thanks for the upgrade!

Starting to download Mage_Core_Modules-1.1.3.tgz (1,241,575 bytes)
...done: 1,241,575 bytes
ERROR: failed to mkdir /var/www/localhost/htdocs/magento/404/skin/default/images
ERROR: failed to mkdir /var/www/localhost/htdocs/magento/skin/frontend/default/default/css
ERROR: failed to mkdir /var/www/localhost/htdocs/magento/app/locale/en_US
ERROR: failed to mkdir /var/www/localhost/htdocs/magento/skin/adminhtml/default/default/images/tree_icons
ERROR: failed to mkdir /var/www/localhost/htdocs/magento/pkginfo

The correct path should be /var/www/magento.....

:(

... still no patch or documentation?… this is getting ridiculous! and another theme update? how are we supposed to update custom themes (an impossible dream)? Do we need to update themes? ... man is a little documentation too much to ask? sorry if a 10 line blog post just doesn’t cut it for me…

do appreciate the update though, just frustrated…

have to agree with pixelpusher, updating custom themes is a pain.  I just upgraded a couple days ago to 1.1.2 and have been fighting with my custom theme since then.

maybe it’s time to implement some controls around changes that break themes and add-ons.  Perhaps only whole number releases 2.0, 3.0… may contain changes that could cause breaks?

great product, just a few processes left to work out!

@marcM - We are working on improving backwards compatibility for future updates so that custom themes do not break when upgrading.

Thanks

yoav

I hate how it changes all the email notifications after I personalized them for my store. I loaded my old Magento 1.1.1 version customized email templates over the newer version. But I have no idea if new changes to Magento core files will cause an error, not a good feeling. Also do not feel confident other changes I made are not washed away. They should do something about this.

Also, when Invoicing & Shipping, it would make sense to be able to select a group of orders to ‘create invoice’, and to confirm shipment at once, instead of having to enter into each order. Creating invoice seems like a pointless step to me, it should just be automatically created.
Invoice texts are too small.

When looking at a category page listed with products on the front end. It looks like there is too many buttons. Add to wish list, add to compare, add to cart.... Wish list and compare are not even important features. I feel having larger product images in the category listing pages would directly increase my sales, by making my products look more attractive, and my site more professional. 90% of my products are rectangle images. I don’t like the wasted space, resulting in small image of the actual product. I wish I could add to MY Wish list, having Magento custom the image sizes for product pages.

Maybe there is solutions to these I could do if I was amazing with code and all that. But I am not. And I can’t afford to hire someone to help me with these things, hence choosing the free shopping cart system.

But it is great overall, and I am sure these will all be addressed in the near future.

Thanks

RE: Update Woes…

Your comment chimes in with what I’m working on this very minute. Here’s my theme-only “Minor Upgrade” workflow.

1. Save my clean 1.1.2 upgrade copy of modern theme so I can diff in the future.
2. Once I’ve made all of my customizations save another copy of my modern theme to diff against step 1.
3. Upgrade to modern 1.1.3 and save a fresh copy for future diffs.
4. Diff step 1 and step 2 to update step 3 piece by piece.
5. Save a copy of the result of step 4 so I can diff against step 3 for next week’s 1.1.4 minor update.

Is this really the best way to do this? Is there not a better way? I’d like to know what files are updated so I can know if one that I’ve customized has been overwritten.

A slick update process when a file is about to be part of a minor or major update would include a diff of the file against the old versions default, if uncustomized it is merely updated. If customized however, a time stamped backup of the file is created before the file is replaced with the updated new file and a customized file report is part of the upgrade output to provide an easy checklist of conflicts needing review.

I know the above is not without technical challenges for the magento team but I’m just describing perfect world scenario as an end-user.

lizardo

Don’t work on backward compatibility...DO IT! Maybe you should have thought of this from the beginning?

It updated but then it gives me an error that it couldn’t update the Registry. So now I get 1.1.3 on the site and its still coming up as an Upgrade Available in the Connect. WTF does that mean? Is my system now having issues with a upgrade. I went through all my files and folders and made sure my permissions are correct, my groups and users are correct and still it does this.

I’m not actually sure if it made all the necessary changes.

Heres an error that needs to be fixed with the next update. If I try and remove and exclude a picture that I had been using for a product and replace it with a new one, it still uses the old picture. Even if I go in and delete where it is looking up to, it will create it again. It will show the new picture on the backend as the only one there. And on the front end it will show it as a gallery option but not the base image

Does dumping your Magento caching help? Did you search the forums for this?

S

I deleted the cache in media folder, and it just recreates itself with the incorrect images. Tried all the clear cache features on the backend too.  I can not find anything in the forums for this,

I would suggest looking for a bug report to exist already, if not, file it with the bug reporting system.

Can someone confirm that this looks like an up-to-date installation of stable?

Interface_Adminhtml_Default 1.1.2 (stable)
Interface_Frontend_Default 1.1.2 (stable)
Interface_Frontend_Default_Modern 1.1.2 (stable)
Interface_Install_Default 1.1.1 (stable)
Lib_Google_Checkout 1.1.1 (stable)
Lib_Js_Calendar 1.0.18800 (stable)
Lib_Js_Ext 1.0.18800 (stable)
Lib_Js_Mage 1.1.1 (stable)
Lib_Js_Prototype 1.1.1 (stable)
Lib_LinLibertineFont 1.1.1 (stable)
Lib_Varien 1.1.1 (stable)
Lib_ZF 1.1.1 (stable)
Lib_ZF_Locale 1.1.1 (stable)
Mage_All_Latest 1.1.3 (stable)
Mage_Core_Adminhtml 1.1.3 (stable)
Mage_Core_Modules 1.1.3 (stable)
Mage_Downloader 1.1.1 (stable)

@YoavKutner , what I really like to see is, give us option whether to overwrite files in the two skin folders that are concerning theme/template in the update. Now that Bundle has been out, and after so many upgrades, I think you guys must have stablized the template system no?!

The files in two skin folders really have to be absolutely independent, completely seperate from Mage core files IMHO. The wiki post for the v1.1.1 changes was great and should anything need to be replaced in phtml files in future upgrades, we can follow it without problem.

@Thejosh13,

Heres an error that needs to be fixed with the next update. If I try and remove and exclude a picture that I had been using for a product and replace it with a new one, it still uses the old picture. Even if I go in and delete where it is looking up to, it will create it again. It will show the new picture on the backend as the only one there. And on the front end it will show it as a gallery option but not the base image

Tested this on 1.1.3. Everything works fine. Could you, please, provide more details?

@Frost

I loaded products with images through Import. Later I noticed these pictures need their color adjusted because they look to dull. I loaded up a different picture, and removed the others manually. The new picture shows up on the product page as the thumbnail. The old picture still stays as the small image on category pages, and the main blown up image on product pages. I use web developer to find the path of the image, when I delete it, it will recreate itself, always with the old(wrong) image. I am not sure where it is grabbing it from, I deleted it from the import folder that I used for the initial mass upload. And I am trying to fix this for all my products on the initial upload, not just a few or one. What else can I tell you that would be of use?

Hi Magento Team,

While many of us appreciate some longer term work like “improving backwards compatibility”, if you can release a list of files that are updated in 1.1.3 vs 1.1.2, and the SQL update scripts for 1.1.3 (from 1.1.2, or 1.0), then the community can perform manual upgrade, and not rely on MagentoConnect (which many users have all kinds of issues).

Releasing such files only take one member a few hours, but will be hugely benefit & pacify many angry users.

And you can then take your time to work on the next release.

@thejosh13

check out this thread. it sounds like your problem…
http://www.magentocommerce.com/boards/viewthread/15034/

I second peterbao.  Had asked this myself in the previous release, look like you guys aren’t even consider it

One hour of your work will save us many many grief. 

pleases (begging!!!!)

here here. I third peterbao.

@misterMan

Marking the 1.1.3 notification message as read in your inbox should stop the popup.

@peterbao

Such a list of changed files has always been available from svn repository and is very easily accessible with any svn client

Is anyone else getting errors on onepage checkout with version 1.1.3?

Hi. I keep getting this error when upgrading from the Magento Connect Manager:
Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, webmaster and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

I’m pretty sure it’s not my server in fault, but Magento’s. Any clue on how to solve this? I’ve also tried upgrading from the extension key given before, but same result…

TIA.
Andrés.

Hi Salo,

I am a noob for SVN and only know how to checkout files.  Please kindly teach me how to access it via svn.  I can make the results as a wiki entry.

@salo,

How one uses SVN to check the updated files if the original installation was not downloaded via SVN?
Another thing is, the site is already in the web server, and the webhost doesn’t allow SVN or no such feature I can find.

update to my previous post, SVN is still pointing to v1.1. @Salo, did you get the latest version from SVN?

hello,

i’m really happy that my posted bug related to the costum option products has been fixed

hi, I wish the Magento Team could release a list of file names that have been changed since the last upgrade.

This will really help.
Thank you.

@oxygen:

why you need that ?

When I upgraded it changed my product image permissions, and it also Changed all store view Images so that they selected exclude image for every product image. Now I had to go in to each of my 300 products one by one and remove the exclude check box. Thanks Magento

Big deal...another update of garbage. I refuse to dig through these forums anymore for a solution.  It should be in the installer.  that’s it...when something doesn’t work, usually the next version fixes it, with an installer.  I shouldnb’t have to go trouble shoot this stuff…

Geeez…

Fatal error: Class ‘Mage_Review_Helper_Product’ not found in /home/podgrand/public_html/magento/app/code/core/Mage/Core/Model/App.php on line 779

I ran a clean installation, and restored all customize files, everything seems working perfectly smooth. The product image disappear problem in v1.1.1 and v1.1.2 got fixed. 

Still, it’s very frustrating to have to run a new installation every two weeks and the hours spent that can’t be billed.

I think the Installer via Magento Connect isn’t compatible with many web servers that is the problem why many people ran into problem.

hi thE_iNviNciblE,

I put all my customized files in the local folders. When I upgraded from 1.0.19870.4 to 1.1.1, my customized files are intact.

I am not sure, however, if the old files are compatible with the rest of the new files. I have read from the forums and Issue Reporting that some functions were changed and moved in the new upgrade. So, the safest thing to ensure compatibility is to restore all my customized codes to the new files when I upgrade.

My opinion is, while it is safe to keep your customized files in the local folder without being overwritten, it makes no sense to keep them if the same files from the new version contain bug-fixed, new functions, or enhancement.

By keeping my customized files in the local folders, I am not taking full advantage of the new version, at the same time, running into risks of compatibility issue.

If I were to have a list of the file names that have been changed since the last upgrade, at least I could compare with my own list and restore only those files that have been changed.

This way, I can estimate my time and effort required to do an upgrade.

At this moment, I am not sure if I were to upgrade to 1.1.3, looking at the list of issues reported. I have customized about 20+ files in 1.1.1 and I do not know how many of these 20+ files are affected in the new version. A list of the file names would be very useful.

Perhaps anyone who is more experience in open source development could enlighten me a proper way to do upgrade.

It is a great software and I am happy that I found it for my first online shop. I just hope that the upgrade process in the future isn’t as painful and uncertain as it is.

Thank you.

Hello Oxygen,
You hit everything on the ball.
You are limited in options:
A) Install new, and re-apply all your customizations.
B) Try to discover what changes have occured and update your changes and upgrade hoping for things not to break.
C) use the SVN repository install the new, have the old, compare and contrast and use something like Diff/Meld/WinDiff and toss through the changes.

I have started with .6 and upgraded all along the way. (using a real live site, and a play site without at template).
The non-templated site, default works like a charm with the update Manager, the custom templated one...not so much. Tens/Hundreds of hours have been tossed into keeping up with the updates, its a painful process.

Backwords compatibility will remain an issue until some larger goals are met, speed/functionality/usability. As long as the magento team keeps on altering the database/naming/functions/templates/design/xml, its going to be a fun run through for the custom upgrade process.

hi oxygen,

why you “hacked” the main source ?

Magento is using the great Zend framework -> see @ google.... support for eBAy API , Amazon, and so on…

i’m curious what you had changed

next time you should have a look in the magento wiki…

hi josh_trivera,
Thanks for sharing.
As I said, I wish I could better estimate the time/effort required in each upgrade before I do it. For instance, from 1.1.2 to 1.1.3, and now looking at the long list of reported issues, perhaps I should wait for 1.1.4..

hi thE_iNviNciblE,
I am not a programmer and I don’t know Zend framework. My knowledge in PHP and open source is limited to trial-and-error.

I am keen to learn Magento and everyday I read thru the forums and wiki to understand what problems/issues others are facing.

I tested 1.1.1 and managed to find some bugs (some are in core) which I reported. Finally I solved all of them myself after spending hours tracing the bugs. They are valid issues that have been either already assigned or resolved.

#6315
http://www.magentocommerce.com/bug-tracking/issue?issue=2655

#6281
http://www.magentocommerce.com/bug-tracking/issue?issue=2637

#6280
http://www.magentocommerce.com/bug-tracking/issue?issue=2636

#6065
http://www.magentocommerce.com/bug-tracking/issue?issue=2516

The rest of the customizations are in the frontend and skin. Many were discussed in the forums and I just applied them, for instance the well-known ‘Ship to this address’ radio button, left and right callouts, the once image resize issue, tablerates patch, sitemap sorted in category order, etc.

I used to have lightbox in my previous version but then I decided not to restore it in 1.1.1 as I am not sure if the new versions would affect the files. Afterall, lightbox isn’t a crucial feature. You see my concern?

Of course I also changed the css files. But then I noticed there are changes/additional codes in boxes.css in 1.1.1 and I had to restore my own changes as well.

I started Magento in June and after spending 2 months of exploring, in fact I am ready to open my shop using 1.1.1. Before that, however, I wish to do one more upgrade to 1.1.4, hopefully I don’t have to wait too long.

I just hope that, as I said, the future upgrade is less time-consuming.

Thank you all for sharing.

Hi folks,

I upgraded from 1.1.2 to 1.1.3 but now I can’t log in to System->Magento Connect->Magento Connect Manager; it gives me 404 Not Found. Also, in the footer, it is still vers. 1.1.2

Could you help me, please?

Be kind to your neighbors my friends.  Magento is an Open Source project that everyone is free to download and modify at will.  How many things in life are this freely available?  I’m amazed at how outraged some people get for something they never paid for and were never forced to use.  If you have never been in software development or worked on a very complex project like this, you may not have a clue how difficult this type of work is.  Be patient and thankful for what we have so far from Magento - a damn good start in my opinion!  Instead of complaining try adding something positive to the community.

The update killed my custom theme… I had it under .../defaul/my_theme.  Should I not have it under default package at all?

djackso1 - Lets not be superficial here.
This(Magento) is something people are depending to compete against the real world and take market share. Its not just another open source project, but rather a community driven project that says hey “open source” needs to be taken seriously in the production environment.

To do that, feedback must be given, issues must be address and thats what makes this such a daunting task.

Yes the magento team (michael / moshe / misha / andrey / dmitriy / mitch / sergei / vasily / victor et-al) are doing a wonderful job!

And to have the final product that is desired not just by them, but by the community who invests large time and effort into making their goal a reality needs to be listened to.

If you get a chance see: http://blog.hanfordlemoore.com/2007/04/16/dont-do-what-your-users-say

They do just that! And for that they have earned my respect. Thanks ~!

@oxygen:

OK ...

nice work @finding some bugs AND report them

@josh_trivera - Let’s be real here. Open Source applications (including Magento) are mission critical - CRM, ERP, Linux, Apache, MySQL, etc. Magento is no different. What is also not different is an open source community that feels entitled to complain without contributing much (if anything) to the conversation.

I agree with @djackso1 - be thankful for the work that has been provided to you at zero cost. You don’t like it? That’s fine - move on. Being disrespectful and providing negative energy does nothing to help your cause. This project is great and leaps and bounds from any other solution in the market. If you truly want to see Magento succeed, back it up and contribute.

@marc_j
Lets be real...Some OS applications have become mission critical..
Most aren’t...theres plenty @ sourceforge
Incorporating feedback and using it constructively is the goal to create a usable product.
Thats what we need, usable products. Thats what everyone needs.

In my world of development we have to take the user’s serious or we loose the client.
Feedback for our applications and implementations are key to our success.
This is no different.

While some people pat us on the back and say good job, it doesn’t make for a better product.
But if thats your goal… a better product. Then you need that feedback.
As I stated, a daunting task.

From my personal interaction thus far, the Magento community isn’t a bunch of whiners, rather people trying to utilize a new product and grow it to its potential.

While I do not support people being disrespectful, I do support helping others on the forums and getting those bug reports in!  See you in the forums. ~Josh

When I try to upgrade from 1.1.2 from Magento Connect, I get this error:

Ignoring installed package magento-core/Mage_All_Latest
Nothing to install

When I try to use Magento Connect… i get a blank screen… no errors, no information… :(

Keep copies of your htaccess file! Updates do crash them and you might lose any change you have made, eg to run php5. So all your carefully tuning just smokes away, your updated site crashes and you are crying or scratching your head…

I am trying to upgrade to 1.1.3 from 1.1.1 via Magento Connect Manager.  But I am not getting very far for some reason.

‘Cos I am upgrading just the core, to me it seems everything should be pretty intuitive.

Can someone kindly provide step by step instructions??

Try upgrading 1.1.2 first, then do the 1.1.3

For Some reason I cant update either via connect or ssh using ./pear upgrade-all. It appears to work and says it has worked however the version is still 1.1 for most things. See below.

Interface_Adminhtml_Default 1.1.1 (stable)
Interface_Frontend_Default 1.1.1 (stable)
Interface_Install_Default 1.1.1 (stable)
Lib_Google_Checkout 1.1.1 (stable)
Lib_Js_Calendar 1.0.18800 (stable)
Lib_Js_Ext 1.0.18800 (stable)
Lib_Js_Mage 1.1.1 (stable)
Lib_Js_Prototype 1.1.1 (stable)
Lib_LinLibertineFont 1.1.1 (stable)
Lib_Varien 1.1.1 (stable)
Lib_ZF 1.1.1 (stable)
Lib_ZF_Locale 1.1.1 (stable)
Mage_All_Latest 1.1.2 (stable)
Mage_Core_Adminhtml 1.1.2 (stable)
Mage_Core_Modules 1.1.2 (stable)
Mage_Downloader 1.1.1 (stable)

Anyone have any ideas how I can update ? I have tried deleting the cache in /pearlib/cache and /pearlib/downloads to start from afresh.