Hey, the sliding menu isn’t working at all, please see this screen recording for both symptoms and how it was implemented:
Please let me know 
Benjamin
Hi, @ben3!
Thanks for reaching out!
With regards to your issue: as long as the issue is not reproducing on our side, could you please clarify what version of iOS/Safari have you used and please add our support@zeroqode.com account to your collaborator’s list in Settings → Collaboration so we could check the issue inside your application. Plus, please tell us the name of your Bubble application and page name where you develop it, it would be way easier for us to help you solve the issues.
Note: avoid the warning message regarding Professional plan, as we are an agency and you can easily add us to your collaborators.
Regarding the order of the options- yes, it is establishing according to the order in the database. It means if in the database is indicated 1,2,3,4,5 then the options will be like that- 1,2,3,4,5.
About the space - it is possible to add the space between the option through the Element menu Height. But I need to check this feature, it seems there is a bug.
Best, Julia.
Hey Julia,
I have tried it on three different browsers all on the computer. Safari, Chrome, and Firefox. The outcome was the same.
Safari - Version 14
Chrome - Version 87.0.4280.88
Firefox - Version 83
support@zeroqode.com is now a collaborator, the page is “test” on the app “omoffic”.
Regarding the order of operations, I have to enter them into the database in that order, there isn’t was to create a sort order?
The space I am trying to talk about isn’t the space between the options, please see the screenshot. You see the space between the options. I want to have space like that:
Let me know 
Hi, @ben3!
Thanks a lot for the adding us as a collaborator. Now we can dive into the investigation inside your app. As soon as I have the relevant info, I’ll get in touch.
Oh, I am sorry, probably I’ve got you wrong. So, if you have a few options then would be better to write them in the database in the order you’d like to see as a result. In case you have a lot of option, then you are able to sort them with like this :item# 2.
With regards to space, I’m afraid the plugin adds space between the options only. By the way, we have fixed the bug. Please upgrade the plugin to the latest version before testing, refresh your app and give it a try again.
Could you please clarify if you have any extensions set in your browser which can affect the page styles? Thanks.
Best, Julia.
Hey, @ben3!
We have checked your app and it turns out that there is another plugin which is using the “Material Icons” and which affects our plugin. As far as I can see the plugin works. Did you make any changes?
Best, Julia.
I didnt make any changes, what do I do about the other plugin? Are you saying that because I use the google material icons plugin, I am not able to use the sliding menu plugin? Please see this screen share:
Thank you.
It worked for maybe 10 minutes not, then when I went in to add the page names in the order they should be in, it stopped in the middle of that.
Here is the error I get now:
The plugin Sliding Menu / element Side Sliding Menu threw the following error: creationListOfItemeMenu
anonymous
https://dhtiece9044ep.cloudfront.net/package/run_debug_js/580f9eaf347a3e96b9fc9a562a294f86843edbad4041bfac0698e01dff6bec32/xfalse/x9:15:477425 (please report this to the plugin author)
As you can see, not the logo is all wrong in terms of height, also, the highlight no longer works. This is going backward, we’re supposed to be going forward Ahah.
Hi, @ben3!
Apparently, some plugin effects to Siding menu plugin and rewrite the page styles. I’m afraid we cannot influence other plugin and guarantee the computability with other plugins. But there is a workaround that might be helpful in your case.
In the Settings- SEO/Metrics we have added a script that will apply the right style to your image. With yellow is indicated dimensions which can be changed in order to see the required size.
Here is a result:
With regards to the issue: it’s appearing because the third field in the database is NULL (empty). Unfortunately, we couldn’t check this, because we didn’t have permission.
Hope this help!
Best, Julia.