The following warnings occurred:
Warning [2] Undefined variable $unreadreports - Line: 26 - File: global.php(961) : eval()'d code PHP 8.2.25 (Linux)
File Line Function
/global.php(961) : eval()'d code 26 errorHandler->error
/global.php 961 eval
/showthread.php 28 require_once





× This forum is read only. As of July 23, 2019, the UserSpice forums have been closed. To receive support, please join our Discord by clicking here. Thank you!

  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Project structure / design
#2
Hmmm. I'm trying to think through that. I tend to think you're right on the first idea. Put all those things as subfolders.

One of the things to remember is that userspice is really tolerant of how you organize your stuff, as long as it knows where to look. As long as that z_us_root.php file is in the root of your userspice folder, it can get to everything else via a relative path from there.

It also doesn't really make much of a difference if you use the userspice headers etc as long as the path to the init.php /helpers file is correct and you add that line that says

Code:
<?php if (!securePage($_SERVER['PHP_SELF'])){die();} ?>

Beyond that, userspice is really pretty good about keeping it all sorted out. Since 4.1 it stores the paths of the files in the database, so that gives you a ton of flexibility.

  Reply


Messages In This Thread
Project structure / design - by Sebastian - 08-25-2016, 04:10 PM
Project structure / design - by mudmin - 08-25-2016, 07:02 PM
Project structure / design - by Sebastian - 08-26-2016, 04:55 AM

Forum Jump:


Users browsing this thread: 2 Guest(s)