| # |
Mar 5th 2018, 13:02 |
 admad |
shiftplayer: it's not, but https://github.com/FriendsOfCake/crud-json-api is |
| # |
Mar 5th 2018, 13:00 |
admad |
@dereuromark "Spares me the internal request baggage" cells don't do any internal request |
| # |
Mar 5th 2018, 12:34 |
shiftplayer |
does anybody now if the JSON View described in the documentation (https://book.cakephp.org/3.0/en/views/json-and-xml-views.html) is compatible with json-api? (http://jsonapi.org/) |
| # |
Mar 5th 2018, 12:33 |
shiftplayer |
Hi |
| # |
Mar 5th 2018, 12:20 |
portilloster |
but the idea is to have a login, and in the next view you can see the name of the person that is logged |
| # |
Mar 5th 2018, 12:19 |
neon1024 |
Hehe! |
| # |
Mar 5th 2018, 12:19 |
portilloster |
I do not know whether the docs need tweaking, to be honest Im just a simply junior dev and I just do what I´m told! |
| # |
Mar 5th 2018, 12:18 |
portilloster |
thanks @neon1024!! It worked!! |
| # |
Mar 5th 2018, 12:04 |
joshualuckers |
but maybe helpers are a better solution |
| # |
Mar 5th 2018, 12:04 |
dereuromark |
I still use component+helper mix here :slightly_smiling_face: Spares me the internal request baggage |
| # |
Mar 5th 2018, 12:04 |
joshualuckers |
I use cells to make reusable pieces of templates. For example a "ProductPriceCell" that can be reused in different views. |
| # |
Mar 5th 2018, 12:03 |
neon1024 |
I like them for database driven navigation, and some sidebars |
| # |
Mar 5th 2018, 12:03 |
dereuromark |
Really? anything in cells can be done otherwise as well, or at least I thought so until now. |
| # |
Mar 5th 2018, 12:02 |
neon1024 |
I love a view cell :slightly_smiling_face: |
| # |
Mar 5th 2018, 12:01 |
dereuromark |
It doesnt work with cells yet quite well afaik - but tbh, I never use cells anyway. Dont find them useful. |
| # |
Mar 5th 2018, 12:00 |
dereuromark |
The plugin workaround using https://github.com/dereuromark/cakephp-tinyauth/blob/master/docs/Authorization.md#authusercomponent works fine for me (and all others) for the time being, but I would still like to see this landing in core at some point. |
| # |
Mar 5th 2018, 11:58 |
dereuromark |
yes, opened April 2015: https://github.com/cakephp/cakephp/issues/6247 => evolved into https://github.com/cakephp/cakephp/issues/6925 but should have never closed due to the missing request part IMO that the helper/view level needs :slightly_smiling_face: |
| # |
Mar 5th 2018, 11:55 |
neon1024 |
Oh, there is a ticket already? Will the new Auth middleware change the way the view layer, accesses the auth information |
| # |
Mar 5th 2018, 11:52 |
dereuromark |
But some docs until then probably cant hurt :slightly_smiling_face: |
| # |
Mar 5th 2018, 11:52 |
dereuromark |
No, it means we have to get this ticket done that is dormant for 3 years, to move everything to its own request (kind of) level. |
| # |
Mar 5th 2018, 11:51 |
neon1024 |
Perhaps this is an indication that the docs need tweaking? |
| # |
Mar 5th 2018, 11:51 |
dereuromark |
also it breaks non-stateless approach usually, and has other cavities |
| # |
Mar 5th 2018, 11:50 |
neon1024 |
I also wouldn’t want to have a component being accessed from my view layer |
| # |
Mar 5th 2018, 11:50 |
dereuromark |
Or, if you use tinyauth AuthUser helper: `$this->AuthUser->user('username')`. No, never ever use AuthComponent here, and statically even never ever ever :slightly_smiling_face: |
| # |
Mar 5th 2018, 11:49 |
edgaras.jan |
`AuthComponent::user('username')` https://book.cakephp.org/3.0/en/controllers/components/authentication.html#accessing-the-logged-in-user |
| # |
Mar 5th 2018, 11:48 |
neon1024 |
`getSession()` now, if you’re on 3.4+ |
| # |
Mar 5th 2018, 11:48 |
neon1024 |
I use this personally, `$this->request->session()->read('Auth.User.username')` |
| # |
Mar 5th 2018, 11:47 |
neon1024 |
If you’re using the AuthComponent you should be able to read it from the Session |
| # |
Mar 5th 2018, 11:42 |
portilloster |
Hi guys! Can you please help me with this basic problem? In the default layout template I want to show the logged User Name in this div: <div class="top-bar-section"> <ul class="right"> <li><a target="_blank" href="#">USER_NAME</a></li> </ul> </div> How can I do this? Thanks!!! |
| # |
Mar 5th 2018, 11:21 |
dereuromark |
always check log files here, they contain the info you need. |
| # |
Mar 5th 2018, 11:20 |
ghoritrilochan |
File uploaded https://cakesf.slack.com/files/U73224C20/F9KC9UN30/image.png / https://slack-files.com/T053DPNCM-F9KC9UN30-9dd8ed1088 |
| # |
Mar 5th 2018, 11:20 |
ghoritrilochan |
hii.. plesk in host my first project. plz help |
| # |
Mar 5th 2018, 09:44 |
em. |
@dereuromark ok thx! :slightly_smiling_face: |
| # |
Mar 5th 2018, 09:40 |
dereuromark |
compsoser.json I mean |
| # |
Mar 5th 2018, 09:40 |
dereuromark |
I keep it lean. Adding the initial code and composer.install so I can composer require it in my app, then finalizing it from there with the ability of doing testing and also in-app-testing. |
| # |
Mar 5th 2018, 09:35 |
em. |
So what is your approach on this? If you start a new cakephp plugin? |
| # |
Mar 5th 2018, 09:24 |
dereuromark |
They would be in vendor then usually, though. |
| # |
Mar 5th 2018, 09:23 |
dereuromark |
Sure, you can do that. Whatever works for you. |
| # |
Mar 5th 2018, 09:22 |
em. |
Hey, good morning! What would be the best workflow for developing, test and maintain all your (private) cakephp plugins? For example, should i make a fresh cakephp project, and maintain my packages in the plugin folder; which all contain git repositories? Or is there a better approach? I can’t find any good reads about it. Maybe someone can point me to the right direction… |
| # |
Mar 5th 2018, 09:16 |
dereuromark |
You could use my Passwordable behavior (in Tools plugin) which ships this functionality out of the box |
| # |
Mar 5th 2018, 09:02 |
clementcrown |
good morning all |
