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:
Weekly office hours
Bring your questions to our weekly virtual office hours, every Wednesday. Everyone is welcome.
Recent topics
Posted 3 hours 7 min ago by (nhunt) in How-To and Troubleshooting
Posted 8 hours 21 min ago by (Alex Kunst) in How-To and Troubleshooting
Posted 9 hours 54 min ago by Martin Price | System Horizons Ltd (yorkshirepudding) in Weekly Meetings
Posted 1 day 4 hours ago by (danryan) in Installation Questions
Posted 1 week 13 hours ago by (NormPlum) in Other
Recent comments
Thanks everyone! This was really helpful. Regards, Alex
One-page navigation, how do I add attribute ID's?
Hi Enthusiast, This is probably a very good method, but at the moment a bit too complex for me. I might take you up on your offer to explain further in the future. Thanks! Kind...
One-page navigation, how do I add attribute ID's?
Thank you! I did all as you suggested. I now get the error message: ------------- Requirements problem Warning message The staging configuration directory (./...
Upgrade from Drupal 7 troubleshooting request
I guess the task can be solved using the Entity Reference module. If the main page of the site is built as fields with nodes that are displayed in it by Entity Reference, then each...
One-page navigation, how do I add attribute ID's?
Adding these [paragraphs with ID] to a standard menu might be tricky. @yorkshirepudding – There is a related issue report: github.com/backdrop/backdrop-issues/issues/4063...
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)?