Nice, thanks Dan. On Thursday, 14 May 2020 20:14:09 UTC+2, Dan wrote: > > Note Jan, to keep your site.config folder in pages/site just put this line > in your index.php script before calling the engine. > > $sitePages = 'pages/site'; > > I realized the solution to putting future site pages in a subfolder > without breaking existing sites is to simply add that line to the index.php > page via the start.php script. > > Cheers, > Dan > > On Thu, May 14, 2020 at 11:19 AM TMurNGon <[email protected] <javascript:>> > wrote: > >> Hi Dan, >> >> From my side I'm fine with all of the above. The pages/site suggestion >> will be good for me as I already use the facility to create/use sub folders >> for various page types (site.pages as well) and site.config currently has >> to break my categorisation rules by being in the pages folder in order for >> Boltwire to function... so all good there. >> >> Looking forward to v7. >> Cheers, >> Jan >> >> >> >> On Wednesday, 13 May 2020 16:25:51 UTC+2, Dan wrote: >>> >>> Hi all, >>> >>> One of my goals with BoltWire 7 is to streamline the core engine of all >>> unnecessary features to enhance performance. But admittedly, I'm basing >>> this on my own personal usage. So I want to list what I'm thinking of >>> stripping out and how I intend to keep these options accessible for those >>> who want them, and solicit feedback before hacking the code... >>> >>> Features Being Removed: >>> >>> Stopwatch: I'll keep the function but delete all the places it's tagged >>> in the code. Pretty much only a developer would use this, and if you are >>> working with the code already it's super easy to put those tags where you >>> want manually. >>> >>> Blacklisting/Whitelisting: I'll put this up as a plugin. >>> >>> Import Requests: BoltWire can be use to feed content to other sites via >>> curl requests. This could also easily be done via plugin. >>> >>> Ajax: I recently added an undocumented feature which allows dynamic >>> updating of sites. I think this might be better done as a plugin too. >>> >>> Buffer Output: This is a feature that allows BoltWire to release the >>> browser and then run background php processes. I'm not sure I ever got it >>> quite to work anyway, and I find myself just using a real cron job for >>> these kinds of things. >>> >>> Settings Being Changed: >>> >>> Site Pages: I want to put these in pages/site folder rather than just >>> pages. This will require manually moving your pages or adding a line to >>> your index.php folder. If this is problematic, there might be some >>> workaround, but it's tricky because of when the site.config folder is >>> processed. One solution might be to add a line to the start.php process... >>> >>> IndexSetup: This creates an automatic indexing of the site but can >>> affect performance. It might be worth keeping turned on by default, but it >>> might be better to leave it off, until a person is ready to get into >>> setting up the indexing system, as getting everything right can be a bit >>> tricky. >>> >>> Account Folder: I'll be setting up a new top level field folder called >>> accounts (or maybe mbase for member database). This will be used in the new >>> account management system. More info on this as I pull this together. >>> >>> BoltWire Variable: The $boltwire variable defining the location of the >>> core engine is currently set in the index.php file when using the start >>> script. And duplicated in the core engine. I'd like to delete that from the >>> core. If you are setting up sites manually, and you don't already have that >>> variable in your index.script, though, that would cause a problem though. >>> Optionally, I could delete from the index.php file start creates, but >>> that's less efficient. Trivial, I know--we're talking nanoseconds. >>> >>> A New Utilities Script: >>> >>> I'm also going to move most of the functions currently in engine.php >>> into a separate utilities script--which will make engine.php a super >>> lightweight script. That means you could easily make a copy of it, call it >>> myengine.php or whatever, tweak however you want, and then call that >>> instead of engine.php in your index script. This would give you the highest >>> level of customization possible. But to make that useful, this script needs >>> to be super lean, lightweight, clean, and well documented. So that's the >>> plan... >>> >>> Admittedly some of this is me thinking out loud. Feedback welcome if you >>> have any input! For most people, unless you use one of the features above, >>> these changes will be seamless. And even if you do, the upgrade path for >>> each should be pretty easy. >>> >>> Input welcome, >>> Dan >>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "BoltWire" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/boltwire/b5913b7b-aa65-49d2-a4ed-47775b76f73e%40googlegroups.com >> >> <https://groups.google.com/d/msgid/boltwire/b5913b7b-aa65-49d2-a4ed-47775b76f73e%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >
-- You received this message because you are subscribed to the Google Groups "BoltWire" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/boltwire/6a7e9373-ab5e-48eb-85d2-e1a9119f98ac%40googlegroups.com.
