In the recent cakePHP 1.3.4 version I discovered that Sanitize::html returns double encoded html entities - because of the newly added fourth parameter of htmlentities 'double_encode'.
Here is a corresponding ticket on cakePHP: http://cakephp.lighthouseapp.com/projects/42648/tickets/1152-sanitizehtml-needs-double_encode-parameter-in-htmlentities
Since I need to use cakePHP 1.3.4 on PHP 5.2.14 I need to change the double_encode parameter. Is there a way to overload the Sanitize::html method in cake so I don't have to fiddle with the core?
You can subclass it in the /app/libs directory:
App::import('Sanitize');
class MySanitize extends Sanitize {
public static function html(...) {
...
}
}
You'll have to switch to use MySanitize instead of Sanitize, but that shouldn't be a big problem. A text find/replace can take care of it if you're using it a lot already.
Related
I'd like to override a function that exists in the CakePHP 3 core (to be more specific Cake\Database\ValueBinder).
How can I achieve this? I tried copying the class to src/Database/ and changed the namespace from Cake to App. I use'd the class in AppController, but had no luck.
Thanks in advance
Adrian
ndm helped me a lot with this (see comments to my question), but since he didn't post an answer I am doing this now.
It's possible to use an own ValueBinder by setting it on my query: $this->Table->find()->valueBinder(myOwnValueBinder).
To make that the default ValueBinder in my own code (sufficient in most cases) one can use e.g. an AppTable as known from CakePHP 2 that extends to Table and make all other *Table classes extend AppTable. Now one only needs to create the following method:
public function query() {
return parent::query()->valueBinder(myOwnValueBinder);
}
In case it's needed that all code uses teh custom ValueBinder, an extended datasource Connection class has to be created (and used). In this class Connection::newQuery() has to be overriden.
I would like to implement an autoslug-function for two models in CakePHP3 and use the beforeSave-callback for that which works fine. However the slug structure is a bit different than in Inflector::slug, so I wrote a small function for the different structure which finally leads to my question
In Cake2 I would have placed this helper function in AppModel which is not existing anymore. What's the best way to do that now? A behaviour (which seems a bit biggish for 2 lines of code) or class AppTable extends Table or ..?
Make it a behavior and use it where needed instead of putting it in a super model class. If you put that into a plugin and repository you can simply add your plugin as package via composer for every app that needs this plugin.
So, in CakePHP, there is a way to turn off labels by default by putting 'label'=>false in 'inputDefaults' in the Form->create() statement.
Is there a way to, instead of removing labels altogether, to change labels into element placeholder attributes? This is equivalent to doing the 'inputDefaults'=>array('label'=>false) on the Form->create while adding a 'placeholder'=>'Placeholder' to each element... but is there a way to do it without having to add it to each element and have CakePHP do it for you?
You could run your own copy of FormHelper that contains your modifications. You can copy the version of FormHelper from lib/Cake/View/Helper/FormHelper.php and paste it into your app at app/View/Helper/FormHelper.php and make the required modifications to your copy. The copy in your app folder takes precedence over the one provided in the core. As always, never ever ever make modifications to files in Core.
Alternatively, you could extend FormHelper into your own Helper class:
class MyFormHelper extends FormHelper {
...
}
Don't forget to add 'MyForm' into your $helpers array!
At any rate, what you're asking is not currently possible using Cake 2.x. Without any changes, you'll need to add a 'placeholder' => '...' in the options array of each input() call. If you make this change, please consider contributing it back to the CakePHP community so others can benefit from your work!
I'm trying to export a data view to Excel format but can't find a helper that works with Cake 2.x
The closest I found was http://bakery.cakephp.org/articles/wasenbr/2007/04/12/excel-xls-helper but that throws errors like this
call_user_func_array() expects parameter 1 to be a valid callback, class 'XlsHelper' does not have a method 'beforeRender'
Does anybody have a link to a helper that will work in newer versions of Cake?
The helper works if you just add blank functions for all the errors that appear.
I have a module that handles translations.
It is not bound to any database, the file is purely and simply something like this:
$arr["key1"]="text";
...
I need to make Ajax calls in order to edit that file. That file will be imported each time a page is accessed in order to deliver any text content that I need (it may not be the best thing of the world but it does the job, and it's supposed to be really fast since there's no "XML parsing" kind of thing, it is simply stored in a standard .php file).
To handle these ajax calls that will have actions like Add/Edit operations, I have made a TranslationController that is Model-less:
class TranslationsController extends AppController {
public $uses = array(); // Model-less
public $components = array('RequestHandler');
public $helpers = array('Session');
protected $translationFilePath;
public function setItem() {
}
public function backupFile() {
}
}
My problem is simple: where do I put custom functions that are used to open/write/find in files?
For example I have a function that extracts a key from the line that is being read.
I've seen some posts where we are advised to place the data inside the model but in my case I have no model AND it's these functions are not linked to the data. So it shouldn't be in the model, right? I do not want it to be global.
Thank you for your help.
Why are you not using the built in translation stuff that comes with CakePHP and is based on the more or less standard gettext tools?
What you're doing is just re-inventing the wheel and probably coming up with a non tested customized translation implementation that is obviously lacking feature that CakePHP alreay offers you. For example how do you handle plurals?
CakePHP offers you __(), __d(), __n(), __dn() for translations and the translation files are stored in APP/Locale/ as plain text files and are edited with poedit.
See http://www.gnu.org/software/gettext/ and http://book.cakephp.org/2.0/en/core-libraries/internationalization-and-localization.html
Sounds like a use case for a custom datasource: http://book.cakephp.org/2.0/en/models/datasources.html.
Personally, I would just create a normal PHP class in the app/Lib folder of your application.