search

FluidTYPO3 / fluidcontent

TYPO3 extension Fluidcontent: Fluid Content Element Engine
71 stars 64 forks source link

When upgrading all other Fluid Extensions to the newest official Version FluidContent does not work #430

Open the-hotmann opened 6 years ago

the-hotmann commented 6 years ago

I updated all other Extensions (vhs, flux, fluidpages) to their newest official Version. But when I do this and I want to add content elements in the Backend it does not work. The section with all the contentemelents does not even show up.

I know this Extension is obsoled but how can I work around this?

I also tried to uninstall this extension and edited my providerextension (deleted the dependency on fluidcontent) but even after that I could'nt reactivate my providerextension without FluidContent.

I also tried to update FluidContent to its latest dev version but this also did not work.

EDIT:

figured out how it still works. If I update flux and fluidpages it will break things.

This works:

Typo3 8.7.17 vhs 5.0.1 flux 8.2.1 (9.0.0 available) fluidpages 4.1.0 (4.2.0 available) fluidcontent 5.2.0 (obsoled but how to do it without?)

In general I would like to leave fluidcontent behind (if I dont need it) and maybe the rest will work then? But maybe there is even a problem at flux or fluidpages as if I update them it breaks my backend?

NamelessCoder commented 6 years ago

See https://github.com/FluidTYPO3/flux/issues/1542 for information how to migrate.

the-hotmann commented 6 years ago

Thank you but actually there are NO informations about HOW to migrate _fluid_content to pure flux_ ..

When I disabled fluid_content it totaly fucked up my frontend (and backend)

In my Backend everywhere stood: "WERT IST NICHT ERLAUBT ("fluidcontent_content")" In my frontend stood: "ERROR: Content Element with uid "50" and type "fluidcontent_content" has no rendering definition!"

So how do I migrate my Content Elements to Flux? Is there any tutorial/how to?

Thank you!

the-hotmann commented 6 years ago

What have to be changed to migrate successfully from a installation with fluid_content to pure flux?

NamelessCoder commented 6 years ago

Copy/pasted from the link above:

Pay attention to the CType that results from using Flux or Fluidcontent respectively. Your content types should be possible to insert and if you create a new one, you can read the CType value from the database. Then to migrate, perform SQL queries to update any old records to get the new and correct CType.

This quote deals precisely with migrating previously Fluidcontent-operated elements to Flux by way of changing the CType with SQL queries which is extremely relevant given your error description. So I would disagree and say the link actually does contain migration information.

Determine your old and new CTypes then perform the SQL query to bulk-update all your records. Fix your templates by adding colPos="0-99" to your templates where you make the actual value a single number between zero and 99. Then use the EM upgrade script to migrate your content records and make sure you've selected the proper backend_layout in your pages.

You should also read the change log that is distributed with the package:

And ones before that. The titles give you a hint about what was changed, clicking the link takes you to a complete description of what changes - for example if a ViewHelper argument has become mandatory. The commit messages lists every single piece of information given above.

NamelessCoder commented 6 years ago

PS: reading change logs should be your common practice at the very least when upgrading to a new major version. We use semantic versioning which means a new major version number indicates at least one breaking change that for example requires templates to be changed, uses different DB values, etc. so it is absolutely vital that you are aware of that before you go upgrading. Saves us all some hassle ;)