You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that there is a bug leading to papers not beeing added in the database.
Once you have duplicated the database, it is possible to add papers without issues. However if you add a new property (just a new column in the database, no need to populate the property), then papers are no longer added. Deleting the property restores the ability to add papers.
This is a strong limitation. Adding custom properties could allow user to do custom board to track reading for example !
Do you think there is a way to correct this behaviour ?
The text was updated successfully, but these errors were encountered:
Hi, @N0ciple , have you tried this tool successfully?
Thanks for your work on this extension !
I noticed that there is a bug leading to papers not beeing added in the database. Once you have duplicated the database, it is possible to add papers without issues. However if you add a new property (just a new column in the database, no need to populate the property), then papers are no longer added. Deleting the property restores the ability to add papers.
This is a strong limitation. Adding custom properties could allow user to do custom board to track reading for example ! Do you think there is a way to correct this behaviour ?
Thanks for your work on this extension !
I noticed that there is a bug leading to papers not beeing added in the database.
Once you have duplicated the database, it is possible to add papers without issues. However if you add a new property (just a new column in the database, no need to populate the property), then papers are no longer added. Deleting the property restores the ability to add papers.
This is a strong limitation. Adding custom properties could allow user to do custom board to track reading for example !
Do you think there is a way to correct this behaviour ?
The text was updated successfully, but these errors were encountered: