Reply to thread

Message: <blockquote data-quote="joz" data-source="post: 558621" data-attributes="member: 70244">Re: Server console (again <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink    ;)" loading="lazy" data-shortname=";)" />)What I have now is based upon adjacency list model, the one that uses parentid.That works ofcourse however the downside of that structure is that CRUD (Create Read (not that complicated) Update Delete) operations can become over complicated from times.I want to give the user the ability to build up there own menu. So when there's a release it will have default set of items (that work out of the box) but the user can just delete those, move them around, rename them and what not.This can be done with adjacency and already currently is but the left right structure seems more flexible when it comes to this.Moving items around is easier (although more resource intensive) as well as adding items etc.Building up the multi dimensional array within PHP based upon adjacency also tends to get trickier when there are a lot of sublevels.And maybeme if you got some spare time on your hands feel free to contact me, can use all the help there is.---EDIT---thought I might as well drop some kind of changelog here to let you know what I've been working on;- Refactored models now use a nice way of getting settings per model basis (for filenames of sqlite db's for example)- Refactored controller base class to handle mobile requests better- Refactored mobile detection script into a model- Added PHPSysInfo as a plugin- Added highslide jquery plugin to the jquery imageflow plugin that's used for the catalog part (readout of AMC, SGC, movingP, tvseries)- Added MySQL status as a plugin- Added uTorrent statistics as a plugin- Added Orb as a plugin- Added some mobile layouts for a couple of plugins----EDIT2---I guess I'll be sticking with adjacency for now. I can not seem to figure this out and it's not that badly needed, just over optimizing things again <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile    :)" loading="lazy" data-shortname=":)" />----EDIT3---As long as I keep discussing my development issues here with you guys I thought I might as well throw out another one.A lot of the third party web applications I use in my server console require a login to be accessed. This is a good practice and I do not want to disable any of it however requires loging in when accessing certain parts of the console (like ForTheRecord or utorrent for example). Which means for 4TR access thru server console I need to login to the console (or not when I have set remember me cookie) and then login to 4tr. You can guess were I'm going with this, circumventing the second (in this aspect unneccessary but still vital for security cause 4tr URL is still accessible with a direct URL).So what I though of doing now since I have not been successfull with this totally yet (I have some half assed stuff going that works kinda). The scenario:Apache runs on port 80,ForTheRecord runs on 8080When accessing it thru the server console I will be using the server as a proxy to itself (although on a different port)So all requests done for 4TR will go to apache (say on "/4tr/request?org-url=http://fortherecord-original-url-request") which then fires a php script that uses cURL and the get paramater orig-url as the URL to cURL too. Bassically using a proxy call.This way the first request (the login) will generate a cookie on 8080 (which is useless for port 80). That cookie will be send over and over for the proxy requests (from the server) which then will validate because they are on the same domain (read on the same port)What do you guys think? This is gonna take some effort to get to go but if it works will be a solution for other problematic logins as well.</blockquote>

Verification