Allows tidier rewrite rules in .htaccess, also negates need for RewriteBase configuration in initial setup.

The logic may need a bit of explaining.

For a request like http://local.host/PIP/class/function/p1/p2 you get the following variables.

$_SERVER['REQUEST_URI'] == '/PIP/class/function/p1/p2' // $request_url
$_SERVER['PHP_SELF']    == '/PIP/index.php'            // $script_url

PHP_SELF gives the same value as SCRIPT_NAME, I think this is the best one to use, but I'm not 100%. See http://stackoverflow.com/questions/279966/php-self-vs-path-info-vs-script-name-vs-request-uri

The $url is built in three stages.

1. Use str_replace to remove index.php from $script_url leaving the path base /PIP/
2. Use preg_replace to remove only the 1st occurrence of /PIP/ from $request_url
3. Trim end slashes as before

This leaves you with only the relevant part of the path string class/function/p1/p2

preg_replace is used to remove only the first occurrence of the base path. This means that urls like http://local.host/PIP/class/function/PIP/p1/p2 are correctly filtered as class/function/PIP/p1/p2 not class/functionp1/p2.

I'm not sure how clear this is in the source. If you think it's read better in some other format, that's fine.

You may also notice my OCD for aligning operators on neighbouring lines, I am taking medication for this.

Removed closing php tags to prevent potential 'Headers already sent' errors. Some people think this is best practice, some don't. I'll leave it up to you to decide whether you'd like to make this change or not.

Gilbert,

I've added a new line of code that allows the controller actions receive any number of arguments. I thought it would be a good one line change that would add some flexibility without bogging anything down. I know you want to keep this as simple as possible, so additions should be done sparingly to keep in the spirit of the framework.

I've also decided to use this project as the base for a framework that I am working on. It is named pep in the spirit of this framework. I restructured it a bit and added themes, templating and language support so far. I also added SQLite for a simple drag and drop database component. Next stuff I'm doing for this project is some authentication and a basic admin section. Feel free to check it out here.

https://github.com/robertabramski/pep

This was intended to just be about adding in phpdoc style comments for everything.

But I also moved the load functions to a separate class so the can be called from within models as well as controllers.

And a few other little bits.

Created folder structure for static content. Moved CSS file from application/view folder to static/css Added .gitignore files to preserve folder structure. Added BASE_URL link to CSS in header.php.

Also, style.css is full of styles, are these from another project?

I downloaded it thinking it may help me understand some basic MVC concepts. -- that is not what happened. Better change the name from PIP to "Frameworks the bad way"

I changed the segment function to use REQUEST_URI from the $_SERVER array. The $_GET['_url'] variable wasn't working for me. I couldn't find any documentation of this variable being in the $_GET array by default. This new function also does an integer check to the variable passed in and returns false if not an integer.

Just some useful functions I've chucked in after playing around with PIP for a recent project.

escapeArray applys mysql_real_escape_string recursively to an array.
to_bool to_date to_time to_datetime convert data types to MySQL compatible strings for use in building queries.

Edited to remove the need for empty index.html files in directories. Used Options -Indexes in .htaccess Added a .gitignore file in /application/plugins/ to preserve folder structure when committed.

Hi, I'm using the framework, I like it because it's simple. I have a problem: What happens if I don't receive a parameter in a function? I selling error:

Fatal error: Uncaught ArgumentCountError: Too few arguments to function Usuario::restablecer(), 0 passed in C:\laragon\www\lidcon\system\pip.php on line 176 and exactly 1 expected

I tried to validate if the variable is defined but still I have the same error

Hi i get this on using PIP "Deprecated: mysql_pconnect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead" how much important is this message? how can i change it to using PDO or mysqli instead? why u don't fix this?

GitHub changed the way Markdown headings are parsed, so this change fixes it.

See bryant1410/readmesfix for more information.

Tackles bryant1410/readmesfix#1

previously when query string parameters were passed it would be considered as the url. Now they can be accessed separately and even upgraded to mysqli