Drupal 4.7.x

Hi Guys,

Using Blue Marine PHP Template Version. Drupal ver 4.7 recent beta. I am getting this error at my site:

Fatal error: Call to undefined function: format_name() in /home/tidalsound/www/az/themes/engines/phptemplate/phptemplate.engine on line 275

Any idea what this is? How do I fix this?

I cannot get my site backup. I notice if I delete the phptemplate folder under engines I get a partial site back [ I know, based on Drupal.css, I think ].

What is the main use of the 'prepare' op in hook_nodeapi? It's not documented , and i was just wondering what is commonly done during that hook, and when it is fired...

I would like to detect if someone is logged in to my site in the page.tpl.php page.

Similar to the "if (isset($secondary_links))" or "if ($site_slogan)" tags. Any suggestions?

We are currently setting up Drupal for a university society. As such signups need to be restricted to university members, defined as those with a university username (and hence email address).

The way we did this on our home-grown system was to force their username to be their university username, and then we'd email their password to the associated email address, which they'd change when they first logged in.

Hello.. I'm trying to install Drupal 4.7 beta 4 on a test site and the server is running MySQL version 4.1.15 but I've struck upon problems..
It says:

The database type mysql is unsupported. Please use either mysql for MySQL 3.x & 4.0.x databases, mysqli for MySQL 4.1.x+ databases, or pgsql for PostgreSQL databases. The database information is in your settings.php file.

We have developed a patch that is likely to be accepted into Drupal 4.7, http://drupal.org/node/45414. The static file caching patch reduces load on the server in four ways.

1) Database load: Anonymous users are served static pages directly with out contacting the database for session management or other database queries, reducing the anonymous load to 0 and allowing the query cache to be used more effectively for authenticated users.

2) Disk IO load: Pages being served by Apache or a web server will take advantage of the operating systems internal page caching mechanism meaning most popular pages will be served directly from memory and not from disk reducing disk IO latency.

3) PHP CPU load: If the static caching patch is configured much of the Drupal PHP that needs to be interpreted or even loaded load from an Op cache will not be done as Drupal is largely bypassed in serving pages.

4) Apache thread load: Drupal's PHP apache threads are at least 16MB each. Static pages in a directory can be re-directed and served from a separate web server that will use 1M threads for anonymous pages meaning that expensive threads for Drupal can be reserved just for expensive operations.

These results have been validated with a similar file caching patch for Wordpress.com. Please test this patch and help us get this patch into Drupal core. If you are interested in funding this kind of development please contact me.