| Re: Creating a PHP 7/8 FUDforum [message #187956 is a reply to message #187955] |
Sat, 19 September 2020 00:03   |
 |
interestinglyaverage
Messages: 5
Registered: July 2020
Karma:
|
Junior Member |
|
|
1. - To test, just check it out from git into the web folder, run `composer install` in that folder to install the dependencies, then edit the GLOBALS.php file with the paths and database settings. If you are using MySQL it should work, if you are using another PDO database it will probably work.
2. - Yes and no. The forum would work, the URLs would be unchanged, all the data would still be there, but the themes would not be compatible so they would either be reset to the default theme or would need to have a new theme ready to install.
3. - So, I did initially have it following the original file structure, but then I realized that that approach is somewhat counter productive. My end goal is to only have a single copy of each pages code that is completely independent of the theme, and multiple theme-specific view files, one per page per theme. This removes everything that shouldn't be directly displayed to the end user from the public folder, and could still be configured to allow for distributable themes - even a theme marketplace like WordPress has. Also, the ability to create child themes is possible. And, you could have different theme systems side by side. Don't like Twig, put in an HTML renderer. Or a JSON renderer and create an Angular or React front end. Just by changing a single dependency.
1. - Probably saying compatible wasn't right - but I want to take advantage of the improvements in 7 and 8, leverage things like stronger typing in the code. So I am targeting 7.3 right now. I can downgrade to 7.2 if that is preferred, but that is two versions out of date.
2. - This is really one of the key changes. The URL structure will be independent of the theme being used. You would be able to change the URL structure regardless of the theme just by changing the request object.
3. - I can incorporate the TranslateWiki files, or even have the translation system be able to use TranslateWiki or .pot files, or whatever is needed, and just change a single setting to load the appropriate translation. But again, the goal would be to switch from having theme-en-us, theme-es, etc. to having a single theme that can translate its content into any language.
It probably won't be able to be merged in git - at least at this early stage I wouldn't, but rather see how the two align after the next stage of the development. I am sure there will be plenty of things to fix as well, places that I may have missed, etc. This is still Alpha 0.0.1. But at least it is progress toward the final idea.
[Updated on: Sat, 19 September 2020 00:04] Report message to a moderator |
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]