PyroCMS v0.9.7.4 - an open-source modular general purpose CMS

[eluser]Phil Sturgeon[/eluser]
BenneX: which language is your primary?

[eluser]Phil Sturgeon[/eluser]
Ok, paths should be working a little better in the bleeding edge copy. All guessed paths will add missing slashes to the start or end of the path, and to the base_url.

Ray, spotted anything else for me yet? hut:

[eluser]BenneX[/eluser]
Sorry, my internet connection was temporary down, cause of bad wether... Now it's still very slow and I'm loading the files from Github with 2 kb/s >_< just a few ours left

My primary language is german, but generally I understand the english language.
The only thing I just need to know is how to upload my changes to github, without destroying the work of an other team-member.

I also need more information about my tasks. Shall I only exclude the hardcoded strings to a language file or have I also to think about the adding, editing, removing and choosing the languages? What's also to do along the language system? maybe there are some more things I can do.

@Yorick Peterse
Thank you very much for your excellent little guide. It helped me very much

greetz

[eluser]ray73864[/eluser]
[quote author="Phil Sturgeon" date="1244590522"]Ok, paths should be working a little better in the bleeding edge copy. All guessed paths will add missing slashes to the start or end of the path, and to the base_url.

Ray, spotted anything else for me yet? hut:[/quote]

Not yet, only woke up about 30mins ago

Will have to grab the latest tagged release (have you done a 0.9.5.4? ), the system is getting better and better though, i am finding it much harder to actually find bugs in the system

[eluser]Phil Sturgeon[/eluser]
No v0.9.5.4 just yet. I'm waiting for you and one other dude to give it the go-ahead before tagging.

Have you seen Yoricks installer? It kicks ass! :-) Would love some testing on that if you could?

[eluser]Yorick Peterse[/eluser]
[quote author="Phil Sturgeon" date="1244590522"]Ok, paths should be working a little better in the bleeding edge copy. All guessed paths will add missing slashes to the start or end of the path, and to the base_url.

Ray, spotted anything else for me yet? hut:[/quote]

*cough* http://www.thebuggenie.com/ *cough*

Much better than GitHub's bugtracker

[eluser]Phil Sturgeon[/eluser]
Is anyone else having trouble with admin page loading in the current bleeding edge? Had two people report the bug and I cannot recreated it in a root install, sub-domain install OR sub-folder install. All using the current code-base...

Apparently admin pages are loading borked, not fully loading and missing assets.

[eluser]Yorick Peterse[/eluser]
[quote author="Phil Sturgeon" date="1244652776"]Is anyone else having trouble with admin page loading in the current bleeding edge? Had two people report the bug and I cannot recreated it in a root install, sub-domain install OR sub-folder install. All using the current code-base...

Apparently admin pages are loading borked, not fully loading and missing assets.[/quote]

No, it's working fine for me.

[eluser]ray73864[/eluser]
I like the installer, but i do have a few problems with it.

Could it be made so that when you download a fresh copy of PyroCMS, the first thing it does is checks to see if a database exists, if one doesn't, then auto-run the installer?

Next up, using WAMPServer, the installer keeps telling me:

The config file could not be written, please chmod PyroCMS's database.php file to 777

Which is a bit tricky since Windows doesn't support that style. I know that wampserver might be a lower use than what this is intended for, but if the installer can be made to work on anything then i think we will be onto a winner.

Oh, and the CMS should check for the presence of a database file and the installer directory, if the database exists and the installer directory is still there, then refuse to let the CMS run.

[eluser]Phil Sturgeon[/eluser]
Good point. Windows does not support chmod but the equivilent of 777 can be set via right clicking and going to properties.

Yorick: I believe the chmod() function should take care of this nicely. It could set the files to 777 and then set them back to 644 afterwards.