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
-
The documentation appears as a link on the Dashboard by default. If you install the User Guide module, it will use the stylings from that to make it look a little nicer: https://www.getfuelcms.com/developers
-
Try using a lowercase "Home".
-
If you are seeing a Back to Admin and Logout button only it's most likely that you are viewing a page that is not editable in the CMS and is instead just a static view file correct? Also, do you have the $config['fuel_mode'] = 'AUTO'; in fuel/applic…
-
For the email settings, they should go in fuel/applications/config/email.php (which you may need to create) and not MY_Config.php. Just to confirm, you downloaded the module from the following URL and installed it per the instructions on that page?…
-
Are you wanting to do this with Javascript or PHP? Also, what are you wanting to do with that file name? If you are wanting to perhaps do something with the file itself, there are on_after_post model hooks you can use to further manipulate things on…
-
Have you checked out the Forms module: http://docs.getfuelcms.com/modules/forms
-
There appears to be an issue in the model. I've posted the following fix to the dev branch: https://github.com/daylightstudio/FUEL-CMS/commit/89409cf666662bc1aa7d6b04369b050c040b1d7e
-
I'm sorry but I don't quite understand your question.
-
Are you directly editing the core library Email.php file? If so, I'd recommend either extending it with a fuel/application/libraries/MY_Email.php or create a fuel/application/libraries/email.php file. If you are seeing the email debugging message, …
-
This is actually a fundamental part of how CodeIgniter works. "$this" actually refers to the Controller object which is used to load resources etc. If you want to reference that object from within a different context, you must do something like the …
-
Are there any javascript console errors by chance? Or if you inspect the element DOM do you see any fields there that may be hidden? I don't see issues with the field code above at first glance.
-
I think in your case, you need to specify either a "folder" or "upload_path" parameter. The folder is relative to the /assets directory whereas the upload_path is the server path to upload to.
-
Just to confirm, you have the set the field's parameter of "sorting" to true? You could use an on_after_save model hook to loop through the multi field's value IDs (they should be in the order in which they were sorted) and then retrieve those reco…
-
You have init_display parameter set to "none". That will have it set to collapsed requiring a you to double click the gray bar to display. Try commenting out that line.
-
So it sounds like you were able to get the form to display but upon submission of the form you are getting the PHP mail error correct? If so, perhaps try this: https://stackoverflow.com/questions/3859958/codeigniter-unable-to-send-email-using-php-ma…
-
I suppose you could create a form_builder.php config file and add the following: $config['render_format'] = 'div'; However, that would change it globally and would likely make the admin area a mess. What areas are you needing it as a div? If it's in…
-
The Forms_custom_fields.php file has a recaptcha method in it which is used to render the recaptcha form field. In that method it has a line used to validate the recaptcha on post process: $validator->add_rule("recaptcha_response_field", "validat…
-
Yes, that would help.
-
The preview should be displaying right by the form input field. Are you seeing any errors in the browser console?
-
There is a form function you can call in which you pass it the key of your form: <?=form('my_form')?> That function is simply just a wrapper around: $CI =& get_instance(); echo $CI->fuel->forms->get('my_form')->render();
-
Sure thing... I've updated it.
-
OK. But when you say "the data isn't showed" where are you referring?
-
You can browse to fuel/build and it will compile your change in the linked_field_formatters.js file into fuel.min.js
-
I'm not quite sure I understand what you mean by the data isn't showed? Where are you referring?
-
Are you using your block field type in a page layout form or in a simple module's form?
-
That line should be: return !empty($this->{$found[1]}); It's in the develop branch. I've merged it into the master.
-
I'm not quite clear on what you are trying to do.
-
Are you referring to the block field type? http://docs.getfuelcms.com/general/forms#block If so, you can specify a block layout to a specific group and then reference that in the field parameters using the "group" parameter.
-
See these issues on GitHub for more references: https://github.com/daylightstudio/FUEL-CMS-Forms-Module/issues/13 https://github.com/daylightstudio/FUEL-CMS-Forms-Module/pull/15 Sounds like you'll need the vendor package installed with composer.
-
To check where things may be getting hung up I'd debug Fuel_forms::notify() method around line 1086 in fuel/forms/modules/forms/libraries/Fuel_forms.php. That method is what is used to send out the email using CI's Email class.