Scriptaculous/Prototype Ajax Comes to Drupal

I've committed (an early beta version of) the S/P Ajax module that attempts to create an API for easily adding Scriptaculous and Prototype JavaScript/AJAX functions to your Drupal themes and/or modules. Other than providing a whole lot of PHP functions, this module doesn't do a whole lot on its own. But it does allow for creating animated message divs - you know, the ones that tell you your node was saved or that your submission has an error. Now you can make them flash a little to wake users up.

The first module based on SPAjax.module is called S/P Magic Menus and it does some sought after things with Drupal's menu blocks. First, it uses the Scriptaculous "blind" effect to toggle the display of submenu items - so, for instance, you don't need to view the node/add page just to get to node/add/story, just click "create content" and out pops the node types without reloading the page. You can also remove the menu blocks from the page flow completely and they become draggable "toolbars" (think PhotoShop's tool pallette). What's particularly cool is that when you drag the menu, its position is sent (via ajax) to the server so it STAYS there as you move from page to page. There is also a setting to choose whether you want the menus positioned absolute (they will scroll with the page) or fixed (they will not scroll with the page).

Multi-site selective content sharing? (is this a really dumb way to do this?)

I have a client that is a nationwide restauraunt chain, with probably about 14 locations total. So far, their CMS setup is going great (drupal 4.7 is pretty damn amazing to work with.) However, there's one feature that they ABSOLUTELY insist on having that totally has me stumped though, because it's not something that drupal was really designed for, but now I need to try to hack into it. They need to have a system-wide admin be able to post content across all sites simultaneously. If that's not bad enough, they need to be able to edit any of a number of static pages and have the ability to have that update occur system-wide as well. These are pages like menus, directions, about the restauraunt, etc. and would be individualized to the local restauraunt under normal circumstances, except when corporate deemed in nessesary to make a system wide update.

Aside from reservations I have about usability in a system where local admins are getting their content overwritten by a superadmin, I have no clue what the best way to pull this off would be.

Here's what I've come up with, and it looks like it *should* work, at least for the static pages. Can anyone offer any feedback / validation / suggestions? Maybe there's a much easier way and I'm going about it all wrong? Thanks!

  1. Create all the static page nodes on the various systems. (most of these will be flexinodes because of the structured content they need to store)

Multi Site Deployment Questions

Hello,

I'm evaluating using Drupal for our business needs and I had some questions about the multi site deployment.

I am looking to deploy a large amount of sites (roughly 100) that will each be a sub domain of my main domain. I would like one code base so that upgrades and changes will be easy for all sites. However I need each site to be somewhat independent from each other say look and feel, but share other things such as user rights and content.

_user hook: when does a uid get assigned?

I'm creating a module that needs to know the uid of a new user to update a db table. I've tried placing my SQL call in the 'validate' and 'insert' sections of hook_user, but neither work: in validate I get a uid of 0, in insert I don't get a uid at all.

Any help on this? The life-cycle documentation for many of the hooks with operation arguments is pretty poorly documented. I'm not even sure that $user or $edit is valid in a hook_user 'insert'.

Thanks

Forum settings: how do I set forum posts so they are NOT promoted to frontpage of site.

How do I set up the forums settings so that forum posts are NOT promoted to the frontpage?

Thanks,

ahijado

Differences in .htaccess causing 500 errors?

Hi there,

Can anyone explain the differences between the .htaccess file from 4.7.0beta3 and 4.7.0beta4?

When I initially upgraded to beta4, the .htaccess file starting causing problems with short urls.

The old .htaccess file (v1.67) had the following section in it:

Pages

Subscribe with RSS Subscribe to RSS - Drupal 4.7.x