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,799
- Last Active
- Roles
- Administrator
Comments
-
Ah... the demo is pretty old and may need php 5.4.
-
This is an older version but may help: https://github.com/daylightstudio/daylight-roasters
-
It sounds like you should be able to do that. I'd try adding the following to your projects and awards models: public $has_many = array( 'tags' => array( 'model' => array(FUEL_FOLDER => 'fuel_tags_model'), …
-
It does sound like a session issue. Sometimes it has to do with where the session information is being saved may not be a writable folder. You can try setting up a writable /tmp directory above the web root and set the fuel/application/config/config…
-
Can you paste the code in your MY_fuel_modules?
-
I'd have them try deleting their cookies and see if that fixes it first.
-
Does the "stories" table have a "published" or "active" field? If so, is it set to "yes". By default, FUEL will look at those to fields to automatically not include those in the query. Similar with "publish_date". You can do this->stories_model-&…
-
I was able to replicate your issue and have pushed a fix to the develop branch.
-
There does appear to be a bug in the docs like you suggested (I've posted a fix in the develop branch and updated it on the live docs).
-
Does just the following work? <?=fuel_var('metadescriptionposter')?>
-
You can try the following: <?=fuel_block(array('view' => 'myblock', 'parse' => FALSE))?>
-
Interesting. Thanks for the update.
-
Another thing you could try is adding the following to the fuel/application/config/custom_fields.php to overwrite the existing configuration for the select2 custom field: $fields['select2'] = array( 'class' => array(FUEL_FOLDER => '…
-
It will depend a lot on the custom changes made to your version in how well the upgrade goes. We typically will handle it through GIT and point to GitHub FUEL Repo as a remote source and merge in that way resolving any conflicts that usually happen …
-
You mind testing something out on your end? Line 1485 in the custom_fields.js file to add a cache breaking query string parameter (timestamp) to the AJAX call: var embeddedListAjax = $.post(__FUEL_PATH__ + "/" + $activeEmbeddedList.data("module-u…
-
Does it work if you attach data attributes to the element like in the following: $fields['states'] = array('type' => 'select2', 'data' => array('maximum-selection-length' => 5, 'maximum-input-length'=>3));
-
On load it does AJAX... only on updates. Does it sound like you are seeing a cached version of older data? If you check the database, is the data updated?
-
Are you able to see in the console AJAX requests when deleting a record (it should be using AJAX to refresh that area).
-
Hi weblar, Are there any errors that are displaying in the console. The embedded list view does trigger an event when it's complete on the document object that you can listen to. If you add the following field it should console.log to your browse…
-
If your application has a separate login than FUEL, than you'll want to create a separate table with your own user session using maybe something like Ion_auth (https://forum.getfuelcms.com/discussion/comment/11090#Comment_11090). FUEL handles ses…
-
What version of FUEL are you using? (echo FUEL_VERSION) Have you upgraded to the latest to see if it fixes your issue?
-
Unfortunately it's tough to tell from the screenshots and code to properly debug. I would start from where it's originally called and debug from there. It may take you into the internals of the MY_Model class.
-
When you say "i want to call get_ajax_csrf() through url" do you mean you want a URL that returns the CSRF token? If so, you can create a method on your model called "ajax_csrf_token" and then it would be available at fuel/{module}/ajax/csrf_token: …
-
The php index.php fuel/installer/update is actually just for upgrading from 1.3 to 1.4 due to the changes in file names, caused by CI 3. So to actually update the version of FUEL, we typically setup the FUEL github repo as a remote and pull from it …
-
What are the folder permissions for that folder?
-
Can you access the following? http://bgterhome-new/index.php/fuel/login
-
That error message can sometimes be due to a casing difference on the file. Is the model's file name "Ion_auth_model" or "ion_auth_model"? Also, how is that class being loaded into the page (e.g. $this->load->model(...), require, include, etc)?
-
What version of PHP are you running?
-
Thanks... it looked good and I merged it in.
-
That would be the way to do it at this time.