I get the errors on the dry run.

which is..to my understanding, the system trying to fix the errors and the displaying "sample" results.


Like the system saying "We tried to fix and this is what would happened if you continued".

Do you want to continue?

----

When you say 100 fields, is that before or after the code change?

Just my typical plugins equal almost 76 fields leaving less than 30 for user info on several different plans.

hmmm....

I already undid my changes and will have to redo them again to test the dry run.

The button did say something like
"do a dry run to see the expected results of the fix...."

Which I did,
and mine still spat out red errors.

and yes I believe there was an option to continue the fix, but it was not clear that the RED results of the dry run would be repaired.

I would assume that if the system could fix the errors that this would be reflected or noted in the dry run.

if it could not then it would show red.
(as it did)


Having a dry run system that showed red errors that it would still fix, kinda defeats the purpose of a dry run...?

How would you know if the errors were real or not?

Okay so I tried again and this is what is gives me

a ton of red errors like

B fields data storage Database structure differences:
Table #__comprofiler Column cb_businessname type is text instead of being prefixed by "sql:"
Table #__comprofiler Column cb_streetaddress type is text instead of being prefixed by "sql:"
Table #__comprofiler Column cb_city type is text instead of being prefixed by "sql:"
Table #__comprofiler Column cb_clubcountry type is text instead of being prefixed by "sql:"
Table #__comprofiler Column cb_postalcode type is text instead of being prefixed by "sq


then this at the bottom
The CB fields data storage database structure differences can be fixed (adjusted) by clicking here: Click here to Fix (adjust) all CB fields data storage database differences listed above (you can also Click here to preview fixing (adjusting) queries in a dry-run), but in all cases you need to backup database first as this adjustment is changing the database structure to match the needed structure for the installed version.


after running a dry run
I get this all in red

CB fields data storage Database adjustments errors:
Table #__comprofiler Column cb_businessname type is text instead of being prefixed by "sql:"
CBSQLupgrader::changeColumn of Table #__comprofiler Column cb_businessname failed because the column type text could not be determined (not starting with sql:).
Table #__comprofiler Column cb_streetaddress type is text instead of being prefixed by "sql:"
CBSQLupgrader::changeColumn of Table #__comprofiler Column cb_streetaddress failed because the column type text could not be determined (not starting with sql:).
Table #__comprofiler Column cb_city type is text instead of being prefixed by "sql:"
CBSQLupgrader::changeColumn of Table #__comprofiler Column cb_city failed because the column type text could not be determined (not starting with sql:).
Table #__comprofiler Column cb_clubcountry type is text instead of being prefixed by "sql:"
CBSQLupgrader::changeColumn of Table #__comprofiler Column cb_clubcountry failed because the column type text could not be determined (not starting with sql:).
Table #__comprofiler Column cb_postalcode type is text instead of being prefixed by "sql:"


and this text at the bottom.

Dry-run of CB fields data storage database adjustments done. None of the queries listed in details have been performed.

The database adjustments listed above can be applied by clicking here: Click here to Fix (adjust) all database differences listed above. You need to backup database first as this fixing/adjusting is changing the database structure to match the needed structure for the installed version.


but
nothing here indicates that performing the fix will give me the successful fix.