Problem with 2.0.1 environments

[eluser]@li[/eluser]
Thanks for sharing this, whats the fix in CodeIgniter.php?

[eluser]The Wizard[/eluser]
Lıne 51:

Code:

/*
* ------------------------------------------------------
*  Load the framework constants
* ------------------------------------------------------
*/
    if (file_exists(APPPATH.'config/'.ENVIRONMENT.'/constants'.EXT))
    {
        require(APPPATH.'config/'.ENVIRONMENT.'/constants'.EXT);
    }
    else
    {
        require(APPPATH.'config/constants'.EXT);
    }

[eluser]InsiteFX[/eluser]
This was fixed two weeks ago download the newest version from the Reactor!

InsiteFX

[eluser]@li[/eluser]
It isn't fixed, I downloaded the latest reactor release yesterday and in Core/Codeigniter.php, line 51 it says this:

Code:

/*
* ------------------------------------------------------
*  Load the framework constants
* ------------------------------------------------------
*/
    require(APPPATH.'config/constants'.EXT);

I've changed it with the fix given by herrkaleum. Are there any other such lines that have to be changed, e.g with loading route config?

[eluser]troy_mccormick[/eluser]
[quote author="@li" date="1301453670"]It isn't fixed, I downloaded the latest reactor release yesterday and in Core/Codeigniter.php, line 51 it says this:

Code:

/*
* ------------------------------------------------------
*  Load the framework constants
* ------------------------------------------------------
*/
    require(APPPATH.'config/constants'.EXT);

I've changed it with the fix given by herrkaleum. Are there any other such lines that have to be changed, e.g with loading route config?[/quote]

Looks like it's fixed in the repository to me:

https://bitbucket.org/ellislab/codeignit...gniter.php

Was changed back on 3/15...

[eluser]@li[/eluser]
How come the .zip hosted on the website isn't updated with this? That's what I downloaded.

Do any other files have to be updated? the OP had an issue with routes config as well?

[eluser]troy_mccormick[/eluser]
I've been just grabbing the latest version off of BitBucket and haven't run into too many problems doing that. You are also able to view bugs that have been submitted and are being worked on, which I highly recommend a read through.

https://bitbucket.org/ellislab/codeigniter-reactor

[eluser]InsiteFX[/eluser]
This is right from the latest release on Reactor Bitbucket!
And it is also in the version I downloaded.

Code:

/*
* ------------------------------------------------------
*  Load the framework constants
* ------------------------------------------------------
*/
    if (file_exists(APPPATH.'config/'.ENVIRONMENT.'/constants'.EXT))
    {
        require(APPPATH.'config/'.ENVIRONMENT.'/constants'.EXT);
    }
    else
    {
        require(APPPATH.'config/constants'.EXT);
    }

Phil Sturgeon 2 weeks

constants.php will be loaded from the environment specific config folder if…

InsiteFX

[eluser]Madmartigan1[/eluser]
The home page should **absolutely** offer the "core" branch download, at least as an option.

I never had a problem with 2.0, and I've used it ever since it was available, as I'm sure many of you have. Ever since I started using the reactor branch, things started getting hashy.

[eluser]Phil Sturgeon[/eluser]
People are still getting pretty confused about this, but it's not that hard.

There are Core and Reactor, both are available to download from the Downloads page or from BitBucket. If you just go to BitBucket and click "Download" you are most likely getting what is called the "tip" which is the very latest commit at any one time. If you don't understand version management or source control then please stick to downloading from the Downloads page and stay away from BitBucket. People should not be suggesting you go here unless they are pointing you to a specific fix.

Core is just "what EllisLab like to use, Reactor is the version that contains the new features. These features work fine for me and have no problems in any of the applications I implement them to, so so far that has been enough for me to be happy with a feature.

Moving forwards more excessive testing is required, not just from the Reactor team but from the Core team too. That said, Reactor is working perfectly for most of us and often the case is not enough debugging. Many of these "Reactor bugs" are nothing more than user error.