Hello,
I am trying to upgrade to latest version and I get this problem
An AJAX HTTP error occurred. HTTP Result Code: 500 Debugging information follows. Path: /batch?id=195&op=do_nojs&op=do StatusText: error ResponseText:
Backdrop LIVE
October 22nd-24th, 2026
An interactive online event for anyone interested in Backdrop CMS. Everyone is welcome.
Weekly office hours
Bring your questions to our weekly virtual office hours, every Wednesday. Everyone is welcome.
Recent topics
Posted 17 hours 19 min ago by (stpaultim) in How-To and Troubleshooting
Posted 1 week 3 days ago by (clarkac) in How-To and Troubleshooting
Posted 1 week 4 days ago by (indigoxela) in Weekly Meetings
Posted 2 weeks 6 days ago by Martin Price | System Horizons Ltd (yorkshirepudding) in Meet-Ups and Events
Posted 3 weeks 4 days ago by (ian) in How-To and Troubleshooting
Recent comments
Did you forget to add a link?
How to track when a field was last updated?
Here is a sample module that does the required task. I'm still working on it and testing it. But, initial tests are good. Still open to finding out that there are already...
How to track when a field was last updated?
Thanks, the /tmp folder was the problem. I moved it elsewhere and then the updated worked. Thanks again!
Update 1.35.1 appears to install but hasn't
Probably not the reason, but worth to do a quick check: Sometimes the update cache interferes, so if something's odd with updates - some module (or core) claims to have updated, but then...
Update 1.35.1 appears to install but hasn't
Nope, not touched any permissions!
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)?