Sergio Cambra

Probably it could be fixed with this method: ```ruby def pending_any_confirmation super if invitation_token.nil? end ``` In that case users which didn't accept invitation are not allowed to resend confirmation....

confirmations controller check if anything was sent with this method: ```ruby def successfully_sent?(resource) notice = if Devise.paranoid resource.errors.clear :send_paranoid_instructions elsif resource.errors.empty? :send_instructions end if notice set_flash_message! :notice, notice true end...

Does the token hace a question mark in the email? If URL in email doesn't have question mark, it must be your web server who is adding it, I don't...

Then I don't think is related to devise invitable. It must be some web server or reverse proxy which is adding question mark. What would explain why it works in...

Why is redirecting to sign up? What are your routes? Can you see in the log if there is a redirection or loading wrong controller action? If you are accepting...

When user set the password, invitation should be accepted, then user must be allowed to sign in. https://github.com/scambra/devise_invitable/blob/master/lib/devise_invitable/model.rb#L168 Are you overriding block_from_invitation? or clear_reset_password_token methods?

Are other emails working for you?

do other devise mails work? DeviseInvitable does nothing special for sending emails, only adding new mailer method and view, but uses same Mailer class.

Sorry, I'm not sure if I understand your suggestion. Do you want to use devise invitable to call invite! class method only from some custom controllers, or model callbacks, so...

I think another way to do it is defining authenticate_inviter! to raise an exception, redirect or render an error, but if you add that option it could be a cleaner...