Log message #4114752

# At Username Text
# Feb 5th 2018, 21:38 saeideng that is very easy
# Feb 5th 2018, 21:38 quecosa ?
# Feb 5th 2018, 21:38 quecosa oh saedeng that cannot be that easy, really
# Feb 5th 2018, 21:38 saeideng cake 3 and 2 is same in this case
# Feb 5th 2018, 21:37 saeideng https://stackoverflow.com/a/28185392/8016450
# Feb 5th 2018, 21:37 quecosa i tough i could skip the php mysqli select part of the normal jquery ajax way to do it
# Feb 5th 2018, 21:37 inoas you just need two very dead simple cakephp actions - one that fetches all states and one that fetches all cities filtered by a given state
# Feb 5th 2018, 21:37 quecosa thanks ill look for it then
# Feb 5th 2018, 21:36 inoas chain select jquery ajax xhr
# Feb 5th 2018, 21:36 inoas look for chain select jquery or something
# Feb 5th 2018, 21:36 inoas the tricky part is not cakephp but javascript
# Feb 5th 2018, 21:36 quecosa ive seen tutorials, but those tutorials are for old cakephp versions
# Feb 5th 2018, 21:35 quecosa or a tutorial for cakephp 3 plz
# Feb 5th 2018, 21:35 quecosa Is there anybody who could help me with a simple state, city ajax select populate?
# Feb 5th 2018, 21:33 quecosa hi
# Feb 5th 2018, 21:32 inoas cause cake/bake is really of less imporance
# Feb 5th 2018, 21:32 inoas now what I do is using 4.x and fixing cake/bake to an old version so I can run both alongside
# Feb 5th 2018, 21:32 inoas instead of saying: cake/bake only runs on 7.x ...
# Feb 5th 2018, 21:31 inoas Hmm ok anyway, when supporting twig 1.x and 2.x bake won't run unto issues with older PHP versions as well. <= yes but that's the reason TwigView supporting php 5.6 was used by cake/bake in the first place
# Feb 5th 2018, 21:29 night_wulfe Unless I'm misreading the documentation, I mean
# Feb 5th 2018, 21:29 slackebot application's themed folder?
# Feb 5th 2018, 21:29 night_wulfe I'm trying to override theme paths in a CakePHP 2.x application to search a Plugin's View\Themed. This is to allow the theme to override the application's view files. Presently the only way to do this is to put the theme files into the App's View\Themed\ThemName\PluginName folder, which to me breaks the idea of encapsulating plugins from the application. How can I tell CakePHP to search my plugin's themed folder rather than the
# Feb 5th 2018, 21:28 WyriHaximus Hmm ok anyway, when supporting twig 1.x and 2.x bake won't run unto issues with older PHP versions as well. I'll look into moving that way later this week, got some things planned =D
# Feb 5th 2018, 21:27 inoas I have been using twig to render xml
# Feb 5th 2018, 21:27 inoas but I will keep that in mind
# Feb 5th 2018, 21:27 inoas with supports for cells, helpers etc
# Feb 5th 2018, 21:26 inoas that's nice too but in this case I really need an AppView replacement
# Feb 5th 2018, 21:26 inoas Well the question really is what things aim for, if it is low end shared hosting then 5.6 is still ok, but otherwise IMHO it is not. I don't think people will update CakePHP versions but NOT php versions or have problems updating cakephp but not php etc
# Feb 5th 2018, 21:25 WyriHaximus https://github.com/WyriHaximus/php-simple-twig
# Feb 5th 2018, 21:25 inoas hm which package?
# Feb 5th 2018, 21:25 WyriHaximus inoas: did you also see the package I linked you the other day?
# Feb 5th 2018, 21:24 inoas anyway I will try to use real TwigView soon (instead of my hacked SimpleTwigView that just loads your extensions)
# Feb 5th 2018, 21:24 WyriHaximus Depends on how you look at it, 5.6 is going to supported by Zend Server untill december 2020: http://www.zend.com/en/support-center/support/php-long-term-support
# Feb 5th 2018, 21:23 inoas grml
# Feb 5th 2018, 21:23 inoas http://php.net/supported-versions.php
# Feb 5th 2018, 21:23 inoas or well it is EOL now, and extended security will only run until end of 2018
# Feb 5th 2018, 21:23 inoas 5.6 will be EOL in 11 month
# Feb 5th 2018, 21:22 inoas :(
# Feb 5th 2018, 21:22 inoas imho
# Feb 5th 2018, 21:22 inoas the real issue is just cakephp supporting php 5.6 for too long.
# Feb 5th 2018, 21:21 WyriHaximus inoas: Contemplating going 1.x and 2.x with 5.0 if they are compatible and just dropping most of the non-essential extensions