I think there is an issue with domain_prefix. I have set this on the domain prefix settings page. I have the latest version of Drupal 6 (6.22):

Domain creation options: *

X Generate tables as defined below
Do not generate any tables

When I set to "Do not generate any tables" there is no time lag during registration. There is about 15 second time delay and it happens in domain_prefix.admin.inc in domain_prefix_form(). Specifically, in the foreach(), starting on line 291.

I only want to generate 1 new table via Domain Prefix - which is the url_alias table, so each user has his own url_alias table. The problem, it seems, is that this foreach on line 291 is iterating through every table and not ignoring all but url_alias.

I stuck this in there: if($table != "url_alias") { continue; } - and it appears to have fixed the time delay.

Is this a bug? Or am I doing something wrong/confused?

Comments

agentrickard’s picture

Priority: Normal » Minor

It's the module trying to do something it was never designed for: prefix tables when used with Domain User (which is what it sounds like you are doing.)

The problem is with using drupal_execute() to trigger the automated build, which actually happens in domain_prefix_domainupdate

Essentially, that code needs a major refactor, so that the table creation sequence is removed from the form processing.

However, I never use the module and it is barely supported. This should get fixed in the D7 version, which I don't intend to maintain. And this bug is edge-case enough that I won't spend any time fixing it for D6.

I'll be happy to review patches, though.

dqd’s picture

Issue summary: View changes
Status: Active » Closed (outdated)

I'll close this issue due to inactivity for 12 years and upcoming EOL of Drupal 7 in January 2025. While the project's version for Drupal 7 will surely keep providing support for security issues and website breaking bug fixes for Drupal 7, we should try to minimize the open issues for Drupal 7 in the queue as much as possible. A big thanks around for the report and all the efforts in here. Feel free to re-open if you can provide a fix or found an additional related problem which increases the issue priority.