| # |
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 |
| # |
Feb 5th 2018, 21:21 |
inoas |
just support 4.x longer? |
| # |
Feb 5th 2018, 21:21 |
inoas |
so 5.0 won't drop 1.x support? |
| # |
Feb 5th 2018, 21:20 |
WyriHaximus |
inoas: the thread from the other day got my doubting about the course to take with 5.0 |
| # |
Feb 5th 2018, 21:20 |
inoas |
or is 4.0 Twig 2.x and my brain is damaged? probably |
| # |
Feb 5th 2018, 21:20 |
inoas |
I think TwigView 5.0? |
| # |
Feb 5th 2018, 21:20 |
inoas |
WyriHaximus: any idea when you will tag up a Twig 2.x release? |
| # |
Feb 5th 2018, 20:58 |
maneken |
ok. I'll try that. Thanks again! |
| # |
Feb 5th 2018, 20:58 |
WanderingJon |
@maneken I can relate to what you're doing, but it's easier to just make the table and move on. Especially if you need to check login status later. |
| # |
Feb 5th 2018, 20:54 |
maneken |
maybe my approach is wrong. Would you suggest to create a db table users, add just one user with it's hashed pass, and go with the standard cake authentication? |
| # |
Feb 5th 2018, 20:49 |
maneken |
WanderingJon: thanks for the reply. I don't have a problem to use a Model. I'm trying to avoid using a db table for just one record |
| # |
Feb 5th 2018, 20:46 |
WanderingJon |
Have you checked https://book.cakephp.org/3.0/en/core-libraries/form.html ? |
| # |
Feb 5th 2018, 20:45 |
WanderingJon |
It would be simpler to just set up the model and add 1 admin user to check against. |
| # |
Feb 5th 2018, 20:44 |
WanderingJon |
maneken, may I ask why you're doing it that way? I imagine that would make things more complicated later on. |
| # |
Feb 5th 2018, 20:35 |
maneken |
Do I have to create a model, even if I won't use the database for the authontication? |
| # |
Feb 5th 2018, 20:35 |
maneken |
I created a User controller (I haven't created a Model), and I want to write a login function that checks the hash of $this->request->data['password'] against a hardcoded hash |