Skip to main content
Solved

Numbers and bullet points

  • 28 January 2021
  • 8 replies
  • 101 views

Hello. I don’t know if is a bug, but I am not able to add bullet points or numbers on posts. 

 

Are there more people facing the same problem? 

Hi,

sorry to hear you are facing issues with this. I can add them here, I also tried it on your community (without publishing of course) and it works just fine:

 

Or did you encounter this issue after publishing a new topic / reply, or was it in the control environment?

Usually it should just work!?


Hello @Julian 

I can edit the post and add the bullet points and numbers. The problem is after publishing it. 

Once I publish the article or topic, I cannot see the bullet points and numbers. I’m facing this problem and also other members of the community. 

When I go to the control environment and try to edit the post and add the bullet points, even when I update the page, it doesn’t work. 

 


Julian! How are you?

 

I wanna show you what is happing with the "numbers and bullet points issue"

 

I can add numbers in the control environment:
 

But, when I go to the community:
 



 

I don’t what is happing. :( 


I actually just tested this myself on your community. I did not publish it, but I can see it as well in the article preview:

I think the problem is that, just like in the other topic we discussed here, there is something in the custom CSS code you have added (to change the layout in the community) which is removing the lists that you have added.

This is because the lists work fine in the Control Environment, where the custom CSS does not apply. As we have not received any other reports and it is working fine on other communities, it is not likely that there is actually a bug in the editor or somewhere else.

Of course I am not technically advanced enough to verifiy this myself, or to solve the problem for you. But what I can do is I can ask my colleagues from support to have a look at it.

If you know who of your team has added this custom code, maybe you can also ask them to improve this. Changing or improving your own code is not our responsibility, however we are always happy to assist!


I actually just tested this myself on your community. I did not publish it, but I can see it as well in the article preview:

I think the problem is that, just like in the other topic we discussed here, there is something in the custom CSS code you have added (to change the layout in the community) which is removing the lists that you have added.

This is because the lists work fine in the Control Environment, where the custom CSS does not apply. As we have not received any other reports and it is working fine on other communities, it is not likely that there is actually a bug in the editor or somewhere else.

Of course I am not technically advanced enough to verifiy this myself, or to solve the problem for you. But what I can do is I can ask my colleagues from support to have a look at it.

If you know who of your team has added this custom code, maybe you can also ask them to improve this. Changing or improving your own code is not our responsibility, however we are always happy to assist!



It would be great if you could ask the support to help me with this issue. I didn’t change anything in the Custom CSS code, so I am not sure how can I fix it. 
 

Do you think I must send an email to my CSM? 


@Julian Hello! 

I still facing the same problem. Can you please help me with the Custom CSS code?

 

cheers!


@Juliana Spinardi In your Custom CSS you have the following:

ol, ul {
list-style: none;
}
fieldset, ol, ul {
margin: 0;
padding: 0;
}

The first definition says: Don’t show list indicators (numbers or bullet points).

The second definition says: Don’t indent the list-items.

If you remove these two definitions, you should see your lists correctly in the frontend. I’ve tested it with my browser’s developer tools:

On the bottom right you see that I disabled the two custom CSS definitions. And in the content you see that the numbered list now is being displayed as you expect it.


Thanks @bjoern_schulze for your help here in finding what's causing this!

@Juliana Spinardi unfortunately my colleagues were quite busy in the past few days, so we did not get around to find the solution ourselves. If you need help in removing this code from the custom CSS, then we can do that for you. However, this code probably was added for a reason (to change the design in another area of the platform). We might want to test what happens when we remove this code, before we break something else. I could look into moving this code into your staging environment, there we can test without any risks for the end user experience...


Reply