Hi,
I would like to start a new e-commerce website. It is very important to know which VirtueMart version to choose.
If VM2 will come in 2-3 weeks than I will wait. So is there any chance to know if I should wait or go with Joomla 1.5 and VM1.9?
Thanks?
See this message from yesterday:
http://forum.virtuemart.net/index.php?topic=85951.msg291023#msg291023 (http://forum.virtuemart.net/index.php?topic=85951.msg291023#msg291023)
...so I would wait ;)
Ok so seems that Joomla 1.7 will be out in a couple of days.
1) Will VM RC2 work with J1.7?
2) Will we have a possibility to upgrade from RC2 to STABLE when STABLE will be out?
Thanks!
So often already explained, first here http://virtuemart.net/news and then in the forum.
As found on the forum:
1) yes, VM2 is compatible with J1.7
2) yes, VM2RC2 will have the option to get upgraded to VM2STABLE
Is that correct?
Unfortunately I didn't found any answer to the most important question: when will VM2STABLE be ready? One week? One month? Two? Three?
Thanks!
It is done, when it is done :-)
the final will be j1.7 compatible and we expect to release end of August 2011
Quotethe final will be j1.7 compatible and we expect to release end of August 2011
Great, thanks!
Now if I would just receive a short "yes" or "no" to...
Quote2) Will we have a possibility to upgrade from RC2 to STABLE when STABLE will be out?
Thanks in advance!
The answer to your latest question is here: http://forum.virtuemart.net/index.php?topic=85549.msg291021#msg291021 (http://forum.virtuemart.net/index.php?topic=85549.msg291021#msg291021) ;)
Great! Thanks!
I thought it will be release in the end of Aug, it is middle of Sep now.
Quote from: lukelee on September 08, 2011, 06:28:34 AM
I thought it will be release in the end of Aug, it is middle of Sep now.
Me tooooo :-(
J1.7 made it hard for us, sry
dont be sorry, you have done a great job.
So, when do you think the virtuemart 2 stable will be released?Around Sep?
same question here
We wanted to release this week a version, which we call already internally final, lacking some features we promised.
But atm we have 3 majog bugs left we want to solve first. For exampel the synchronising media, display of child products (prices are lacking and not visible in category views).
Thank you for all of your hard work and dilligence.
Once launched, will there be a 1.1.9=>2.0 upgrade option?
There is already a migrator built in vm2. Please test the new version provided here http://forum.virtuemart.net/index.php?topic=85643.0 .
When in this version not new major bugs appear you can consider it as the Final.
where is the list of new features ?
thank you
When should we expect for the stable release of VM2?
is there a link to get it ?
They are working really hard on the stable version. There is no ETA yet, so we need to wait till its done.
When they have an ETA we will see it on the homepage. i am sure about that.
So keep your horses and wait please for these hard working people.
Greets,
The Pin
The Eta is the end of this month.
my client doesn't want to wait any more, I think I have to go back to VM2 version G.
We released today the H version, but you will see in your virtuemart anyway :-)
Is their perhaps a changelog, i see the included 1 is still for V1.5.
How close are we to the final release, G was pretty good once i figured out that yootheme was causing my biggest problem, the last major thing was the products module broke the page when checking out, obviously i can prevent its display, would be nice if i didn't have to though.
THanks for all the great and hard work guys.
Quote from: CranialBlaze on October 07, 2011, 06:56:57 AM
Is their perhaps a changelog, i see the included 1 is still for V1.5.
What do you mean with this?
The update fail for me on Joomla 1.7 with:
XML: Document is empty
XML: Start tag expected, '<' not found
I tried to upload the update manually as an extension - the same thing. So the auto-update doesn't work. The only way I was able to update is by downloading the whole H package and installing that - seems to work ;)
Let me ask the same question, but in a different way.
What would be the downside of beginning development with H right now? IOW, if we start building a store, and a couple features are still buggy but we can live with them or work around them, won't that eventually be corrected by slipstreaming incremental fixes along the way? Or would corrections require completely reinstalling and starting over from scratch?
The point is that for those of us who are under pressure to have a site ready in time for the upcoming Christmas season, we can't wait until November to only then begin updating everything. It would be greatly beneficial to many of us to be able to begin basic configuration, populating items and testing payment gateways sooner, rather than later.
Quote from: Hammerhead on October 07, 2011, 16:42:22 PM
Let me ask the same question, but in a different way.
What would be the downside of beginning development with H right now? IOW, if we start building a store, and a couple features are still buggy but we can live with them or work around them, won't that eventually be corrected by slipstreaming incremental fixes along the way? Or would corrections require completely reinstalling and starting over from scratch?
The point is that for those of us who are under pressure to have a site ready in time for the upcoming Christmas season, we can't wait until November to only then begin updating everything. It would be greatly beneficial to many of us to be able to begin basic configuration, populating items and testing payment gateways sooner, rather than later.
VM does not do incremental updates, i updated from G to H today and spent 2 hours putting the styles back together, would of been much longer but i had the sense to do as many of the modifications as i could in an alternate style sheet. Your database will remain in tack, but any custom styling you implement will be replaced.
Quote from: CranialBlaze on October 07, 2011, 16:47:29 PM
VM does not do incremental updates, i updated from G to H today and spent 2 hours putting the styles back together, would of been much longer but i had the sense to do as many of the modifications as i could in an alternate style sheet. Your database will remain in tack, but any custom styling you implement will be replaced.
Thats why you dont change the "default" files.
Then you can also uncheck include virtuemart css in the backend. Then include the file you want in your template.
I did a J1.7 to 1.7.1 upgrade on a development site, and it wrote over my beez_20 template that I had modified a lot, and hadnt renamed.
Its just a matter of learning what to do.
Quote from: CranialBlaze on October 07, 2011, 16:47:29 PM
VM does not do incremental updates, i updated from G to H today and spent 2 hours putting the styles back together, would of been much longer but i had the sense to do as many of the modifications as i could in an alternate style sheet. Your database will remain in tack, but any custom styling you implement will be replaced.
It was my understanding that the new VM was built using Acyba's update engine. Perhaps I was mistaken.
However, I think you focused on only one aspect. I'm not going to be doing any CUSTOM styles right now.
So, back to the question again
Would there be any downside to installing and configuring H now? If all I am going to do is use default styles, configure payment gateways and populate with various manufacturers, categories and items (which are stored in the DB) would upgrading to the official release 'break' any of that?
Quote from: BanquetTables.pro on October 07, 2011, 17:01:25 PM
Quote from: CranialBlaze on October 07, 2011, 16:47:29 PM
VM does not do incremental updates, i updated from G to H today and spent 2 hours putting the styles back together, would of been much longer but i had the sense to do as many of the modifications as i could in an alternate style sheet. Your database will remain in tack, but any custom styling you implement will be replaced.
Thats why you dont change the "default" files.
Then you can also uncheck include virtuemart css in the backend. Then include the file you want in your template.
I did a J1.7 to 1.7.1 upgrade on a development site, and it wrote over my beez_20 template that I had modified a lot, and hadnt renamed.
Its just a matter of learning what to do.
Currently VM only works with the default template, i also never ever ever use the default Joomla Templates, that's just wrong.
I used my CSS for the styles i needed to change, a lot of VM's stuff is fine where it is so its more work to not use their file especially seeing as that option was not their for G
If you install VM2 RC 1.9.8.H locally on your PC and then connect it to the SVN, you can update it any time you want with the latest fixes or new features.
I have a VM2 shop with 500+ products almost ready to go live. (just didn't enter prices and individual product specifications yet, but that's something I have to do, not the VM2 developers). All basic features are working and I can work around a few minor issues.
In other words, If I had my shop content complete, I could go live immediately. At present I don't do this, because I hate going live with "sorry, but most provided information about my products are still incomplete".
Quote from: Hammerhead on October 07, 2011, 17:05:19 PM
Quote from: CranialBlaze on October 07, 2011, 16:47:29 PM
VM does not do incremental updates, i updated from G to H today and spent 2 hours putting the styles back together, would of been much longer but i had the sense to do as many of the modifications as i could in an alternate style sheet. Your database will remain in tack, but any custom styling you implement will be replaced.
It was my understanding that the new VM was built using Acyba's update engine. Perhaps I was mistaken.
However, I think you focused on only one aspect. I'm not going to be doing any CUSTOM styles right now.
So, back to the question again
Would there be any downside to installing and configuring H now? If all I am going to do is use default styles, configure payment gateways and populate with various manufacturers, categories and items (which are stored in the DB) would upgrading to the official release 'break' any of that?
Akeeba is a backup application, not an update application and their were bugs with VM when using it, nothing more. It has its own updater for itself as well as joomla and a snapshot backup similar to windows system restore but it does not do the updates, even if it did, VM releases a complete build not just the patched files, that they may start doing after its official, but even then any file updated will still be replaced.
Version H is still not truly ready for commercial use, the shipping for 1 still needs to be sorted out, so if you selling physical products you may have some trouble their, their are still bugs in the Products Module.
It depends more on your specific needs, the only way to truly answer that question is for you to download an install a copy onto a test site and confirm that it does everything you need, as i said the database remains in tact so if you do not change a single file and can work around the remaining bugs then you will be fine, provided they do not make any changes in the table.
@CranialBlaze, Thanks for that clarification. It helps.
@JJK, thanks... never used SVN, and not sure if I'm confident doing so at this point. Seems an additional learning curve and time to get up to speed. I'm not a 'developer' by rights, so much as a sole entrepreneur who's looking to Joomla and VM as a solution. So back to the question... would it be safe (assuming no changes to default styles) to begin installation and configuration? Or, is the official release close enough (under 2 weeks) that it would be better to wait?
you should start now, learn it etc.
Its not going to mess up your products when you update. Just keep backups
@CranialBlaze
VM2 has a built in 'Akeeba release managment system' (Live Update). 'Akeeba Backup' is a completely different piece of software.
Quote from: jjk on October 07, 2011, 17:36:38 PM
@CranialBlaze
VM2 has a built in 'Akeeba release managment system' (Live Update). 'Akeeba Backup' is a completely different piece of software.
Ok kool, still overwrote my template file.
Quote from: CranialBlaze on October 07, 2011, 17:51:16 PM
Ok kool, still overwrote my template file.
If you customized the original template, that's your fault. Make a copy of the orginal, rename it, then customize the renamed copy to what you need and use that one instead of the original. - This way updates will never overwrite your customizations. ;)
...also you might keep a backup copy of your configuration file.
Quote from: jjk on October 07, 2011, 18:34:33 PM
Quote from: CranialBlaze on October 07, 2011, 17:51:16 PM
Ok kool, still overwrote my template file.
If you customized the original template, that's your fault. Make a copy of the orginal, rename it, then customize the renamed copy to what you need and use that one instead of the original. - This way updates will never overwrite your customizations. ;)
...also you might keep a backup copy of your configuration file.
Of course I did, point still remains, that's y it took 2 hours and not 2 days like it did first time round.
Sent from my Nexus S using Tapatalk
CranialBlaze sorry to say that, but RTFM.
Read the ***obscenity removed*** manual of joomla and learn template overrides, read here http://forum.virtuemart.net/index.php?topic=90935.0 and there are other links, like pointing to http://dev.virtuemart.net/projects/virtuemart/wiki/Hints_for_the_use_of_the_template_system
I would start with vm2 to learn it now and to bring my shop online next 2-3 weeks.
The installer is also an updater. That means all old files get overwritten and the database get adjusted and that is incremental. You can update a rc2 b version with the H installer and you have the latest version.
Quote from: Milbo on October 07, 2011, 21:20:33 PM
CranialBlaze sorry to say that, but RTFM.
Read the ***obscenity removed*** manual of joomla and learn template overrides, read here http://forum.virtuemart.net/index.php?topic=90935.0 and there are other links, like pointing to http://dev.virtuemart.net/projects/virtuemart/wiki/Hints_for_the_use_of_the_template_system
I would start with vm2 to learn it now and to bring my shop online next 2-3 weeks.
The installer is also an updater. That means all old files get overwritten and the database get adjusted and that is incremental. You can update a rc2 b version with the H installer and you have the latest version.
No a word meaning manure scherlock, I was expecting it to overite my files, pretty much why I made backups and did all my styling outside of the vm stylesheet.
The overwriting of template file started a few posts back explaining it to someone else and now u want to jump in on the arse end of a topic and give ur meaningless 2 cents worth.
Its an effing beta, id be more worried if it not overwrite my files. Hell if it was not for the beta id simply just of replaced the new template files with my edited ones, or better yet, renamed my styled one so that I don't have to worry, but as its its a beta little things like that don't work just yet, or at least it did not in revision G. Even then id ovewrite my files as its not final yet and just by the notes you can see thiers plenty left to still fix/add in
Sent from my Nexus S using Tapatalk
Quote from: CranialBlaze on October 07, 2011, 21:30:32 PM
The overwriting of template file...
Just curious - which template file exactly are you talking about ? (I've updated my VM2 shop many times since the first beta was released and my templates don't get overwritten)
Quote from: jjk on October 07, 2011, 22:07:23 PM
Quote from: CranialBlaze on October 07, 2011, 21:30:32 PM
The overwriting of template file...
Just curious - which template file exactly are you talking about ? (I've updated my VM2 shop many times since the first beta was released and my templates don't get overwritten)
Default.php for the category and details page as well as the virtuemart-ltr.css (could b a lil off on that filename). But I have also completely changed it, as far as moving elements and renaming and adding div's as well as adding classes in to some of the h and p tags, have a very specific design layout that required such serious changes.
As I had an external style sheet most of it was as I left it, just had to go back and reorganize and not break anything after the changes.
Was not planning on making such drastic changes when I started so I had not marked off all my changes.
Sent from my Nexus S using Tapatalk
Sorry, it seems you do not to understand that you just lack a lot knowledge.
This has nothing todo with beta or not, it will never change. It has also nothing todo with virtuemart in special. Just learn how to customize a joomla component. You dont know how to, then read the links I posted to you and learn it. Banquet and jjk already said to you simular. Stop hacking the vm core, this is obsolete and outdated and learn todo it right, thats it.
Sometimes you can only go so far with stylesheeta before you actually need to modify the php itself, once vm2 can actually read something other than default.php, and no I have not actually checked H, ill no longer need to wory about updates replacing my files.
Sent from my Nexus S using Tapatalk
An example:
Concering your 'default.php' for the categories - just go to the directory ...\components\com_virtuemart\views\category\tmpl and make a copy of 'default.php' which you rename for example to 'mycategory.php and place it in the same directory as your 'default.php'. Now you can select 'mycategory' as your standard 'Category Browse Page' in the 'Product Categories' - 'Product Category Form'.
If you customize your 'mycategory.php' it will never become overwritten by a VM2 update again. Very simple, isn't it? ;)
I tried thay in G with the category page when I first started and it did not work. Probably should of tried again with H, was planning on waiting till its finally final again before trying again that way I at least know all the important stuffs their and working.
Rather a little extra work now as the sites 3 months in developement and we need to go live, I'm hoping that vm is working well enough for phase 1, just a shipping issue left and I can safely let it go live and update as team cm does.
Even buggy vm is now and most definitely in the future a far better choice than hika or jshopping
Sent from my Nexus S using Tapatalk
Hi
QuoteEven buggy vm is now and most definitely in the future a far better choice than hika or jshopping
great :)
Spread the word ;)
Quote from: alatak on October 08, 2011, 13:00:36 PM
Hi
QuoteEven buggy vm is now and most definitely in the future a far better choice than hika or jshopping
great :)
Spread the word ;)
Always do, if you guys has takeb much longer I would of had no choice but to use jshopping but for 2 smaller sites one which I already complete I stuck with j1.5 just so I could use vm, the other sire, well leta just say the clients less organized than id normally like, but is kind of advantages this time round.
Sent from my Nexus S using Tapatalk
www wheeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeen