CRITICAL SECURITY VERSION UPDATE:
https://github.com/daylightstudio/FUEL-CMS/releases/tag/1.4.13
https://github.com/daylightstudio/FUEL-CMS/releases/tag/1.4.13
admin
About
- Username
- admin
- Joined
- Visits
- 8,800
- Last Active
- Roles
- Administrator
Comments
-
Thanks for the report. I've pushed that fix to the develop branch here if you want to merge it in. https://github.com/daylightstudio/FUEL-CMS/commit/6454106579710bf4df20a5fbd1d9a642c495d095
-
There is a "dsn" property on a model that can be set for rare cases when the model's data pulls from a different database. If it's empty, it just uses the default database connection. How are you determining the number of connections in a sleep stat…
-
You can totally do it but you'll need to think of traditional CI controller view and routing. You may need to add your route to your fuel/modules/reports/reports_routes.php file and to get rid of the $nav_selected error, you'll need to just make sur…
-
Actually, you created an "Advanced Module". Advanced modules are a way to sort of "name-space" your code and make it modular by not interfering as much with your fuel/application directory. They can contain "Simple Modules" (e.g. like the Blog and …
-
Try the following instead (feel free to change the value from 'reports' to what you need to appear selected in the admin when in the module): $config['modules']['reports'] = array( //... other configuration 'nav_selected' => 'reports',…
-
It seems likely that it may be due to the default security settings for a module. In the fuel/modules/fuel/config/fuel_modules.php file, line 37 of the $config['modules']['pages'] configuration, there is a line for sanitizing input which overwrites …
-
Thanks... I've pushed an update for this.
-
I've pushed an update to this in the develop branch for you to test out
-
What if you move it to your module and just reference it in the ./application/config/custom_fields.php like so: $fields['my_custom_field'] = array(); include(FUEL_PATH.'config/custom_fields.php'); include(MY_MODULE_PATH.'config/custom_fields.ph…
-
Can you try reinstalling the database first just so we can make sure everything is fresh (I'm assuming this is a new install).
-
Yes. FUEL doesn't support PHP 8.2.
-
Doesn't work on 8.2. https://docs.getfuelcms.com/installation/requirements
-
Do you have PHP 8.1 or lower to try?
-
You may need to essentially pre-process the navigation items to determine the styles parameter values. You can get the navigation in an array structure by using render_type => 'array'. Then you can loop through the data and create an styles array…
-
You can do nested, nested arrays too: <?php echo fuel_nav(array('container_tag_id' => 'topmenu', 'item_id_prefix' => 'topmenu_', 'styles' => array( 0 => 'level1', 1 => array(0 => 'level2')))); ?>
-
It sounds to me that all the files weren't updated. The latest version has all those methods protected. Make sure everything in the fuel/codeigniter folder has also been updated as well as the fuel/modules folder.
-
Is the _set_default_controller() method on both of these files protected? https://github.com/daylightstudio/FUEL-CMS/blob/master/fuel/codeigniter/core/Router.php#L291 https://github.com/daylightstudio/FUEL-CMS/blob/master/fuel/application/third_…
-
Did you update the fuel/application/third_party/MX/Loader.php file by chance when upgrading? Those looks like errors that are probably fixed in the newer version and am wondering if there were some files that didn't get upgraded.
-
I don't currently have MySQL 8 to test. However, I think this may be something with the CI DB Driver but haven't found anything on their GitHub repo about it.
-
Double check that the column is using an auto_increment. If so, then maybe check it manually with the native functions to see if it is indeed the MySQL driver: https://www.php.net/manual/en/mysqli.insert-id.php
-
You may need to go code diving into the /fuel/codeigniter/core/CodeIgniter.php file to see where the 404 is being triggered. Not sure what is going on since you can see the fuel/application/views/offline.php page but you can't see the fuel/applicati…
-
Put some content in that file and see if it is still a 404 error. I'm trying to determine if you have an .htaccess file or something else is going on.
-
The test page should be in the fuel/application/views folder (with content in it).
-
It sounds like the only page that appears is the homepage/installation page correct and not even the test view you created above shows up (neither http://localhost/test OR http://localhost/index.php/test)? Does the offline page appear at http://loca…
-
Ok. It sounds like there is a problem with .htaccess. Have you tried adding a question mark at the end of index.php as in the following in the .htaccess? ... RewriteRule .* index.php?/$0 [L] ... https://www.codeigniter.com/userguide3/inst…
-
If you add a page called test.php with some text like "test" in it in fuel/application/views folder does http://localhost/test appear?
-
Does http://localhost/index.php/home work?
-
Are you able to go to http://localhost/index.php/fuel/login? For http://localhost/fuel/login to work, the config needs to have $config['index_page'] = ''; and the .htaccess needs to be what came in the original zip. Also, Apache needs to have .htacc…
-
Thanks for the report. I've pushed an update for that.
-
It sounds like it may be an issue with the Session. Try setting the $config['sess_save_path'] value in the fuel/application/config.php file to a writable folder full path on the server (.e.g. /var/www/tmp/). Also, delete any cookies from your browse…