Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
For example: If you clear this string "%%3f3f" according to the $bad array will fail. The result will be "%3f"
Because str_replace() replaces left to right.
Signed-off-by: xeptor <servetozkan@live.com>
|
|
- anchor() is for local links and breaks ones that don't have a protocol prefix
- Allow :// links (no actual protocol specified)
- Further simplified the URL regular expression
|
|
Signed-off-by: Eric Roberts <eric@cryode.com>
|
|
|
|
As suggested in issue #2134 & PR #2149
|
|
Signed-off-by: Eric Roberts <eric@cryode.com>
|
|
constant FILE_WRITE_MODE contains octal 0666
|
|
Signed-off-by: Edwin Aw <tkaw220@gmail.com>
|
|
Specific codes are as follows, but can easily be changed if a different order/breakdown makes more sense:
- 0: Success; everything executed as planned
- 1: Configuration Error; something is wrong with/in the configuration file(s)
- 2: Class Not Found; what it says
- 3: Driver Method Unsupported; the method you're trying to use on a Driver doesn't exist
- 4: File Not Found; 404 error
- 5: Database Error; something is broken in the database somewhere
- 6: Invalid Input; the user attempted to submit a request with invlaid characters in 1+ key names
7 through 26 are reserved for future use
- 27: Generic Error; generated by show_error() when the status code is >= 100
28 through 127 are errors generated by user applications, normally by using show_error() with a status code below 100
128 through 254 should not be used by applications, as they are reserved by system-level functions
- 255: PHP Fatal Error; automatically generated by PHP for fatal errors, and therefore not allowed for our use
Status codes below 100 are shifted up by 28 to place them in the user error range. It may make more sense to have these codes
left alone and instead shift the CI errors into the 101 through 127 space, but that's not what I opted for here.
It would probably also be a good idea to replace the hard-coded numbers with constants or some such, but I was in a bit of a
hurry when I made these changes, so I didn't look around for the best place to do this. With proper guidance, I could
easily amend this commit with another that uses such constant values.
Signed-off-by: Daniel Hunsaker <danhunsaker@gmail.com>
|
|
so that it's only called by drivers that need it ('mysql', 'mssql').
As proposed in issue #2187.
|
|
Fix and optimize auto_link() URL helper function.
|
|
|
|
|
|
|
|
|
|
Signed-off-by: Eric Roberts <eric@cryode.com>
|
|
Add headers to Output class cache files.
|
|
Signed-off-by: Eric Roberts <eric@cryode.com>
|
|
Signed-off-by: Eric Roberts <eric@cryode.com>
|
|
|
|
feature/output-cache-improvements
|
|
|
|
Exact same behavior, but faster. I also think it's more readable.
|
|
feature/output-cache-improvements
|
|
|
|
|
|
URI->_remove_url_suffix() : suffix has to be at the end of uri_string
|
|
related to #2135
|
|
|
|
related to #2135
|
|
Added protected method _escape_str() to deal with quote escaping.
|
|
|
|
minor tweaks and optimizations to URI library
|
|
|
|
Fix interbase limit issue for subqueries
|
|
|
|
|
|
_fetch_uri_string(); use constant PHP_SAPI instead of function php_sapi_name()
|
|
Fix MSIE conditionals regex in minify output
|
|
to the class property declarations rather than setting them in the constructor. Subclasses can always override in their own constructor if they wish to. Is there a reason why it was done the way it was done? A policy that I am not aware of?
|
|
threshold and Log library instance to reduce function calls
|
|
Allows IE conditionals like the following to remain unmodified.
```html
<!--[if gt IE 8]><!--> <html class="no-js"> <!--<![endif]-->
```
Credit to joebert regex from
http://www.sitepoint.com/forums/showthread.php?696559-Regex-pattern-to-strip-HTML-comments-but-leave-conditonals&s=3eef4ceb0a59b2fdb946fa56220fb6fd&p=4678083&viewfull=1#post4678083
|
|
This reverts commit 8e12c787042396e172a7448c65bd16c3015ffb0f.
|
|
Allows IE conditionals like the following to remain unmodified.
<!--[if gt IE 8]><!--> <html class="no-js"> <!--<![endif]-->
Credit to joebert regex from
http://www.sitepoint.com/forums/showthread.php?696559-Regex-pattern-to-strip-HTML-comments-but-leave-conditonals&s=3eef4ceb0a59b2fdb946fa56220fb6fd&p=4678083&viewfull=1#post4678083
|