Are you using 0.93 (master branch) or the 1.0 beta?
That error is most likely coming from the AJAX requests in the DashboardController.js file. Is it perhaps something to do with switch logic in the index.php bootstrap that it simply isn't seeing t…
Unfortunately, I'm not aware of any POSTGRES changes. However, if you are able to make progress on this front, please post back and let us know how it goes.
Are you using 1.0 beta or the 0.93 master branch?
On 1.0, there is a has_many model property that can be used in which you can make multiple many to may associations. 1.0 also has a built in categories and tags module you can use (categories being…
Normally, we'll save that information to a big text field as serialized data. However, if you are saving it in another table, you'll need to modify the method used to retrieve the values to edit. The default method on the model is "find_one_array". …
That is a repo that we control. We will eventually update the site to list other repositories. I'd recommend creating your own GitHub repo and we can list it here and tweet it out. Keep us posted and look forward to seeing what you create.
Also as …
Try using this instead:
https://github.com/daylightstudio/FUEL-CMS.git
Or you can look into creating an SSH key:
https://help.github.com/articles/generating-ssh-keys
When you say saved correctly, is the data serialized into a single text field? If so, did you set the field as a serialized in the model property like so:
public $serialized_fields = array('dates');
Another option is to either overwrite the find_on…
I'm not quite sure I follow. Are you wanting a scenario where you select a something from say a dropdown and it changes the fields below it? If so, there is a "block" field that can be used to select from a list of Fuel block layouts which act as su…
Thanks. This is updated in the 1.0 user_guide:
https://github.com/daylightstudio/FUEL-CMS/tree/1.0
https://github.com/daylightstudio/FUEL-CMS-User-Guide-Module
The index.php bootstrap file is what is used to determine which application folder to use. I'd recommend using the FUEL index.php bootstrap as the starting point (since it contains a couple things specific to FUEL). From within the index.php file, a…
I'm not sure why it would sometimes and not others. A few questions:
1. Are you selecting the same parameters when uploading each time?
2. What's the file size of the zip?
3. Does it actually get uploaded and is just displaying an error message?
…
The Fuel_blog class has a "get_recent_posts" method on it which you can call like so in 1.0:
$posts = $CI->fuel->blog->get_recent_posts(5)
You could also use the fuel_model function but you'll need to specify the "module" parameter like so…
I believe the example you have above is in an incorrect format. Try the following:
public $has_many = array('tags' => array('model' => array(FUEL_FOLDER => 'fuel_tags_model'), 'where' => 'category_id = 1'));
Not really. I think I would start by trying to create a simple static page (without the controller), that loads. Then I'd add in using $this->load->view('_blocks/header') ...etc. Then, perhaps add fuel_set_var('layout', 'main') to the top of t…
A couple things to check:
1. Did you clear the contents of the cache folder? You can log into the admin and click on Page Cache to clear the cache.
2. Is it perhaps an environment setting in that there is a PHP error displaying on the new server be…
My apologies... I mis-informed you about the use_nav_key. That is a boolean value that helps when doing matches for active pages and gets set to true if you are using the CMS since the nav_key value is supplied. To do matching, you need to use the s…
There is a "use_nav_key" parameter you can pass to fuel_nav (was added about a week and a half ago to the 1.0 branch). The default value is set to AUTO, which means if the navigation is created in the CMS, it wil use the nav_key value. You can howev…
That is strange and I don't have an answer for that right now. I would have to debug the model or perhaps MY_Model::save method around line 1444 to see what the $values are being set to save.
Hmm... are you using any model hooks? Perhaps add something like the following in an on_before_validate hook which will run the validation before saving and tell you if there are any errors preventing it from saving:
function on_before_validate($val…
When you say it won't save do you mean that it blanks out the contents of that field or that the changes to the field don't get saved? Have you found certain characters causing problems?
I think I see the issue now. You are right in that it had to do with the belongs_to value being set in the fuel_tags_model. I've posted a fix for that in the 1.0 branch.
Try adding the following to your module's config in MY_fuel_modules.php:
'sanitize_input' => array('template','php')
By default, the xss_clean function is applied to fields which can cause issues sometimes. Adding the above will remove that filte…