Closed kevcomparadise closed 1 year ago
Does it work if you use different files for classes vs the new class
syntax?
I have not tested this but I am not sure Volt works with that (yet).
Does it work if you use different files for classes vs the
new class
syntax?I have not tested this but I am not sure Volt works with that (yet).
Nop same result This work with Phalcon 3.4
I'm also experiencing this issue (in v5.0.2). A workaround that seems to work for my situation is to first set a variable, and then display that variable. Using your example:
Change:
{{ testObject.sub_object.getValue() }}
To:
{% set foo = testObject.sub_object.getValue() %}
{{ foo }}
same problem here. The solution @colinpieper mentioned works but far from ideal especially when you have many templates, like @kevcomparadise said this used to work in Phalcon 3.4.5. Can we expect this to be fixed soon?
I have the same issue and the releases from v5.0.0RC4 to v5.0.4 have the issue but the release v5.0.0RC3 works fine
Any update on when this will be fixed please?
We are working on this one guys. Hopefully we can figure out where it comes from.
I checked a bit the code and it seems to fail in the code to ob_start()
so that might be happening in Zephir.
This has been resolved in https://github.com/phalcon/cphalcon/pull/16187.
Thank you @kevcomparadise @colinpieper
Describe the bug When we try to access a public method of a sub class contained in a public property of a root class, Volt generates a Notice. PS : Return value OK
To Reproduce Steps to reproduce the behavior:
Note : If we use a getter for sub_object (like : getsubObject()) it work
Expected behavior Render without notice
Details