Hi

I also have an error after an update from Seblod 3.8.1 to 3.8.2.

See the picture.

(Sorry, I can't upload/display the picture bigger from media manager of Seblod. I made an external link to my picture.)

Now, all my forms can't save modifications.

Any ideas ?

Thanks

Jean

This is harmless notice that will be fixed in next ersion, set your error reporting in joomla to None, error reporting needs to be disabled on production servers

Hi Klas, 

I disabled error reporting in the Joomla configuration and tried the upgrade again. Got the same message during install. Anyways, the Seblod Component now displays Version 3.8.2. Therefore, I guess it worked. -

Thanks!!

Best,

Bernhard

Hi,

sorry for the confusion, I was answering to JBLwith a different problem.

For your installation problem, try installing 3.7.2 again and upgrade to 3.8.2 afterwards, for some reason installer thinks you are already on 3.7.3 and does not execute that upgrade sql which creates this missing table.

Also, there have been reports of users that had upgrade problems that were solved by first upgrading to 3.8.0 then to 3.8.2, perhaps try that option too.

And as always - BACKUP BEFORE you do any experiments like this. You can find releases here

https://github.com/Octopoos/SEBLOD/releases

Hi Klas,

I tested to reinstall 3.7.2 and get the following error:

Duplicate column name 'path' SQL=ALTER TABLE #__cck_core_folders ADD path VARCHAR( 1024 ) NOT NULL AFTER parent_id;

Seems not to work. There should be a more reliable way, to create missing seblod tables (like the Joomla database repair function). 

For the moment my 3.8.2 setup seems to work without the #__cck_more_jobs table, too. Hope, this won't have any side effects.

Thanks,

Bernhard

What I meant is to install 3.7.2, ignore errors, then install 3.8.0 and then 3.8.2

Hi Klas,

1. ignored errors

2. installed 3.7.2 -> again got error mentioned above

3. installed 3.7.2 once again -> success, no errors

4. installed 3.8.0 -> success, no errors

5. installed 3.8.2 -> success, no errors

6. eneabled error reporting

Everything seems to work all right.

Thanks,

Bernhard