Yes. You will need to setup a controller to handle that. Take a look at "advanced modules" which allows you to setup your own controllers, models, views, etc.
http://www.getfuelcms.com/user_guide/modules/advanced
That is strange. If you look at that file, you'll see a require BASEPATH.'core/Controller'.EXT; right above it. That file should contain the CI_Controller class. Do you see that class in that file?
Can you try downloading the latest from GitHub and take the entire contents of the folder and put it on a webserver without upgrading the CI 2? If you install it in a subfolder say called "test" then the URL would be something like http://zkusto.cz/…
Within the downloaded folder, there should be an .htaccess, assets, index.php, README, and a fuel folder that has the application, codeigniter, modules etc. in it. You should be able to put that entire structure into your web's root directory and an…
Adding a javascript file in fuel_javascript is probably the best way for you to insert javascript globally without hacking FUEL code. However, overwriting that particular method may be tricky since your javascript would be inserted before the BaseFu…
One of the ways we do this is to add the "multifile" class to a file upload field in your model's projects_model::form_field() method like so (this is a code example from another project we did):
$fields['image'] = array('type' => 'file', 'class'…
It looks like the most recent upgrade to CI 2.0 reactor caused that change. I did a difff on the 0.9.2 and the 0.9.3 core/URI.php class and found that by removing lines 177-180 would fixes your problem. I did a little research on their BitBucket sit…
You can use use GIT to pull updates if you checked it out from GitHub (instead of using the download button). Otherwise, the following link will show you what changes were made. You could safely download the current folder by clicking the download b…
The reason we that in there is so that textarea will always have the most recent value. This helps for when you enter in text in CKEditor and hit another button on the page, the warning that appears for changing a field will properly be displayed be…
The demo site does require you to install. It also provides a bunch of examples for you through code to show how to create a site with FUEL.
An example of what the front-end of the demo site looks like can be found here:
http://www.getfuelcms.com/…
Hey terdelyi... I just responded to your post. I believe that line is at the very bottom of the Creating Pages tutorial page (I swear I didn't just put it there :-)
In this case, FUEL uses view files to see if a page exist and in this case there are no view files that match. The key is to map a 'view' variable to the URI location. For the news example, it says to insert a news variables file to map the view fil…
Hmm... I just tried on my WAMP server and wasn't able to replicate the problem. In my case I installed the demo site in a subfolder called /v0.9.3 I then changed the .htaccess RewriteBase on line 4 to /v0.9.3/ and then setup the database and changed…
A few questions:
1. Are you able to login to the admin (e.g. http://localhost/fuel/login)?
2. What platform are using (e.g. MAMP, WAMP, etc)
3. What are you seeing instead of the demo?
I'm assuming this is in the admin correct? So that message shows up if a form fields input value has changed since the page was loaded. The fuel/modules/fuel/assets/js/jquery/plugins/jquery.checksave.js is what is controlling that. There are two fun…
That's great to hear!... nice work. One thing I thought of that my help with the navigation, what if you have each language be a different navigation group and then in the code you just reference that group?
I've added it to the list. One thing we are planning on doing for the next release is to make different field types easier to create and extend which should help with your situation.
Thanks for posting...
With regards to the blog posts showing up in the sitemap.xml, try adding this to the file:
/*************************************************************** Add any dynamic pages and associate them to the $nav array here: *****…
Instead of the fuel_pagevariables table, what about adding it to the fuel_page table 'lang_id'? The fuel_pagevariables has a foreign key to that. Then make a compound key between location and lang_id to ensure uniqueness.
The code to initiate the datepicker is in the fuel/modules/fuel/assets/js/fuel/controller/BaseFuelController.js file's add_edit method. We are thinking about compartmentalizing the different Form_builder types a little more to help with issues like …