OpenCart Community

It’s taken some time to get here but we are pleased to announce that we are now in official beta stage. You can download the beta versions here

Or you can download the latest version here (be aware that this might not always be stable!):

When is 2.0 going live?
We will be going live with 2.0 within the coming days, following more testing by the OpenCart team and community. One concern with many developers was that they may have hundreds of modules to update/ migrate, to try to mitigate this we will also be maintaining our 1.5.6.x version for about 6 months after 2.0 release. Whilst we will be promoting 2.0, the 1.5.6 version will still be considered a solid alternative and we will do our best to market to general users that there will be many more extensions available for it until 2.0 gains more traction.

Bug or suggestion?
We get lots of users and developers giving feedback about bugs and suggestions - with 2.0 Alpha we had some fantastic support from many people reporting issues and creating pull requests for fixes. Even though we are now in Beta, we know there may still be a few kinks so we still need feedback!

To report a bug please use our Atlassian bug tracker here

If you have a suggestion / improvement please use our User Voice system here

Whats next?
We are already planning 2.1, we can’t say for sure that it will all be included but some ideas so far include:

Remove encryption class (it is not used / required)
Template editor (emails etc) allowing users to change layouts, html, tpl in the wysiwyg
Layout editor (positions) - i.e. drag and drop sort, position etc
Events system for loading templates / models / controllers to give more flexibility
Strip out modules and integrate a module installer system (via an API)
More reports for sales and products and improve the UI
Removal of language variable setting in controllers where possible
Add additional tax and currencies in the default installation
Migrate to a language translation service such as crowdin to allow community based multiple-contributor based service.

We will also be going through the User Voice suggestion site taking note of the top suggestions and looking at what the community feels is missing.

Any documents with OC2.0 Modification?

Without documentation, it is hard to migrate my VQMOD to OC2.0

https://github.com/opencart/opencart/wi ... fications)

https://github.com/opencart/opencart/wi ... ion-System

Is there a demo of the cart? Rather than needing to download and install, just to see whats different.

Also, how much is involved with updating sites from 1.X over to 2.0?

@fullphat - Short of having no extensions or customisation, moving to 2.0 is going to be a lot of work as it has so many differences - hence the major version change. Themes will need to be upgraded, extensions will need to be upgraded etc. That's before you've even considered migrating data over. 2.0 is looking fantastic, but unless you absolutely need to and have a running 1.5.X store, you would probably be better waiting for a 2.1 release where it will be more stable if you must upgrade, as 2.0 is likely to have issues despite the bug testing we've all been doing.

@AllenShea - Note that some of the OCMod features don't work in the same way as the VQMod ones, and VQMod 2.5.0 and above will work in conjunction with OCMod if you want to continue to use it

Install gives two options for dbase
but we use mysql not mysqli
hence the install failes
Notice: Error: Table 'opXXXX_oc20.setting' doesn't exist
Error No: 1146
SELECT * FROM `setting` WHERE `store_id` = '0' ORDER BY `store_id` ASC in /home/opcXXXXXX/domains/XXXXXXXXX-XXXXX.com/public_html/oc20/system/library/db/mysqli.php on line 40

Post it on the atlassian tracker as per the first post. This isn't a bug thread

Is there a release note or list of what's new, or changed in 2.0? Not at a low-level technical level, just a feature overview would be fine.

Can we please have jut one single place were we can report feedbacks, issues, bugs?

Seriously, there are loads of bugs in the current OpenCart 2.0 beta. And now we have:

• the OpenCart forum
• github
• atlassian tracker
• User Voice system

Can you at least check the issues reported on github, too?

JNeuhoff wrote:Can we please have jut one single place were we can report feedbacks, issues, bugs?

Seriously, there are loads of bugs in the current OpenCart 2.0 beta. And now we have:

• the OpenCart forum,
• github,
• atlassian tracker

Can you at least check the issues reported on github, too?

+1 A lot of functions seem missing in admin whether intentional or a bug plus error messages when making changes to various settings, but I'm unsure where to report them.

OK, some feedback:

1) Doesn't always preserve HTML code entered in source mode upon saving
2) Is not XHTML5 compliant, too many tags aren't properly closed, such as instead of . it may be HTML5, but now no 3rd party extension can modify templates using XML parsers

BTW.: what was wrong with the ckeditor? That one worked just fine!

Seriously, there are loads of bugs in the current OpenCart 2.0 beta. And now we have:

the OpenCart forum
github
atlassian tracker
User Voice system

+1 A lot of functions seem missing in admin whether intentional or a bug plus error messages when making changes to various settings, but I'm unsure where to report them.

Can you PLEASE read the original topic, it clearly states where bugs and suggestions should be reported. As Jay mentioned, the forum (including this thread) is not the place to report bugs, you can create issues on GitHub still but that is not preferred as it is not as easy to manage with priorities.

I read the original topic.

If you are serious about bug reports, please make it less confusing, I just spent 5 lost minutes trying to figure out where or how to enter bug reports in the atlassian tracker. I'll put them into github for the time being, until we have a better bug tracker.

JNeuhoff wrote:I read the original topic.

If you are serious about bug reports, please make it less confusing, I just spent 5 lost minutes trying to figure out where or how to enter bug reports in the atlassian tracker. I'll put them into github for the time being, until we have a better bug tracker.

Glad I'm not the only one

If you are serious about bug reports, please make it less confusing, I just spent 5 lost minutes trying to figure out where or how to enter bug reports in the atlassian tracker. I'll put them into github for the time being, until we have a better bug tracker.

Just so everyone else is clear, like GitHub create an account / login and you can then create an issue. I have also updated the intro text on Atlassian so *hopefully* people realise this. I have sent an email to Atlassian asking for a simple button before login to help with usage.

is any docs for OC2 installer?

James wrote: Just so everyone else is clear, like GitHub create an account / login and you can then create an issue. I have also updated the intro text on Atlassian so *hopefully* people realise this. I have sent an email to Atlassian asking for a simple button before login to help with usage.

I created an account, after less than 2 hours it was gone, for not apparent reason. There is no obvious button or link where you can create a new bug entry. This kind of defeats the purpose, this tool is a hindrance to my productivity. Please ask the authors of this software to make the user interface more friendly, and to make sure accounts don't get lost. Bugzilla did a better job in my previous projects.

For the time being, I'll post bugs on github and the OpenCart forum.

What's the theory behind the extension installer? It looks like it's using an FTP connection to do a simple file move/overwrite in the store. This 1) throws errors since a default install has wrong/incomplete information to make the FTP connection, 2) adds a big setup hurdle for the end user and, 3) has many security implications.

we shouldn't be using FTP to upload the files for the installation feature on OC2. It's just like placing plain text password easily accessible to others..

we shouldn't be using FTP to upload the files for the installation feature on OC2. It's just like placing plain text password easily accessible to others..

It not hard to modify the admin/controller/extension/installer.php so that it doesn't use FTP, but rather, place the files directly to the server. And the session can be made secure by using SSL for the admin backend in general, including the installer.