php cannot access protected property
Получаем доступ к приватным свойствам объектов в PHP без рефлексии
Несколько недель назад я работал над проблемой в ProxyManager. Проблема была проста: ReflectionClass и ReflectionProperty очень, очень, и ооочень медленные!
Причиной этого исследования является моя попытка оптимизировать «hydrator» для работы с большими объемами данных без накладных расходов на инициализацию.
PHP 5.4 выручай!
Определим замыкание для получения этого поля:
А теперь украдем yummy из экземпляра Kitchen :
Сделаем нашего вора умнее Closure#bind() :
Closure::bind vs Reflection: быстродействие
Я сделал простой бенчмарк для 100000 итераций инициализации:
На только что скомпилированном PHP 5.5 (Ubuntu 13.04 amd64 box), первый тест занял 0.325 секунд, а второй 0.658.
Рефлексия здесь гораздо медленнее.(На 49%)
Но это совсем не интересно, так как никому не потребуется инициализировать 100000 раз одно и то же, по крайней мере мне точно. Что на самом деле интересно — так это доступ к приватным свойствам. Я протестировал и это тоже:
0.110 секунд, а второй
0.199!
Это гораздо быстрее рефлексии, впечатляет!(На 55%)
Доступ к приватным свойствам по ссылкам
Есть еще одно преимущество, используя замыкания вместо рефлексии мы можем работать с свойствами объекта по ссылкам!
Универсальный метод доступа
Учитывая выше сказанное, мы можем написать простую обертку для получения любого свойства любого объекта:
Рабочий пример.
У нас есть доступ к любому свойству, в любом месте, и даже по ссылке. Ура! Мы нарушили правила еще раз!
Заключение
В очередной раз PHP показал себя с хорошей и плохой стороны одновременно. Это ужасный язык, с ужасным синтаксисом, но он позволяет нам обходить любые языковые ограничения радуя нас новой функциональностью с каждым релизом.
Я не буду использовать эту технику сам, но если мне потребуется получить приватное свойство объекта, да еще и по ссылке, я сделаю это именно так.
Дисклеймер: используйте данную возможность с осторожностью!
Cannot access private property
I have a problem with the following code, I am trying to print the data of a student but I get the following error:
Fatal error: Uncaught Error: Cannot access private property Secretary::$students
If i put the attributes as public, it works correctly.
3 Answers 3
What you want to do is this:
This will act as expected.
If you want to know more about access modifiers, you can read about them here.
You need a setter function for this. You cannot directly access a private variable.
This function will look like:
Afterwards you can use your function ‘printStudents’ to printout all students.
You cannot access a private property of a class outside of its own scope. To achieve what you want, consider making a new method like so:
Then, you can append your new student to the Secretary.
You can see a live demo of it working.
Not the answer you’re looking for? Browse other questions tagged php or ask your own question.
Linked
Related
Hot Network Questions
Subscribe to RSS
To subscribe to this RSS feed, copy and paste this URL into your RSS reader.
site design / logo © 2021 Stack Exchange Inc; user contributions licensed under cc by-sa. rev 2021.9.17.40238
By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.
Fatal Error: Cannot access protected property OutputPage::$styles #23
Comments
atrus1701 commented Oct 10, 2014
I am getting the following error when installing this plugin:
Fatal error: Cannot access protected property OutputPage::$styles in /home/wikiuncc/public_html/test/extensions/WYSIWYG/CKeditor.body.php on line 191
I have commented out the foreach statement on line 191 of CKeditor.body.php and it seems to work now. The OutputPage::$styles was an empty array, so for my purposes, it’s not needed but it would be great if this could get fixed in future versions.
The text was updated successfully, but these errors were encountered:
We are unable to convert the task to an issue at this time. Please try again.
The issue was successfully created but we are unable to update the comment at this time.
riparap commented Oct 13, 2014
There are installations using branch «CKeditor_v4» without problems. Could this be some kind of environment specific issue.
I am wondering what is the version of wysiwyg you are using. Would you be so kind and give a little more detailed information about versions of components of your installation: MW, PHP, database, web server, wysiwyg.
LunaticMuch commented Nov 28, 2014
I have the same issue:
Fatal error: Cannot access protected property OutputPage::$styles in /var/www/html/wiki/extensions/WYSIWYG/CKeditor.body.php on line 191
These below are my env details:
MediaWiki 1.24.0
PHP 5.5.9-1ubuntu4.5 (apache2handler)
MySQL 5.5.40-0ubuntu0.14.04.1
WYSIWYG extension 1.5.6_0 [B551], based on this version, modified further, using CKEditor 4.4.5 (revision 25cdcad)
riparap commented Nov 28, 2014
Ok. I did not notice that there already was this issue open, when I created new one #31 :). I will close issue #31 because it is dublicate with this #23.
One workaround would be to change MW variable «styles» in includes/OutputPage.php to be «public». If you choose to do this, you will do it at your own risk, because I am not aware of security effects of this kind of modification. Variable has been declared as «public» in MW versions
bruce1949 commented Feb 8, 2015
I have the same problem, Wiki version: 1.24.1 php 5.5.15, mysql:5.6.20, I accept your comment, to comment out lines 191-211 and I experienced another error
Parse error: syntax error, unexpected ‘>’ in D:\xampp\wiki\extensions\WYSIWYG\CKeditor.body.php on line 214
If I comment out lines 191-214, I can edit pages some warning messages is showed on the top of every pages;
Notice: Undefined variable: inlineStyles in D:\xampp\htdocs\wiki\extensions\WYSIWYG\CKeditor.body.php on line 216
Warning: Invalid argument supplied for foreach() in D:\xampp\htdocs\wiki\extensions\WYSIWYG\CKeditor.body.php on line 216
Do we have new solution now?
BTW, This is the best wiki editor I used. Thanks a lot for your contribution, Very appreciated.
riparap commented Feb 8, 2015
I am just wondering if that rearranging of styles in CKeditor.body.php is needed at all anymore with current browsers. Simplest final solution would be to comment that part out completely, but I have been unwilling to do it because I am not sure if it is still needed or not.
bruce1949 commented Feb 8, 2015
Thanks a lot, As an IT guy, I am willing to contribute on the project and want to share my knowledge to others, But I know little about PHP programming, and I am learning to promote my PHP, I would like to do something when I can,
Thanks a lots for your help.
bruce1949 commented Feb 8, 2015
This is a update message.
I think I make it successfully with your instruction, Thanks a lot, in my files, I comment out lines from 194-214,
HilmiDEV commented Apr 22, 2015
The extension is work now perfectly but i want if i can not use this extension in some pages means the extension work in all the pages except some pages.
bruce1949 commented Apr 23, 2015
Thanks a lot for your update. I will try it on my wiki, thank you everything.
The extension is work now perfectly but i want if i can not use this extension in some pages means the extension work in all the pages except some pages.
―
Reply to this email directly or view it on GitHub.
fullduplex1 commented Aug 23, 2015
as line write just before foreach loop
if(!empty($out->styles) and is_array($out->styles))
riparap commented Sep 1, 2015
Thanks, this workaround has been included in branch CKeditor_v45 «Version 1.5.6_0 [B551+01.09.2015]».
riparap commented Mar 26, 2016
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.