Juan de la Cruz

how does one uninstall silverstripe fluent? doing composer remove tractorcow/silverstripe-fluent causes:

  1. Fatal error: Uncaught InvalidArgumentException: SilverStripe\CMS\Model\SiteTree references nonexistent TractorCow\Fluent\Extension\FluentSiteTreeExtension in 'extensions' in

i want to clean the database since some pages got broken when a locale was deleted.

nightjarnz

The reason will probably be that the locale query mutation is interfering, the page didn't exist in any locale beforehand, so now looking for history for a locale returns nothing ;)

taoceanz

If I can find out the reason, I'll try write some kind of fix for it and make a PR. Currently though, it's just a surface, "oh look the history isn't there but it's still in the DB", issue.

taoceanz

I'll be investigating the reasons behind, but just want to know whether it's occurred before and is something to do with the task or the project.

nightjarnz

Please open an issue on GitHub @taoceanz - I'm not aware of one, but can see that it could be caused.

taoceanz

@tractorcow Is it a known issue for page history to disappear after a Translatable migration?

taoceanz

If that's correct, before running the Translatable migration task, it's required to specify all fields on each page to be translated for those columns to be created in the _Localised table, else the fields that aren't specified to be translated won't have anywhere for the field translation to be written to so in a way will be lost data?

taoceanz

Ah I see. The one-to-many is what allows translations to be done on a field by field basis? The localisation tables contain only the fields specified to be translated, then when preparing the page for the browser, fields in the current locale are required from the _Localised table, but for all other fields that aren't in that table, they're required from the normal _Live table, assuming page is being prepared for the live stage?