Problem with web2py-users in web interface
48 views
Skip to first unread message
Anthony
Jul 21, 2015, 3:44:00 PM7/21/15
to web2py-developers
Is anyone else having a problem replying to posts or creating posts in the web interface of web2py-users (also, when viewing a topic, the title of the topic does not appear and the "Loading" message remains on the page)?
When I click "New Question" or try to reply, the JS console says "uncaught exception: Class$S54: duplicate key: dal". Looking at the list of tags, it appears we have both "DAL" and "dal" (both of which have been in use for a long time). Google pushed an update of the web app today, so I'm assuming something in the new code is no longer allowing duplicates like this. I can't find any way to edit or delete one of those tags to prevent the duplicate error.
Anthony
When I click "New Question" or try to reply, the JS console says "uncaught exception: Class$S54: duplicate key: dal". Looking at the list of tags, it appears we have both "DAL" and "dal" (both of which have been in use for a long time). Google pushed an update of the web app today, so I'm assuming something in the new code is no longer allowing duplicates like this. I can't find any way to edit or delete one of those tags to prevent the duplicate error.
Anthony
Niphlod
Jul 21, 2015, 3:56:23 PM7/21/15
to web2py-developers
confirmed, although a few hours ago didn't happen at all.
Anthony
Jul 21, 2015, 4:12:07 PM7/21/15
to web2py-developers, nip...@gmail.com
At some point today, I got the "Application has updated, please reload the page" message, and the problems started after that.
As an aside, I have noticed a lot of open source communities moving to self-hosted Discourse for their discussion forums (e.g., React, Meteor, Elasticsearch, Mozilla). It might be worth considering. Aside from the great feature set and user experience, we would own the data and wouldn't have to worry about Google Groups bugs or a possible future shutdown.
Anthony
As an aside, I have noticed a lot of open source communities moving to self-hosted Discourse for their discussion forums (e.g., React, Meteor, Elasticsearch, Mozilla). It might be worth considering. Aside from the great feature set and user experience, we would own the data and wouldn't have to worry about Google Groups bugs or a possible future shutdown.
Anthony
Reply all
Reply to author
Forward
0 new messages