#9122 closed Bug (fixed)
CKFinder for PHP4x websites
Reported by: | zoey | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | General | Version: | |
Keywords: | CKFinder | Cc: |
Description
I've recently updated to the latest CKFinder 2.2.2 in hopes of resolving the Chrome 20x pop-up issue (it did not help, popup problem continues). Since we are on a server which has PHP4x and will not be updating to PHP5 (too many internal server reasons to list here), the new CKFinder was not loading properly because of this error in the server log:
PHP Parse error: parse error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or '}' in /.../core/connector/php/php4/Utils/Misc.php on line 54,
Therefore, in order to successfully get CKFinder loaded, I had to comment out this function beginning in line 54 /core/connector/php/php4/Utils/Misc.php
/* public static function encodeURIComponent($str) { $revert = array('%21'=>'!', '%2A'=>'*', '%27'=>"'", '%28'=>'(', '%29'=>')'); return strtr(rawurlencode($str), $revert); } */
With this code commented out, CKFinder loads normally. I hope these notes help developers in making sure CKFinder will work with either PHP4x or PHP5x in the future.
Change History (2)
comment:1 follow-up: 2 Changed 13 years ago by
Keywords: | CKFinder added |
---|---|
Resolution: | → fixed |
Status: | new → closed |
comment:2 Changed 13 years ago by
Replying to wwalc:
Oops, thank you for reporting it.
Could you try CKFinder for PHP 2.2.2.1? The issue should be fixed there. Please let us know in either case.
Thank you for the update, I appreciate it very much. All these issues have been resolved.
I've updated to CKEditor 3.6.3 (PHP version) with the latest nightly build Revision number: 7566 and also to CKFinder 2.2.2.1.
RESULTS:
Resolved: Google Chrome version 20x popup
Resolved: CKFinder for PHP4x websites (this ticket #9122)
Resolved: CKEditor 3.6.3 full-page edit affects titles (ticket #9121)
Oops, thank you for reporting it.
Could you try CKFinder for PHP 2.2.2.1? The issue should be fixed there. Please let us know in either case.