Hi @dyrer, I've just updated one of my sites from Backdrop 1.29.0 to version 1.29.1, using the built-in update functionality at the page admin/config/system/updates. I was able to update without problems. Can you provide more details about your case?
Thanks, I see! So you're trying the same method as I did. At the moment, I don't have ideas why it should fail on your site. Maybe have a look at the database log (admin/reports/dblog)?
To confirm that it is ok to be deleted, I would look in the config folder for any config files with the string taxonomyextra in.
If you don't find any, then yet it is probably safe to drop...
Posted7 hours 57 min ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:
Today there was finally time to delve into this issue. First I downloaded the field_data_taxonomyextra table into a spreadsheet. There is a column called Bundle, which in my case included,...
Hi Enthusiast - there is work in progress on an improvement to core that I think will help this.
https://github.com/backdrop/backdrop-issues/issues/4127
I don't fully understand it...
Posted23 hours 33 min ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:
As time ran out to discuss this last week, I would like to discuss https://github.com/backdrop/backdrop-issues/issues/6900 (Pre-existing field with reserved entity machine name re-used on entity...
Posted1 day 3 hours ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:
@waldim, come to office hours and I can see what Cursor AI can do in an hour or two finalize this. We did something similar with OpenID connect and it worked great.
Comments
Hi @dyrer, I've just updated one of my sites from Backdrop 1.29.0 to version 1.29.1, using the built-in update functionality at the page
admin/config/system/updates
. I was able to update without problems. Can you provide more details about your case?Hello,
I am trying to update using built-in update, same method as previous updates.
Thanks, I see! So you're trying the same method as I did. At the moment, I don't have ideas why it should fail on your site. Maybe have a look at the database log (
admin/reports/dblog
)?