Previously (up to a few months ago), I have been able to create users with: sudo -s cd /var/discourse ./launcher enter app rails c u = User.create(username: "dunderhead", email: "dunderhead@live.com", password: "password") u.activate Now the activate step fails with: [7] pry(main)> u.activate ActiveRecord::RecordNotSaved: You cannot call create unless the parent is saved from /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/activerecord-7.0.8/lib/active_record /associations/collection_association.rb:342:in `_create_record What do I need to do?

You are failing validation here, that’s why. e.g. the password is too short. You can bubble up the exception doing this: u.save! which gives, e.g.: ActiveRecord::RecordInvalid: Validation failed: Password is too short (minimum is 10 characters) from /home/robert/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/activerecord-7.0.8.1/lib/active_record/validations.rb:80:in `raise_validation_error' A quicker way of getting to that would have been to add an exclamation mark after the create: u = User.create!(username: "dunderhead", email: "dunderhead@live.com", password: "password") An ID will not be assigned until you give the object fully valid attributes, either on create or on save after fixing them. Only when you have an instantiated object can you proceed to run methods on it.

Does the user get a user ID when you create it? I suspect not, but I don’t know why.

[image] Jay Pfaffman: Does the user get a user ID when you create it? No. [4] pry(main)> u = User.create(username: "dunderhead", email: "dunderhead@live.com", password: "password") => #<User:0x00007fb0c48b17e0 id: nil, username: "dunderhead", created_at: nil, updated_at: nil, name: nil, seen_notification_id: 0, last_posted_at: nil, password_hash: nil, salt: nil, active: false, username_lower: nil, last_seen_at: nil, admin: false, last_emailed_at: nil, trust_level: 0, approved: false, approved_by_id: nil, approved_at: nil, previous_visit_at: nil, suspended_at: nil, suspended_till: nil, date_of_birth: nil, views: 0, flag_level: 0, ip_address: nil, moderator: false, title: nil, uploaded_avatar_id: nil, locale: nil, primary_group_id: nil, registration_ip_address: nil, staged: false, first_seen_at: nil, silenced_till: nil, group_locked_trust_level: nil, manual_locked_trust_level: nil, secure_identifier: nil, last_digest_at: nil, flair_group_id: nil, last_seen_reviewable_id: nil, password_algorithm: nil> I did try saving the user before activating, as the error suggested, but to no avail. I don’t know what the error message means by “parent”. [5] pry(main)> u.save => false [6] pry(main)> u.activate ActiveRecord::RecordNotSaved: You cannot call create unless the parent is saved from /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/activerecord-7.0.8/lib/active_record/ associations/collection_association.rb:342:in `_create_record'

New error in ActiveRecord when activating user from rails c

Product Support

markschmucker (Mark S) March 28, 2024, 10:38am 6

Thanks guys, the password was too short. All good now.

Topic		Replies	Views
Created a user from command line. Supposedly active, but isn't? Product Support dev-install , rake-task	1	133	January 31, 2026
Cant create active user via api, Again Product Support	1	575	April 8, 2021
Creating Active Users via the API gem Development rest-api	39	11293	August 5, 2020
API, create user, no longer returns user_id Product Support	8	431	April 17, 2025
Discourse User Created Response Not as expected Development	5	641	August 2, 2019

New error in ActiveRecord when activating user from rails c

Related topics