Open argiepiano opened 9 months ago
When bee runs it tells Backdrop that is a CLI operation through the backdrop_is_cli()
function. That may then tell Backdrop to do something different.
Isn't this simply because by default BAM does not drop all tables before doing a restore. So while BAM backup did not preserve a sessions table, the site continued using the existing session table. Since restore also does not drop all tables before a restore (unless configured to do so) the session table remains as do any others through out the site, such as caches etc. So, I'd say this is normal behaviour. Maybe bee is doing override with drop tables before bam restore?
This is a follow up to https://github.com/backdrop-contrib/backup_migrate/issues/115
BAM (by default) doesn't include the
sessions
table in backed up database. When you restore from the UI, the old session table is somehow preserved intact, but restoring from bee wipes out its content. I'm not sure how and why this is happening. It may very well be thatsessions
building is being prevented when running bee.