Ju99ernaut / grapesjs-template-manager

Template and page manager for grapesjs

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Index Page Issues

Stage4000 opened this issue · comments

The index page of a project doesnt have any functionality within the page list. For example: If you navigate away from index in the page list you cant navigate back to the index page in the page list, further, you are unable to rename or delete index at any point.

Is this another case of 'this guy is a moron'? or is this a legit bug?

Im not getting any console errors and my back end appears to be functioning correctly as far as I can tell.
Im still troubleshooting this issue but it appears that something isnt reading or setting the index ID. Index Page ID isnt being set on new project creation and causes the builder to not be able to interact with index.

So from troubleshooting yesterday & today it does appear to me that the index page isn't receiving an ID and thus page manager isn't able to call it by ID later. Not sure if that's the correct conclusion but it's the one I have come to.

Can you provide more details of the issues including screenshots were possible? By design the expected behaviour is that you should be able to rename any page including the index page, for pages the only parameter available is the page name, however you can't delete the selected page, so if you only have one page left it means you can't delete it. To edit the page name use the pointer icon on the page. As for navigation I'm not getting the same issue on my end.

Can I send you the link via Discord? I can't do anything with index. And when I export with the code you gave me it returns the css for index as (undefined).css. I checked the save files and the index page didn't have an ID. I've tried generating new projects too and they never get an ID assigned to index.

I am having the same issue is this sorted out ? @Ju99ernaut

There were so many issues last time I tried this, I do believe we fixed this but this page and project manager isn't complete by a long shot.

We didn't manage to fully resolve this, I personally couldn't find how this was an issue with the plugin itself as it seems to work well with the sample API, for remote storage all the plugin does is send GET, POST and DELETE requests and if everything is stored and returned correctly everything should work fine. Unfortunately I can't document how to implement the backend as it is beyond the scope of this plugin.