how do you update? please hit the database fixer. Where / Which version you come intial from?

I came from Joomla 3.8 with JCE Pro and SP Page Builder. J3.8 was promoted from J3.7.5

I used the database fixer. Said that db schema was 3.7.4, now after fix it is 3.8.0

I came from Joomla 3.8 with JCE Pro and SP Page Builder. J3.8 was promoted from J3.7.5

Sorry i don't get you.

Did you update from 3.7.5 => 3.8.1 or did you update from 3.7.5 => 3.8.0 => 3.8.1?

And did you use the updated component?

I updated from 3.7.5 to J3.8 when J3.8 was released and updated to 3.8.1 from 3.8 today.

Always use the Joomla Update component ;-)

if i'm not wrong the params field already exists in the table #__fields_groups
in this case the ALTER is not needed
@ManfredHuebner as a quick test
remove this file administrator/components/com_admin/sql/updates/mysql/3.8.0-2017-07-28.sql
the update should go on

@ManfredHuebner Please post also values of this php settings:
memory_limit
max_execution_time

@alikon: Update didn't fail but produced this message. I guess that during several updates over time, one update step failed without proper notice...

@wojsmol:

I had the same problem upgrading from 3.7.5 to 3.8.0 and then to 3.8.1.
ALTER TABLE #__fields_groups ADD COLUMN params TEXT NOT NULL AFTER ordering;

Database link warns about a not matching database shema (still 3.7.5). After hitting 'Fix' is showns the new one without any errors.

Database schema version (in #__schemas): 3.8.0-2017-07-31. Update version (in #__extensions): 3.8.1. Database driver: mysqli. 147 database changes were checked. 184 database changes did not alter table structure and were skipped.

I got the warning message from the file b) 3.8.0-2017-07-31.sql when updating from 3.7.5 to 3.8.1. There is also a) 3.8.0-2017-07-28.sql.
a) adds a paramfield to #__fields_groups. Field is in the table so it probably worked.
b) wants to insert 2 sets of data into #__extensions. One id already exists with other extension. id:318 = empty, id=479: plg_editors-xtd_fields. It looks as if the update added the code for both the module and the plug-in. Any idea how I got plg_editors-xtd_fields inserted to 479? I guess the last id for plug-ins should have bin 478. (I did not add plg_editors-xtd_fields using some "tricks")

A database-update did not show the warning but set the status to ok.
I then used some manual tricks to add the new plug-in to another (free) id. It looks ok now but I'll never use those extensions anyway. I hope no one will update the extension using a hardcoded id.

@schnuti When it's cams to adding new core extensions then free ids are assumed AFAIK For newer versions there is a helper for determining for example id of core extension.

Same issue here. Updater component. 3.7.5 to 3.8 was OK. 3.8 to 3.8.1 gets the "duplicate column name 'params'" error. Running the database fixer seems to resolve schema.

Note that this only happened on one of dozens of sites I ran the same upgrades on.

A number of my clients have reported the issue as well.

-- hugh

@cheesegrits
Did you check the #_extensions table? I guess the problem with the "duplicate column name" did not break the insertion of the two new extensions but if - the database fixer may not have fixed it for you. I did not get any error message when running the fix although the items were not inserted and the column name was already in the db-table. The version-# was still updated.

Same here, nothing new inserted in #__extensions.

My extension_id 479 is (same as you) plg_editors-xtd_fields. I have no 318.

-- hugh

Shouldn't the db-fix program write a log? I understand it's hard to handle all cases as a sql error may be right or wrong depending on the case.. With a log created a professional could asses it manually later.

@cheesegrits
If you know what you are doing, you can do the following. (I guess you do know ;) )

Run the discover extension method. Extensions -> Manage -> Discover: run Discover.
If now any extension is listed the code is there but the #__extensions entry is missing. A new plug-in and a new module from Joomla might appear. This would happen anyway, next time you run Discover.
You can do one of following 3.

1. keep them in the Discover list for ever.
2. Easy fix: Run Install from the Discover view. Disadvantage - the extensions get id numbers in the "3d-party range" and not the original ones.
3. What I did with the use of phpMyAdmin (or Co):

• Edit the record id numbers 318 (module) / first free number below 479 (plug-in)
• Edit the field State from -1 to 0 (disabled).
• Now you can find those extensions in the Manage (extension list) as disabled. Enable if you really want to use them.
  Disadvantage: As one id is not original, remember this hack should you in future get a missing id error message.

Please let us know.

@ManfredHuebner This could be related to SP Page Builder. Are you using the latest version?

https://www.joomshaper.com/forums/error-after-updating-from-joomla-to-3-6-5

@franz-wohlkoenig Close due to extension compability??