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

[eluser]got 2 doodle[/eluser]
@Yorick

You might want to check out these facebook groups

I hate internet explorer in all its forms 1096 members

and

I hate internet explorer 474 members

I feel your pain, unfortunately IE8 is also a piece of crap

doodle

[eluser]Yorick Peterse[/eluser]
[quote author="got 2 doodle" date="1246744703"]@Yorick

You might want to check out these facebook groups

I hate internet explorer in all its forms 1096 members

and

I hate internet explorer 474 members

I feel your pain, unfortunately IE8 is also a piece of crap

doodle[/quote]

Yes, IE8 sucks too, but atleast it passes the Acid 2 test, even though that test is already 4 years old.

[eluser]doccer[/eluser]
First of all I like the name.
And I like the architecture so far. It seems to be client friendly where EE (I feel) is lacking.
Any way after it took my 3 hours to install properly because godaddy needs a querystring to make ci work, I found a error and posted it on the github. Basically there is an anchor issue with the admin sidebar nav that causes ajaxify to think the page doesnt exist so when I removed the site_url() method from the href for the links it work like it should. Dont know if that was meant to be there or what.

[eluser]Phil Sturgeon[/eluser]
[quote author="doccer" date="1246795953"]First of all I like the name.
And I like the architecture so far. It seems to be client friendly where EE (I feel) is lacking.
Any way after it took my 3 hours to install properly because godaddy needs a querystring to make ci work, I found a error and posted it on the github. Basically there is an anchor issue with the admin sidebar nav that causes ajaxify to think the page doesnt exist so when I removed the site_url() method from the href for the links it work like it should. Dont know if that was meant to be there or what.[/quote]

I am assuming you changed this:

Code:

<a href="&lt;?= site_url('admin/'.$admin_module['slug']); ?&gt;">

to something similar to:

Code:

<a href="&lt;?= '/admin/'.$admin_module['slug']; ?&gt;">

Problem with doing that is that if your installation is anywhere other than the web root it will fail to work. Change it to:

Code:

<a href="&lt;?= BASE_URI . 'admin/' . $admin_module['slug']; ?&gt;">

That work ok?

[eluser]BenneX[/eluser]
Hey guys, while I was trying to sleep yesterday I've got an damn nice idea about the template issue.
It's not very easy to explain it in english, so I'll give you a little example and hope you'll understand what I mean.

There aren't many different ways to display the content. There are boxes, tables, paragraphs, lists, code etc.
That means there have to be only a default of each one and the possibility to extend them or to create additional ones. I'll give a a little example - the table.

The template looks like something like that and is stored at themes/theme_name/parts/table_default.php

Code:

<!-- TABLE begin -->
    {TABLE_HEADLINE}
    {TABLE_OPEN}
        {TABLE_CONTENT}
    {TABLE_CLOSE}
<!--TABLE end -->

<!-- TABLE_OPEN begin -->
    <table border="0" cellpadding="0" cellspacing="0" {TABLE_PARAMS}>
&lt;!-- TABLE_OPEN end --&gt;

&lt;!-- TABLE_CLOSE begin --&gt;
    </table>
&lt;!-- TABLE_CLOSE end --&gt;

&lt;!-- TABLE_ROW_FIRST begin --&gt;
    <tr class="first_row">{ROW_FIRST_CONTENT}</tr>
&lt;!-- TABLE_ROW_FIRST end --&gt;

&lt;!-- TABLE_ROW begin --&gt;
    <tr>{ROW_CONTENT}</tr>
&lt;!-- TABLE_ROW end --&gt;

&lt;!-- TABLE_ROW_LAST begin --&gt;
    <tr class="last_row">{ROW_LAST_CONTENT}</tr>
&lt;!-- TABLE_ROW_LAST end --&gt;

&lt;!-- TABLE_COL_FIRST begin --&gt;
    <td class="first_col">{COL_FIRST_CONTENT}</td>
&lt;!-- TABLE_COL_FIRST end --&gt;
        
&lt;!-- TABLE_COL begin --&gt;
    <td>{COL_CONTENT}</td>
&lt;!-- TABLE_COL end --&gt;

&lt;!-- TABLE_COL_LAST begin --&gt;
    <td class="last_row">{COL_LAST_CONTENT}</td>
&lt;!-- TABLE_COL_LAST end --&gt;

&lt;!-- TABLE_HEADLINE begin --&gt;
    <h3>{TABLE_HEADLINE_CONTENT}</h3>
&lt;!-- TABLE_HEADLINE end --&gt;

With a call of a function like <?=print_table($data);?> the table will be built with the given data and if theres an additional param like $tmpl_name it could be possible to load an own template like table_mytable.php to allow an other output If then it is also mudular - that means it searches first in the modules folder, then in the application folder for the template the building of templates would be very modular
Sure, it's not pretty well explained, but I hope the sense is clear ^^ If there some questions I'll try to answer them as well as possible =)

[eluser]Yorick Peterse[/eluser]
The widget specification has to wait, I spent too much time trying to think of a decent partial cache system as explained here : http://ellislab.com/forums/viewthread/122112/

I'll see if I can write the spec tomorrow or Tuesday.

[eluser]doccer[/eluser]
[quote author="Phil Sturgeon" date="1246818024"][quote author="doccer" date="1246795953"]First of all I like the name.
And I like the architecture so far. It seems to be client friendly where EE (I feel) is lacking.
Any way after it took my 3 hours to install properly because godaddy needs a querystring to make ci work, I found a error and posted it on the github. Basically there is an anchor issue with the admin sidebar nav that causes ajaxify to think the page doesnt exist so when I removed the site_url() method from the href for the links it work like it should. Dont know if that was meant to be there or what.[/quote]

I am assuming you changed this:

Code:

<a href="&lt;?= site_url('admin/'.$admin_module['slug']); ?&gt;">

to something similar to:

Code:

<a href="&lt;?= '/admin/'.$admin_module['slug']; ?&gt;">

Problem with doing that is that if your installation is anywhere other than the web root it will fail to work. Change it to:

Code:

<a href="&lt;?= BASE_URI . 'admin/' . $admin_module['slug']; ?&gt;">

That work ok?[/quote]


Nevermind. It had everything to to with godaddy. After I put the whole environment on localhost there was no longer an issue. Ive decided to stop using godaddy for this purpose. I used a couple of routes in the .htaccess and it still didnt help. Im beginning to think godaddy really isnt for developers.

[eluser]Phil Sturgeon[/eluser]
Ok well if this pops up again i'll have a go at fixing it. It would probably involve modifying AJAXify to not use full domain paths but I don't really want to do that.

Another option is to have AJAXify disabled by default then only enabled by those who know what they are up to.

[eluser]Phil Sturgeon[/eluser]
Forgot to mention, tonight I will be working on making the rest of the control panel multi-lingual. That includes the module titles, descriptions, side-bar and even the slogan in the logo.

[eluser]Yorick Peterse[/eluser]
[quote author="Phil Sturgeon" date="1246887504"]Forgot to mention, tonight I will be working on making the rest of the control panel multi-lingual. That includes the module titles, descriptions, side-bar and even the slogan in the logo.[/quote]

You still need to replace the logo with the one I made