This flag prevents Drupal from rendering the term select element on the following pages:

New term
Edit term
Create / Edit node with standard taxonomy fields

We should prevent this to reduce the core loading overloads when the module is enabled.

The use of Standard / TaxiSelect element will be configurable per type and per vocab on "Create / Edit" node pages, admin pages will use the Standard term select element.

The standard term element will be a clone of the core Drupal standard term element.

The only negative is that this module will be incompatible with "Hierarchical Select Taxonomy", but using "Hierarchical Select" will not be an issue.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Alan D.’s picture

Some memory tests using Devel on "Create page"

No taxonomy
Memory used at: devel_init()=1.64 MB, devel_shutdown()=17.69 MB.

With two taxonomies / 8,380 terms (7 MB Data)

Taxiselect using new API
Memory used at: devel_init()=1.64 MB, devel_shutdown()=17.74 MB.

Standard Taxonomy
Memory used at: devel_init()=1.64 MB, devel_shutdown()=35.17 MB.

Francewhoa’s picture

Wow. Big performance improvement.

What the new API thing? Is it TaxiSelect API or another API?

Alan D.’s picture

The flag taxonomy_override_selector prevents Drupal from generating the list, meaning that Taxiselect has to do all of the dirty work :)

Francewhoa’s picture

@all: If someone else wants to contribute memory usage testing here are 2 large taxonomy files. And a small one for quick test. To download right click on below link then select Save Link As option.
href="http://ccsbcy.ca/_drupal_org_forums/large-taxonomy/vocabulary-large-utf8..."
target="_blank">vocabulary-large-utf8-1.5mb.csv
href="http://ccsbcy.ca/_drupal_org_forums/large-taxonomy/vocabulary-large-utf8..."
target="_blank">vocabulary-large-utf8-20mb.csv
href="http://ccsbcy.ca/_drupal_org_forums/large-taxonomy/vocabulary-small-utf8..."
target="_blank">vocabulary-small-utf8-2kb.csv

File format is UTF-8
3 levels deep

The easiest way that I know of to import large taxonomy files is using the batch feature of 'taxonomy_csv' module version 4.1 or more recent at http://drupal.org/project/taxonomy_csv
Find attached screenshot for module settings.

Note that those links aren't permanent. So if they don't work that's normal.

Alan D.’s picture

Version: 6.x-1.x-dev » 6.x-2.x-dev

K, after redoing this from scratch 5 times I think that the base framework is functional in the new 6.2 branch. Disable and enable the new branch if you do not see the message "Drupal's taxonomy selects are now overridden by TaxiSelect."

Configuration via the admin page for:

a) Vocabs to interact with at the node level
b) Content types at the node level
c) Vocabs on the add/edit admin pages.

Being so pushed for time, this has limited testing.

Alan D.’s picture

Status: Active » Needs review
Francewhoa’s picture

Thanks Alan. I'll try testing next week. Then I'll post my result here.

Francewhoa’s picture

Status: Needs review » Reviewed & tested by the community
FileSize
48.99 KB

Awesome. It works. Memory usage has improved.

Here is my testing result.
Memory usage:
Memory used at: devel_init()=1.24 MB, devel_shutdown()=9.04 MB.

Memory usage as been improved. Now down to 9.04 MB. Reducing load overheads.
With:
-taxiselect-6.x-2.x-dev.tar.gz (September 7, 2009 - 17:28)
-Height taxonomies / 8,380 terms (Each taxonomy with 1048 terms). Created with Devel Generate.
-On "Create page" at /node/add/page
-Fresh Drupal 6.13

Alan D.’s picture

Version: 6.x-2.x-dev » 6.x-2.0-alpha1
Status: Reviewed & tested by the community » Fixed

The alpha release has this feature and currently no known bugs

Two recent empty string bugs were detected and resolved, so use the latest alpha version. Dev could be unstable with new features (if I get the time!!)

Francewhoa’s picture

Thanks Alan. This module is awesome :)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.