Setting the Default Category on Docuss

AndyatFocallocal · 10 August 2021 15:10

@syl I hope you’re enjoying summer

I’m seeing a small bug, i think. The maps are not selecting the default category, and i can’t see where to set it.

Our documentation says the default setting should be in the plugin settings in the admin area, but its not there. Your documentation says it should be here: fl-maps/dcs-website.json at master · focallocal/fl-maps · GitHub

We haven’t defined it here. Probably because we just used the default option of ‘hidden’

Do you have any ideas where i can edit/check it?

AndyatFocallocal · 10 August 2021 15:12

Normal:

When i hit Alt + A:

syl · 18 August 2021 19:30

Hi Andy,

The fl-maps code that sets the category is here:

github.com

focallocal/fl-maps/blob/master/imports/client/ui/app.js#L181

    
      
            comToPlugin.onDiscourseRoutePushed(({ route }) => {
              const topicCategory =
                route.pageName === 'm_about'? 'The About Page Discussion' :
                route.pageName === 'whitepaper'? 'Public Happiness Token' :
                route.pageName === 'wp_why'? 'Public Happiness Token' :
                route.pageName === 'wp_intro'? 'Public Happiness Token' :
                route.pageName === 'wp_faqs'? 'Public Happiness Token' :
                route.pageName === 'm_gather'? 'Hidden' :
                route.pageName === 'summit'? 'The Happier World Economies Summit' :
                'General Discussion'
              comToPlugin.postSetRouteProps({ category: topicCategory })
            })
          
          
}
          
          
export const routeMatcher = new SimpleRouteMatcher({
            maxPageNameLength: websiteJSON.dcsTag.maxPageNameLength,
            forceLowercase: websiteJSON.dcsTag.forceLowercase,
            predefinedPageNames: websiteJSON.pages.map(p => ({
              pageName: p.name,
              pathname: p.url // This works because we know our urls are all relative urls, i.e. pathname = url

Possible issues:

The fl-maps code that computes topicCategory is faulty (for example one or several categories set in lines 173 to 180 don’t exist), or
comToPlugin.postSetRouteProps() has a bug.

Would you please check possible issue #1 first? (also, please tell me of any error message in the console) If everything is fine in your code I will check #2.

Thanks,

AndyatFocallocal · 20 August 2021 13:52

Sorry @syl, i saw this in the middle of the night and forgot to reply. I checked through the linked pages and couldn’t find ‘summit’, the last one, so i commented it out. The others are all there and working well.

The issue isn’t present on the Whitepaper, or the FAQs page. Only the hidden category on the maps.

AndyatFocallocal · 20 August 2021 14:05

I have an idea. Perhaps the issue is that Docuss doesn’t have permission to see or use the hidden category. I’ll see if i can make it publicly accessible to see if that fixes it.

AndyatFocallocal · 20 August 2021 14:09

security settings are normal

AndyatFocallocal · 20 August 2021 14:22

the only difference i can see is that ‘hidden’ is muted.

syl · 20 August 2021 20:41

I can’t seem to reproduce the bug. Would you please tell me how to get to this step (from your post above)? :

AndyatFocallocal · 21 August 2021 01:07

Thanks for replying Syl.

Click near me.
Find anyone on the map, I suggest Vancouver.
Click on that person (or event) and open their page. - Then click one of the three links to engage with them and open Docus.
When it opens the Docuss/Discourse window says users need to set a category before posting a message. For users the category select window is hidden, so it needs to auto fill to ‘Hidden’.

Here’s a direct link to them: Public Happiness

syl · 21 August 2021 13:38

It seems the issue is caused by the missing category “General Discussion”. Would you please check and tell me?

AndyatFocallocal · 21 August 2021 17:12

Ah, that has gone missing

AndyatFocallocal · 21 August 2021 17:12

@syl it’s here: General Chat - Public Happiness

AndyatFocallocal · 21 August 2021 17:55

Oh! You’re right. I changed the name to General Chat. Thanks for solving that, it makes sense now. I’ll add it to our documentation so it never happens again.