Age | Commit message (Collapse) | Author | Files | Lines |
|
Signed-off-by: Sajan Parikh <sajan@noppix.com>
|
|
Signed-off-by: Sajan Parikh <sajan@noppix.com>
|
|
|
|
Also applied @xeptor's fix (a big thanks) to the sanitize_filename() method and added a changelog entry for it - fixes issue #73.
|
|
(where it makes sense)
Also:
- Implemented caching of configuration arrays for smileys, foreign characters and doctypes.
- Implemented cascading-style loading of configuration files (except for library configs, DB and constants.php).
|
|
Signed-off-by: Eric Roberts <eric@cryode.com>
|
|
Signed-off-by: Eric Roberts <eric@cryode.com>
|
|
Signed-off-by: Eric Roberts <eric@cryode.com>
|
|
|
|
|
|
|
|
|
|
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>
|
|
Signed-off-by: Eric Roberts <eric@cryode.com>
|
|
As suggested in issue #2134 & PR #2149
|
|
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>
|
|
|
|
Exact same behavior, but faster. I also think it's more readable.
|
|
|
|
|
|
|
|
|
|
update for Issue #2064 - take 2
|
|
method that returns $this to @return CI_DB_class_name)
|
|
|
|
|
|
Form validation language line keys were not prefixed. They are
now prefixed with 'form_validation_' in order to avoid collisions.
The old keys will still work if a prefixed match is not found, but
are DEPRECATED and will be removed in the next major version.
Also added upgrade notes and changelog entries for the new error
message format from PR #961.
|
|
Signed-off-by: Eric Roberts <eric@cryode.com>
|
|
Conflicts:
system/language/english/form_validation_lang.php
user_guide_src/source/libraries/form_validation.rst
Signed-off-by: Eric Roberts <eric@cryode.com>
|
|
(manually implementing outdated PR #636)
|
|
|
|
|
|
As requested removed useless comment
|
|
This allows developers to create children drivers that are not prefix
with "CI_". This is a nity grity change, however it keeps with the
mindset that class names that start with CI_ are typically overrides of
core classes.
|
|
|
|
(an alternative to PR #1759; partially solves issue #1742)
|
|
Makes it easier to access the data after validation (issue #1208)
|
|
Check for an empty encryption_key shouldn't use strict comparison.
|
|
keep_flashdata accepts array
|
|
|
|
We have file naming conventions and any extension filename needs to match MY_<orig_filename>,
so we don't need to check for lowercase equivalents.
|
|
Signed-off-by: dchill42 <dchill42@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|