In-Portal Issue Tracker

Welcome to the In-Portal Open Source CMS Issue Tracker! This is a central management / tracking tool for all types of tasks / issues / bugs for the In-Portal Project. Before reporting any issues, please make sure to read the Guide into Issue Tracker and How to Properly Test and Report Bugs!

Dependency Graph

[ View Issue ] [ Relation Graph ] [ Horizontal ]

Viewing Issue Simple Details
ID	Category	Type	Reproducibility	Date Submitted	Last Update
0001442	[In-Portal CMS] Optimization	task	always	2012-11-12 00:10	2012-12-03 09:24

Reporter	Dmitry	View Status	public
Assigned To	alex
Priority	normal	Resolution	fixed
Status	resolved

Summary	0001442: Remove "Compress Compiled PHP Templates" functionality
Description	In recent years we have added a new feature (enabled via Admin setting) that allows Admin user to "Compress Compiled PHP Templates" thinking to secure the compiled PHP code and greatly benefit from it. However as time went by we have notice that this feature actually created multiple issues that we have recently came across. Below is a list of discussion where we talked about this issues cased by this particular feature: Getting out of memory error, when "Compress Compiled PHP Templates" setting enabled - details in additional info field Fatal Error when using Tags with <? in Templates - details in additional info field
Additional Information	Discussion "Getting out of memory error, when "Compress Compiled PHP Templates" setting enabled: At some point of In-Portal life (can't really find when) we've added functionality that allows to compress PHP files in /system/cache folder. Doesn't really give any performance benefit and it's only used to prevent attackers on a shared hosting to easily edit these PHP files (since they are located in publicly writable folder) and make it's data to be shown instead actual website. Functionality described above is enabled by "Compress Compiled PHP Templates" configuration variable (in database "UseTemplateCompression"), which is disabled by default by the way. Fatal Error when using Tags with <? in Templates: Looks like we have quite an interesting bug when we get Fatal Error from Parse when trying to using put custom tags that start <?. Here is an example: <?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?> Error, that I get is: Parse error: syntax error, unexpected T_STRING in [path to template.php] on line 12

Web Development by Intechnic

In-Portal Open Source CMS