PHP Function Support, Extended Documentation and UTF8 Settings

[brookinsconsulting]

Hello Open-Wide / eZ Community!

Today we present for your review and acceptance:

• Whitelist (eZ Publish INI Settings) PHP Function Support within eZ Publish Templates (eZ 4.x Only)
• Extensive GitHub Markdown based extension documentation
• UTF8 Encoded Settings

Please accept this pull request into your master repository branch of OWSimpleOperator and help other users make use of Whitelisted PHP Functions within custom eZ Publish templates.

Cheers,
Brookins Consulting

[brookinsconsulting]

Since this extension pull request was not understood, commented on, accepted or welcomed it has now been closed.

[rey0bs]

Thanks for your quality contribution.

Please apologize our lack of answer. We will welcome your gift, as we must to do it.

[rey0bs]

Hi,
How exactly works phpfunction operator ?

I try this following :
{def $output = str_replace('tototatatiti', 'tata', 'titi')}
and
{def $output = 'tototatatiti'|str_replace('tata', 'titi')}

But I get this error message :
array_values() expects exactly 1 parameter, 2 given in /var/www/ez/extension/owsimpleoperator/autoloads/owsimpleoperator.php on line 317

Thanks in advance !

[brookinsconsulting]

Hello Sboye,

Thank you very much for your replies.

Regarding the error you get.

It has been some time since we used this improved extension so our answers may be dusty.

We seem to remember getting the error message you shared when the changes made to "autoloads/eztemplateautoload.php" were not made or were not exactly as provided in the following commit...

brookinsconsulting@028a556

We suggest comparing your local changes (diff/run the code) to the extension OWSimpleOperator with our own github copy: https://github.com/brookinsconsulting/OWSimpleOperator which did not have the error you mention.

The solution to that error you share was a very specific one that required the above autoload file to be re-written to check for PHP functions and allow them to be used even if they use more than one parameter.

Best wishes

Cheers,
Brookins Consulting

[brookinsconsulting]

Hello Open-Wide,

We wanted to inquire on the status of our pull request. We would be happy to help in any way we can get our changes into the extension in question.

Cheers,
Brookins Consulting

[brookinsconsulting]

Hello @sboye / Open-Wide

We offer our most sincere apologies for our previous weak replies. We truly were not having the problems you were reporting so it made testing and solving the problems nearly impossible at the time.

Tonight I set it upon myself to once and for all solve the problems you reported and once again prepare this pull request for another review. In our commits for tonight we have done two things.

First we have solved the errors you were reporting. We have tested with both single parameter php functions and multi-parameter php functions. I am very certain that the previous template operator parameters conversion to php function parameters errors are now finally solved.

Second we have merged in the more recent changes made to the master branch into the php_function_support feature branch solving the merge conflict issue with this pull request. Now this pull request can be automatically merged normally without conflicts.

We realize that a lot of time has passed since we first submitted this pull request.
We ask now for another chance at a round of review and testing of our pull request changes.

Please let us know what you think! Thanking you in advance for your continued support!

Cheers,
Brookins Consulting
Skype: brookinsconsulting
Email: info at brookinsconsulting dot com

[rey0bs]

Hello @brookinsconsulting !

Thanks a lot for your contribution and your last fix. This pull-request will be merged.

Cheers