Official: WCDDL - The DDL Script

[Mr Happy]

Please code the script taking into consideration the new google's penalty. Thanks.

That's a recent searches plugin people added themselves. You don't have to add it.

[JmZ]

A 'search log' is built into v3 which can be outputted as recent searches, but only by your choice.

So if you want to completely avoid the new penalties, don't include it.

As for progress, i'm just doing the admin functionality now, I decided to make it all pretty much AJAX based so the actual admin page remains a single, clean file.

[Mr Happy]

Nice so you know how in V2 you add links to the admin area

$core->admin_links = array_merge($core->admin_links, array('webmaster' => 'Webmaster CP'));

are they going to continue to be reload page or can they have the option of being ajax loaded too?

Not that it matters, just wondering and it would continue the ajax loaded theme.

[JmZ]

It's a db configuration now.

Core::load()->config(array_merge(
     Core::load()->parseConfig('admin_links'),
     array(
           array('someURL', 'SomeText')
     )
); 

Meaning you only need to call that one time, then it is stored in the db unless the user, for some reason, re-alters it (or another mod alters it in a way that removes your changes).

[Mr Happy]

Right so with the admin links and other variables stored in the DB how do you suggest installing or importing mods?
Same idea for adding or modifying tables. Do you suggest mods have an install file run once to make table modifications and load these configs and then delete the install file?

[JmZ]

You could either have an install file, or fetch the config each time and check if your changes still exist. If they don't, make them again.

So an admin module may look like so:

function myAdminPage($go) {
     if($go != 'myadminpage') return false;
}
function myAdminPageInit() {
     if(!Core::load()->config('myConfig')) {
          // check if my config is set, if not, set it
          Core::load()->config('myConfig', 'someValuesWoot');
     }
     $admin = Core::load()->parseConfig('admin_links');
     // Check here if $admin array contains your changes
     // if not, set them
}
Core::load()->hook('AdminHandleContent', 'myAdminPage');
Core::load()->hook('Init', 'myAdminPageInit'); 

Only slight inefficiency there is you run a query per page load.
To make it a bit more efficient you could only run it when the correct _GET['go'] is set.
This way it only runs on pages you need it to run on.

Because the Init hook runs on EVERY page, first thing almost.

[JmZ]

ok forget that I cba with AJAX, im going offtrack here.

*goes in vim, presses '100dd'*

Time to start over.

RELEASE DELAYED BY A DAY

[Mr Happy]

Good idea dropping the ajax. Having ajax will over complicate it and make it harder for less experienced webmasters to code mods and modify it.
The success of the script so far is in it's simplicity. If experienced webmasters want to add fancy ajax themselves they can.

[Jesse]

ok forget that I cba with AJAX, im going offtrack here.

*goes in vim, presses '100dd'*

Time to start over.

RELEASE DELAYED BY A DAY

cause I told you to delete some code earlier?

[JmZ]

Haha

It's because I implemented 100 lines of JS for AJAX requests and what not, but decided to scrap it and make it all standard instead of AJAX.

Now the admin page is way cleaner.