Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to update blog customization settings. #495

Open
AverytheFurry opened this issue Jul 11, 2021 · 3 comments
Open

Unable to update blog customization settings. #495

AverytheFurry opened this issue Jul 11, 2021 · 3 comments

Comments

@AverytheFurry
Copy link

@AverytheFurry AverytheFurry commented Jul 11, 2021

Describe the bug

I'm unable to update my blog's customization settings.

Steps to reproduce (if necessary)

Steps to reproduce the behavior:

  1. Go to example.com/me/c/blognamehere
  2. Click on Save changes
  3. See error
    image
Jul 11 00:20:32 localhost writefreely[23832]: ERROR: 2021/07/11 00:20:32 database.go:929: Unable to insert monetization_pointer value: near "DUPLICATE": syntax error
Jul 11 00:20:32 localhost writefreely[23832]: ERROR: 2021/07/11 00:20:32 collections.go:1087: Couldn't update collection:

Expected behavior

The settings should be updated, but instead it errors.

Application configuration

  • Single mode or Multi-user mode? Multi user
  • Database? Sqlite
  • Open registration? No
  • Federation enabled? Yes

Version or last commit: 0.13.1

@thebaer thebaer added the bug label Jul 13, 2021
@thebaer
Copy link
Member

@thebaer thebaer commented Jul 13, 2021

Thanks for reporting this! We probably need to update this query to work with SQLite, in addition to MySQL.

@AverytheFurry
Copy link
Author

@AverytheFurry AverytheFurry commented Jul 22, 2021

Thanks for reporting this! We probably need to update this query to work with SQLite, in addition to MySQL.

Don't want to nag or rush but I'm curious when this will be fixed, as it's preventing a lot of functionality. Should I just switch to MySQL? I don't know what the difference is tbh and just did SQLite because it was easier lol.

@thebaer thebaer added this to the 0.13.2 milestone Jul 23, 2021
@thebaer
Copy link
Member

@thebaer thebaer commented Jul 23, 2021

Switching to MySQL would fix it in the short term, if that's easy for you to do! SQLite is definitely easier in many ways, since you don't need to set up / configure / maintain a MySQL database. But I plan to have this fixed within the next few weeks, and then we'll put out a bugfix release.

Of course, we'd also welcome pull requests from anyone who wants to fix this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants