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
From user:
"With the new docdb I went to the create document page. In the topic section, the top level topics and check boxes appeared immediately. After about 15 seconds the + signs to open the next tier of sub-topics appeared. This delay was very confusing - I spent the whole time wondering how to get to subtopcis. Now that I know about it, it's just irritating. Is there anything that can be done to improve this? For the record I am using Safari on 2 year old Mac running High Sierra. Others running the same configuration have reported the same behaviour."
I tried it and it was also slow for me, took about 9 seconds.
The text was updated successfully, but these errors were encountered:
That’s curious as CMS has a lot more topics than that and I’ve never gotten
a complaint. Loading the page takes about 5 seconds and that’s from Europe.
So I looked at the DocDB and they have a subtopic that has a blank text
string and ID of 0. Do you think this could cause an issue? The source code
for the DocumentAddForm looks like this:
<ul class="3-deep" id="TopicTree">
<li class="liClosed"><label><input type="checkbox" name="topics" value="0" /></label></li>
</ul>
I can't delete it using "administer topics", because it does not show up in that list.
If I ask the DB people to delete that subtopic, would I need to have them delete
other connected records too?
From user:
"With the new docdb I went to the create document page. In the topic section, the top level topics and check boxes appeared immediately. After about 15 seconds the + signs to open the next tier of sub-topics appeared. This delay was very confusing - I spent the whole time wondering how to get to subtopcis. Now that I know about it, it's just irritating. Is there anything that can be done to improve this? For the record I am using Safari on 2 year old Mac running High Sierra. Others running the same configuration have reported the same behaviour."
I tried it and it was also slow for me, took about 9 seconds.
The text was updated successfully, but these errors were encountered: