Thread

WOaah!!

Nice layout!... I can’t wait to take it for a spin!!

The layout will come with color variations too, black & orange, light blue and greyscale at the moment.

Amazing, keep up the good work dude 😉

Just keeping everyone updated with progress. I have decided to use Assembla for tracking tickets/milestones on this job over my old favourite Unfuddle (thanks to Too Pixel for convincing me a while back).

So PyroCMS will be managed with:

Assembla - Planning
GitHub - Source control

They both integrate nicely too so no duplication of effort. Not sure which will have the wiki but can worry about that junk later.

Follow me on GitHub or Twitter to receive updates on my progress and if anyone fancies helping out with bug testing then I will be importing the current codebase into Git tonight. The code I add tonight will be pre-alpha for a few days so the obvious warnings apply.

Ok not tonight, halo night lasted too long. Tomorrow.

sounds good.

Finally got the code online. However, this should be seen as an initial import and not as a release. Feel free to take a look around, lots of cleaning up will happen tonight and hopefully I can get the database files in order for the v0.9-alpha1 release.

screen shots look amazing!

I will definitely be keeping an eye on this!

doodle

Finally got the code online. However, this should be seen as an initial import and not as a release. Feel free to take a look around, lots of cleaning up will happen tonight and hopefully I can get the database files in order for the v0.9-alpha1 release.

sorry for stuped question , but where can download code ?

http://www.assembla.com/spaces/pyrocms/

There is a tab with a link to the github files.

Sorry I will be making everything a little more obvious later on. Got half tickets done for the alpha1 release tonight.

Download ZIP
Download Tar

Spent most of the evening wrestling with jQuery UI trying to recreate javascript confirm() boxes. Ridiculously complicated! They are in the latest push anyway, even if it is not a perfect final design on the boxes.

of the evening wrestling with jQuery UI trying to recreate javascript confirm() boxes. Ridiculously complicated!

I was looking for the same thing and found a couple ready options:

1. jqModal. Checkout example #6
2. BlockUI.

Thank you for the contrib!
I have try installing the cms under htdocs.
I have this structure folder

-htdocs
  |—pyrocms
    |—public_html

THe php work but the assets folder is not set correctly: i think necessary an .htacess into the pyrocms folder… At this time i have edit the asset helper as

$base_url =$obj->config->item('base_url');

And: at the install you write

6.) Go to your web root, login and make yourself an admin user account.

But for login i use .(JavaScript must be enabled to view this email address) and ...... ?

Thank you

Ahh sorry the password is “password”.

I had always intended this cms to be run from web root as I always use virtual hosts locally and subdomains on servers, never needed to be run anywhere else. Meaning I would have set up http://local.pyrocms/ to point to htdocs/pyrocms/public_html.

Also the reason the asset helper was using / over base_url was due to my assumption of the code being in root, I could cut down on the number of HTTP requests for css/image files. Might need a more flexible option to support both as I understand not everyone will run this from the root.

Other than assets showing funny, any other issues running it out of web root?

Edit: Forgot to say thank you for the feedback. :red:

Why the choice for the apppath directory name public_html, it might confuse people.

You are right, it is a little confusing. It’s a personal choice of mine to put all the app in the web root, then have CI sitting one up from there. Think I should rename the appdir to application or pyrocms?

Edit: Got a potential fix for asset helper. To find the relative root path this crazy bit of code should do it.

$relative_appdir = isset($_SERVER['DOCUMENT_ROOT'])
    ? str_replace( str_replace("\\", "/", $_SERVER['DOCUMENT_ROOT']) , '', str_replace("\\", "/", realpath(APPPATH)) )
    : '';

echo $asset_dir = $relative_appdir .'/assets/';

Could someone check my logic there? It seems about right, on a default CI install that code gave me:

/codeigniter/application/assets/

I basically want to avoid using base_url() as this means you have to create a HTTP connection for each and every file you include, that would be no good for speed at all.