How to move from Co7 to Co8

Again, install C8 and no errors but the admin link is there... no tables on DB.

When you install Cobalt the install SQL script is triggered only on first install. If you update then it is not triggered. No matter how many times you install if you deleted your tables those will not be created on update. This is how Joomla install works.

Again, install C8 and no errors but the admin link is there... no tables on DB.

In this table the column language was already there...

Right because you used install script for Cobalt 8. And this script already contain latest structure. You cannot apply update script. Because it is already there. You can apply update script to Cobalt 7 DB.

Thank you ngarasan, the plugin was disabled.

Now everything appears to be fine.

Thanks Sergey it's good to understand how things work :)

I went with option 1. Updated to Joomla! 3.0.2 Stable, updated cobalt from latest version of 7 to 8. It produces error:

500 SQL=ALTER TABLE xyzab_js_res_types ADD COLUMN language char(7) NOT NULL DEFAULT '*', ADD COLUMN user_id INT NOT NULL DEFAULT 0 AFTER form, ADD COLUMN asset_id INT NOT NULL DEFAULT 0 AFTER user_id;

Sounds like there is not a parent column in Cobalt 7 but there is in Cobalt 8 and the sql is not correct.

Please fix and I will try it again.

I restored back to Joomla 2.5.8 with Cobalt 7 and I have no errors. To move forward to Joomla 3.02 do I need to buy "Field - Relation - v. 8.18" to create a parent field? What is a parent field?? Please provide a step by step walk through on how to move forward.

So it looks like you can't update unless you buy a field? So those who dont even need the field will be forced to buy it just because the coding is bad? So for sure Cobalt is a paid component.

I just helped Brad with get it installed with Package 8.40. Using @ngarasan's guide, we had to do much more than his package 8.36 he was using. Took out ALL of the ALTER TABLE directives because the tables were already altered. I'm not sure how or when they were altered. Because he had to do a complete backup (files & db) from before Cobalt 8 was ever installed.

Had to change ALL CREATE TABLE directives to CREATE TABLE IF EXISTS.

We thought he HAD to purchase the multileveselect field because there was an error upon first installing SQL Error: RENAME TABLE #__js_res_field_miltilevelselect TO #__js_res_field_multilevelselect;

After installing the field the error went away until we got down to it again. It happens to be the second to last sql instruction.

Why is the installer not version forked and separate sql files used depending upon the persons situation? Taking hours to fix the files is not a good way to go. Now we realize that Brad didn't HAVE to buy the multilevelselect field but since it was throwing an error, he bought it to make it go away.

Why include this line if you're not sure people have the field or not? Most probably do NOT have it since it's a paid field, let's just be honest. You should have included that in a PHP file that would sniff if they have it and if so, then run the update. Seems like there's some laziness in testing installation/upgrading packages here.

in order to upgrade I thought I had to purchase multi level select to get cobalt 8 to install with out error.

due to this line 1. I have to delete this line:

RENAME TABLE #__js_res_field_miltilevelselect TO #__js_res_field_multilevelselect;

After purchase we found and removed this line in 8.0-2012-06-17.sql so the field is not needed.

Скрытый текст

Why is the installer not version forked and separate sql files used depending upon the persons situation? Taking hours to fix the files is not a good way to go. Now we realize that Brad didn't HAVE to buy the multilevelselect field but since it was throwing an error, he bought it to make it go away.

I can refund it. Please tell me order number.

Unfortunately we had to put fields SQL queries to Cobalt because in Joomla 3.0 they took out support of running SQL files in installation off type "file". And we pack fields like file type installation. I apologise for this confusion.

Why is the installer not version forked and separate sql files used depending upon the persons situation? Taking hours to fix the files is not a good way to go. Now we realize that Brad didn't HAVE to buy the multilevelselect field but since it was throwing an error, he bought it to make it go away.

You should have included that in a PHP file that would sniff if they have it and if so, then run the update. Seems like there's some laziness in testing installation/upgrading packages here.

I do not think there is a laziness. I work at least 12 hours a day and definitely canot call myself lazy person. Like for example today after long trip I came work very early with attempt to fix all reports and complains on this desk to get it in todays update. My next 5-6 hours I'll spend with answering 45 topics that waiting for my attention. Then I'll have to build all installations and upload it to our site so you could kindly download new pack which fixes all your week issues. I'll have to create and post news on the site with list of what is new there so people could easily discover what was fixed and what they can use as new features. Then some people here expect me to add new features to Cobalt. But I have already spend even more than 9 hours not including lunch time. So I stay in the office another 4-6 hours to make rest of Cobalt users happy. :D

Why is the installer not version forked and separate sql files used depending upon the persons situation? Taking hours to fix the files is not a good way to go. Now we realize that Brad didn't HAVE to buy the multilevelselect field but since it was throwing an error, he bought it to make it go away.

You should have included that in a PHP file that would sniff if they have it and if so, then run the update. Seems like there's some laziness in testing installation/upgrading packages here.

Sergey which was very vague

I apologize. I'll try too be more informative and clear with my answers. Please also consider the fact that I am not native English speaker and sometimes I am not clearly understand what people ask me. So I ask to put it to another words. Because if I understand the question, I can give valuable answer.

Why is the installer not version forked and separate sql files used depending upon the persons situation? Taking hours to fix the files is not a good way to go. Now we realize that Brad didn't HAVE to buy the multilevelselect field but since it was throwing an error, he bought it to make it go away.

You should have included that in a PHP file that would sniff if they have it and if so, then run the update. Seems like there's some laziness in testing installation/upgrading packages here.

Sergey which was very vague

problem and offer help to those that are spending money on your component?

No one here separate people on paid and non-paid. Everyone gets best support we can offer. I understand, and again please accept our apologise for our level of service is quite lower than your service standards.

@Buddy Quaid

Users/Admins here in this forum come from all over the world and not everyones native language is english. Sometimes miscommunication can happen.

Out of my personal experience, you can get an answer within 24h and Sergey and his team are going out of their way, trying to fix problems on the individual installations (including the free Cobalt version) without any charge.

> he ignored those two questions entirely. So to be clear, he asked for clarification

I know that Sergey was travelling the last 2 days and only available for quite some short period of time. Anyway, based on @bradnewman6 comment

**> he ignored those two questions entirely. So to be clear, he asked for clarification

Please fix and I will try it again. **

he wanted to wait for updates. In fact, over the last 3 weeks several improvements were done on the sql script. I check this with every release to see what happend. And again, Cobalt 8 is still in BETA stage ... meaning there will be still issues to fix. So better wait for the STABLE release, if you want a smooth upgrade or try now, but be aware that you might have to fix some issues on the way.

**> he ignored those two questions entirely. So to be clear, he asked for clarification

Please fix and I will try it again.

Also, you guys are on this thread in your own forum, so why didn't you see ngarasan's post of him getting the same error and having to install the multiselect field and post afterwards that it is not needed? **

First of all, I'm just a customer like yourself, not connected in any way to MintJoomla and also not a support person. I participated in this thread (and others about moving from C7 to C8), since i moved from C7 to C8 as well (but with Method 2). Therefore i could share some experiences with @ngarasan.

he ignored those two questions entirely. So to be clear, he asked for clarification

Please fix and I will try it again.

Also, you guys are on this thread in your own forum, so why didn't you see ngarasan's post of him getting the same error and having to install the multiselect field and post afterwards that it is not needed?

How far are we expected to go to ask you the "perfect question" and you not just step in when you see a problem and offer help to those that are spending money on your component?

I think you are painting a wrong picture here. No one expects the perfect question and when you research on the forum, you will see that all questions will be answered, regardless if the person paid for the extension or not. In fact you will find quite some testimonials within the threads were users were extremely pleased and happy with the service given to them.

I personally received a lot of support (since Resources) and bought an additional component (Mighty Touch) without even using it, just as an appreciation of the help and support which was given to me for free.

Just writing this, since you addressed me in your posting, but it might not reflect MintJoomla's opinion. :)

Thanks Sergey and Sackgesicht for your responses. Sackgesicht, it sounded like you worked for MintJoomla, so I'm sorry if I directed what you "should have done" comments your way.

Sergey, you gave great answers and I do understand you work hard and also probably have a life beyond MintJoomla, or at least I hope you do. I understand English is not your first language. However I do have to say that Brad's question of did he have to buy a field to get C8 installed or what a parent field even is was never answered. But the good news is, is that we spent a couple of hours going through the sql and repackaging to test installation about 20 times in order to get it to work. So, the great news is that it works! It's installed and working for him.

I have no doubt that this is a great component and will only get better with future releases. I use it myself as a test to see what its like on one site.

Sorry if I sounded rude to you guys. I'm not trying to be rude to you, I know everyone in the forums wants the same thing, and that is a sound component. One thing I did not know, was that this was a BETA version.

You are more then welcome here Buddy. Please do not hesitate to post topics and ask question. :) We need people with critical mind :)

After successful update I got several errors in the backed. Relating to $params tmpl. I was able to resolve them all by going to Components > Cobalt 8 > Sections > "your sections name" > General Parameters and under templates clicking the gear to open the settings box and saving and closing. See screen shot below.

Also no selection was made under record list. So I needed to select one.

f) Replace all #__ to your DB prefix and apply this script to your DB

Please help, what is "apply this cript to your DB". How can I do this? ppmyadmin? some command or what?

You have to take queries in file

administrator/components/com_cobalt/sql/updates/8.0-xxxx-xx-xx.sql