Dreadknux Posted June 6 Posted June 6 I'm currently working on a pretty large-scale archival project and am using Pages and custom wrappers/templates to pull it off. But a big requirement is to be able to have folders with the same name placed in different areas of the folder hierarchy, and bizarrely it seems as if I can't do that? For example, I have a 'games' folder here: /pages/special/v1/games/ And I have just tried to create another 'games' folder here: /pages/special/v2/games/ But the system won't let me. There's no reason for this error to appear unless I'm trying to make two 'games' folders in the same location, but I'm clearly not doing that. Please fix this in V5. Sonya* 1
Sonya* Posted June 6 Posted June 6 7 minutes ago, Dreadknux said: There's no reason for this error to appear There is a reason, actually. The categories can be freely moved inside the database. Pages is not aware about your strict structure. What should happen if you decide move the folder /pages/special/v1/games/ to /pages/special/v2/? There is already a folder with this name...
Dreadknux Posted June 6 Author Posted June 6 (edited) 59 minutes ago, Sonya* said: There is a reason, actually. The categories can be freely moved inside the database. Pages is not aware about your strict structure. What should happen if you decide move the folder /pages/special/v1/games/ to /pages/special/v2/? There is already a folder with this name... It should offer an error and say the folder cannot be moved as there exists a folder with the same name already. I don't believe the Pages app should be working to a 'flat' structure if it's going to offer folder features. Just feels half-baked, and doesn't make any sense. Maybe there should be a setting in the AdminCP that turns that off. Edited June 6 by Dreadknux
Dreadknux Posted October 30 Author Posted October 30 Sorry for being annoying, but I wanted to raise this particular topic again as it'd be great to get some clarity on how this works from IPS' side. At present, my workaround plan is to do the following: /pages/special/v1/games-v1/gamepage1-v1 /pages/special/v2/games-v2/gamepage1-v2 /pages/special/v3/games-v3/gamepage1-v3 /pages/special/v4/games-v4/gamepage1-v4 etc etc. As you can see, it's not exactly elegant in terms of FURL, is unwieldy for admins to name like this, and from an end-user POV it's pretty redundant (they will ask, "why does "games" and "gamepage1" require the "-vX" suffix at the end of it all the time?"). I should be able to organise as follows: /pages/special/v1/games/gamepage1 /pages/special/v2/games/gamepage1 /pages/special/v3/games/gamepage1 /pages/special/v4/games/gamepage1
Marc Posted October 30 Posted October 30 At present, thats simply how the FURL system works, as mentioned above. Of course I understand thats brought up as feedback here, however the changing of these is not something that would be a small job to do.
Dreadknux Posted October 30 Author Posted October 30 That's fair enough. I'll leave it here for consideration then, thanks Marc. I realised that I was slightly incorrect in my last post; this only seems to be an issue when using folders; I can have pages with the same filename in different folders without issue, I just have to make sure the folders are named individually. So: /pages/special/v1/games-v1/gamepage1(.html) /pages/special/v2/games-v2/gamepage1(.html) /pages/special/v3/games-v3/gamepage1(.html) /pages/special/v4/games-v4/gamepage1(.html) Still not super-ideal, but I think I can work with this for the time being. Thanks for the feedback.
Recommended Posts