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
-
Hmmm... that may be tough. It sounds like this would be something that needs to do with the saved values. You could try adding a pre_process or post_process value to your weight field like so (haven't tested this... and the saved value is JSON encod…
-
If you could provide FUEL access and just the links you are seeing the problem, that would be a good place to start. If you click on my avatar image, you can get my email address.
-
You can change it to "en" => "English", but the first one listed in the languages config is considered the default which means that it won't automatically be appended to the URI.
-
What values do you have for your $config['languages'] in your FUEL config?
-
There is an img_folder parameter you can use: http://docs.getfuelcms.com/general/forms#wysiwyg $fields['textfield'] = array('type' => 'textrea', 'img_folder' => 'images/myfolder');
-
Steps to install: 1. Download and unzip the contents. 2. Rename the folder to "sync" and put it in the fuel/ folder 3. Go to the command line and cd to your folder that your index.php file is and run the following: php index.php fuel/installer/ins…
-
You could potentially do it from production as well by pulling from staging to production. The syncing of assets may take a while and you may need to increase memory and timeouts to do so since it does a CURL request to sync up images not in the env…
-
Does the console request show any HTML in the Response and if so what does it display? To troubleshoot, I would probably need access to try and replicate the issue.
-
The main bootstrap index.php file is where you are seeing those <<<<<<HEAD? If so, have you made changes to that file? If so, you may need to manually merge any changes you made with the FUEL index.php version.
-
I would add it to your MY_fuel.php file instead of overwriting the main fuel.php file (you'll see an example commented out at the bottom of that file). Then you should see these options under the "Settings" module in the CMS.
-
The sync module is intended to bridge the gap of when after a site goes live and the CMS database and assets have changed (we are assuming that the normal FUEL PHP files are tracked and synced via GIT). The sync module has "remotes" configuration va…
-
I would probably recommend extending the fuel_pages_model and overwriting the module's model as displayed here: http://docs.getfuelcms.com/modules/simple#overwrites Then you can leverage a model hook like on_before_save to do any further processing…
-
First, the fix for the category dropdown in the list view is to replace line 10 in the locations_fuel_module.php file with the following (note the key is changed from "category" to "fuel_categories:id"): 'filters' => array('fuel_categories:id' =&…
-
For modifying the locations form, you'll need to modify the locations_model::form_fields method. In your case, you'll want to change the "cities" field to a dropdown. To do that, I'd do something like this: function form_fields($values = array(), $…
-
Try logging out of the CMS and then back in (fuel/logout) and let me know if that does the trick.
-
Those are from a Git merge conflict it looks like. Which file's/URL show this? If you do a search for that string in your project, what file(s) comes up?
-
What are you seeing instead (an error message or nothing)?
-
That DB error looks to be a bug that I will need to look into.
-
For the dropdowns to show up, they need the context value of "locations" (note the where condition in the locations_model.php file for the $foriegn_key parameter).
-
There is a module property of "display_field" that you can specify in MY_fuel_modules.php. By default it will use the first field name without the "_id" suffix. In your case, you may need to use the "_common_query" method on your module to include a…
-
Do you have any categories setup? The categories and tags module are by default hidden. To display them, go to the fuel/application/config/MY_fuel_modules.php file and comment out the line referring to hiding the categories module. Then hit refresh …
-
Sure: <?php echo fuel_nav(array('subcontainer_tag_class' => array(0 => 'dropdown-menu')));?>
-
There is now a "subcontainer_tag_class" property you can use to add to nested "ul" elements. It is an array value in which you'd specify the depth as they key (1, 2..etc) and the value as the class name you want to use.
-
Did you add the following to your .htaccess around line 5? You'll need to turn on hidden files (which I'd recommend if you are dealing a lot with websites and Apache http://ianlunn.co.uk/articles/quickly-showhide-hidden-files-mac-os-x-mavericks/): R…
-
There is an update in the develop branch that should fix the google_geolocate function. The URL use to work when set as https but now does not. So it should now be: http://maps.googleapis.com/maps/api/geocode/json?address=".$address."&sensor=fal…
-
The form in the CMS is created as a simple module I'd recommend reading these to areas of the documentation in particular to become more familiar with them: http://docs.getfuelcms.com/modules/simple http://docs.getfuelcms.com/modules/tutorial Basic…
-
The map being rendered should be at http://localhost/locations/map. You can pull this in via iframe. For the listings you can go to http://localhost/locations/listings
-
What version of FUEL are you running? The fuel_constants.php file should have it as FUEL_VERSION
-
So to be clear, you put the folder in "fuel/modules/" so there is now a "fuel/modules/locations" folder. And it sounds like you add the "locations" module to the $config['modules_allowed'] and installed the database tables. You should remove the …
-
I've posted a fix for that in the develop branch which will be included in the next release.