I got the Autocomplete widget to work with the following:
Same autocomplete widget file as you but different code in controller and
view file:
Controller:
public $helpers = [
'Form' => [
'widgets' => [
'autocomplete' => ['App\View\Widget\Autocomplete']
Actually mark_story most of the documentation is really really damn good. I
am really not the most advanced coder and I can get around with the docs
and API quite well. So maybe it has to do with laziness as well. But as you
asked, what I never really understood is how cakes errors and exception
I've found the documentation pretty good on the whole, but there are two common
issues:
1) It sometimes it lacks context. I can see the code example, but where does it
go, what does it rely on and what does it impact?
2) It sometimes relies on an existing knowledge of the subject matter or
some
As someone who writes a pile of documentation, what kinds of advanced
things have you found lacking? I've found it challenging to add more
advanced examples as they often end up being very situational and we'll
always have some use case that doesn't have a full example. I'm interested
in what y
I think it's interesting that some people say the docs are terrible and
others list documentation as a reason why it's cool or productive.
If you're build a blog application that will only do simple relationships
and not a lot of complex things, the documentation is great. However, we
typicall
Am using cakephp to display my report and i want to display without
repetiton (for instance survey may have many questions and answers and its
numbers of respondents) for each surveys, using cakephp. And if it help me
about graphs such histogram..
Thx
--
Like Us on FaceBook https://www.facebo
So for me in 3 words, CakePHP3 is:
- Best ORM
- Awesome Book / Docs
- Super Maintainance
TLDR;
CakePHP 2 Tops:
- Book
- Community
- Linkable
- Recursive = 3 ;P
- Cake Bake and great bake looks out of the box
- CRUDv3, Scaffold
- Super maintainance cycles and fast security patches <3
- Super Stabl
1. it relieves me to do the hard (and tedious) work with nice apis and
abstraction layers that allow me to do my job better and quickly
2. it leads me to use good standards with conventions over
configurations that allow me to have a cleaner code that is easier to
mantain
3. it ha
UPDATE: I also have to use $array[0]['Model__i18n_translated_field'] in
normal (not forms) view files.
On Wednesday, October 1, 2014 9:32:05 AM UTC+2, Lucky1968 wrote:
>
> Hi,
>
> I'm using i18n in my application and it seems that in certain views I can
> use $array['translated_field'] as in oth
> why you think CakePHP is a cool or productive framework to work with?
Cool:
1. community
2. lightweight, with very few dependencies
3. easy way to contribute to the sources and docs
Productive:
1. core code moving ahead (enhancements and adoptions of the new PHP
features) wisely, very few depr
1. Good, predictable and easy to understand documentation
2. Incredibly friendly and welcoming community and development team
3. Easy of use
On Tuesday, 30 September 2014 10:28:32 UTC+2, José Lorenzo wrote:
>
> Before giving my own view into this problem, you you guys list the reaso
Hi,
I'm using i18n in my application and it seems that in certain views I can
use $array['translated_field'] as in other views I need to use
$array[0]['Model__i18n_translated_field'] to get the same information
coming from the same find in the same model.
Can anyone tell me why this is?
This
It is https://github.com/cakephp/migrations
Sorry I got it wrong when writing the release
On Wednesday, October 1, 2014 6:01:35 AM UTC+2, Dr. Tarique Sani wrote:
>
> What is the link to the Migrations plugin?
>
> T
>
> On Tue, Sep 30, 2014 at 4:44 AM, Reuben wrote:
>
>> Super excited for separat
On Wed, Oct 1, 2014 at 12:07 PM, Lucky1968 wrote:
>
>
> I suggest you use your solution c), so make everything in English by __()
> and do the translation when your application is ready by extracting the
> .pot files. Extremely easy.
>
Yep! +1 to the above suggestion
./Console/cake i18n extract
14 matches
Mail list logo
