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
April 3-4, 2025
An interactive online event for anyone interested in Backdrop CMS. Everyone is welcome.
Recent topics
Posted 10 hours 12 min ago by (bennybobw) in Weekly Meetings
Posted 16 hours 56 min ago by (Coffee70) in How-To and Troubleshooting
Posted 22 hours 32 min ago by (onyx) in How-To and Troubleshooting
Posted 1 day 10 hours ago by (NumerousHats) in How-To and Troubleshooting
Posted 2 days 12 hours ago by RS Snyder (theflightrs) in How-To and Troubleshooting
Recent comments
Here are some more details about my setup. Yes, I am using a contextual filter. Specifically, I have several content types that have an entity reference field meant to hold references to...
Hide title of a view block if no results?
You can use Rules or the Node Notify module for comments. When a new account is created, I believe there are Rules to send.
Email notifications
There's a few way to accomplish it, but it really depends on your full requirements. I'm working on a contact management module but it won't be released for a few months. There...
Pairing fields
I'm fairly sure that some people have done this successfully in Backdrop. Please can you list the modules you are using; that should help us get the right people to join this conversation.
How to render facet blocks?
Another content type for the addresses is a good option, and there are some more, for instance: Use the Address Field. If you already use Paragraphs (or are open...
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)?