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,767
- Last Active
- Roles
- Administrator
Comments
-
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…
-
Is the home page a view file at fuel/application/views/home.php or is it in the DB under the Pages module with the location of home? If the latter, is the fuel/application/config/MY_fuel.php fuel_mode value set to auto? $config['fuel_mode'] = …
-
That error is not a PHP error but a server error and likely caused by something in the .htaccess. Different servers may have different .htaccess abilities so you may need to check there. There is likely a line in the .htaccess that it doesn't like. …
-
I would start commenting out lines in that file to see which one may be the culprit.
-
I pushed an update to the develop branch for that error: https://github.com/daylightstudio/FUEL-CMS/commit/c364e8c5307744ad161be0703e26a54d00eb17ec
-
Actually, that error is likely with .htaccess. Is it properly configured on the site? If it's not rendering the CodeIgniter error page but the default Apache error it's likely that.
-
Yeah... probably... although, I would highly recommend upgrading your version of PHP if possible (I know that can be easier said then done). 5.4 came out over 10 years ago and was EOF nearly 7 years ago.
-
What version of PHP are you running on the server? If it's still PHP 5.4 then it will throw an error.
-
Likely a PHP compatibility issue: https://docs.getfuelcms.com/installation/requirements
-
What version of PHP and what version of FUEL are you running (you can see the version of fuel in the fuel/modules/fuel/config/fuel_constants.php at the top)?
-
Alternatively, you could use database sessions: https://stackoverflow.com/questions/31042456/session-error-in-codeigniter
-
In the fuel/application/config/config.php try changing the following: $config['sess_save_path'] = sys_get_temp_dir();
-
Sorry...wasn't published: https://github.com/daylightstudio/FUEL-CMS/releases/tag/1.5.2
-
I've pushed an update here to hopefully help with your issue. Let me know if that does the trick: https://github.com/daylightstudio/FUEL-CMS/commit/9f4c0450ea734d582c18b297954373504de7fd87
-
That seems more like a module specific permission error. I can't think of anything that FUEL is to prevent iframes like that. You will need to have a proper session and permissions to view the page though (which it looks like based on the error, is …
-
It looks like the paths are relative. When you view source, what do you see for the paths? Is there a reason you didn't use the css and js properties in the image_selector array? In your case, you should be able to do something like the following: …
-
What does your configuration look like for the custom field?