Actually -- I just remembered -- our server team has moved us onto nginx...and from what I remember when they did it...they maybe don't even use the .htaccess anymore...so...I guess I'll likely need to get with them. Thanks for the response.
As of 1.4.7 we are able to add script tags via our input fields...we essentially have a footer code and header code textarea filed that allows that on an as needed basis for quick fixes, etc. As I said before, our content managers are front end devs…
Yeah....neither is really a great option to be honest. If I just "disable" purifier using the new option, then sure it allows style tags, but then I can't allow script tags. If I use purifiier I can allow script tags using HTML.Trusted or whatever, …
Honestly, anything in-between -- including the tags themselves -- are being stripped out (on save) of the textarea regardless of what I set in "sanitize_input" for the given layout.
The only way I found to fix it was on a model by model basis (p…
So it looks like I have to add: public $auto_encode_entities = false; to models if I want to use JS in a textarea as of 1.4. Is that correct?
That's fine with modules...but if I want to use JS in fields in page layouts...then I have to add that t…
Yeah, found this at the top:
public $has_many = [ 'filter_subjects' => [ 'model' => 'subjects_model' ], 'products_they_use' => [ 'model' => 'products_…
Actually...v1.2 had $related_model and that's what the former developer was using ['products'] for there I believe...and that was working. The thing that seems to be missing in his call is $related_field -- which is the newly added first parameter (…
Ok...changed it to /var/www/test-session (temporary test folder) and it seems to have fixed the issue. So is changing the session path to outside of the root the solution, or just a symptom to another issue I should be concerned with? Because even w…
Interesting...is that a new setting in 1.4? We don't have that variable set in our current 1.2 install.
Without me modifying anything, it seems to be set to APPPATH.'cache/' on the 1.4 install...which would make sense that clearing the cache woul…
So this was basically being caused by a internal apache function (tolower) I was using on my previous server to force all urls to lowercase that wasn't working on this one...not sure if it's an apache config issue or something that the newer version…
Just an update, I think I've narrowed it down to something in my .htaccess file. After a fresh install of Fuel 4...everything was fine...started adding things back from my current site one step at a time, and on the very first step ran into the erro…
It’s a fresh install of 1.4, but I’ve copied all of my controllers and models and renamed them as instructed. The front-end of the site is displaying and working fine as far as I can tell...just running into this jqx issue with the backend.
I know this post is ages old...but I wanted to see if there was ever either A) an update to fuel that allows uploading assets to S3, or if you guys knew of anyone that was able to get it working. Thanks!