hi, do you porting this module to drupal 6.x?
and if you think yes, when do you think to do this?

thank you,
bye bye from italy!

CommentFileSizeAuthor
#25 page_title-coder_warnings.patch12.56 KBmustafau

Comments

nicholasthompson’s picture

Version: 5.x-2.0-alpha4 » 5.x-2.x-dev
Assigned: Supercus » Unassigned
Status: Active » Postponed

I am indeed planning on porting this to D6. I want to get a stable 5.x branch first (pretty much done) and then I can work on a D6 release.

Time frame? I cant guarantee anything unfortunately... However I DO know that 2 large projects at the company I work for (Electric Word) are going to be started early this year and based on D6...

Bye Bye from England ;-)

murz’s picture

Subscribe.

Roxpace’s picture

How is the progress on this now ? If you need any kind of specific help, just ask :)

nicholasthompson’s picture

The progress is basically limited by when we can get Page Title 2.0 out for a final release. The alpha's are pretty close to being done... But I wanna make sure Page Title 2.0 is actually GOOD TO GO rather than just tagging a 1.0 release as ok...

Roxpace’s picture

I understand you and your path to go is logic, I was only asking because it was over one month ago you last time wrote about this and this is a such great module to have in a fully SEO equiped drupal site.

nicholasthompson’s picture

Thanks Roxpace...

To be honest - I think all that will really need playing with is (off the top of my head):
1) The hook_menu (due to D6 updates)
2) The form theming - I've head D6 does some funky theming stuff...

Biggynuff’s picture

Subscribe . . .

After having had well over 30 sites in the top 5 of google for their major search terms, I'm convinced that the html page title is by far the most important element

Serious thanks to Nicholas and other developers for what could just be the single most important Drupal module

vegeneric’s picture

subscribe...

yell0w’s picture

+1 for page title port to Drupal 6

ardee-1’s picture

+1 from me, too!

wayland76’s picture

subscribe (+1)

wayland76’s picture

Just a note; with the new stuff in 2.0, I suspect the views stuff will also need changing, because views change for 6.x as well.

Question (which doesn't belong here, but I don't know where it goes); what do you consider essential before bringing out a beta of 5.x-2.0? Just the bugs labelled for 2.0-alpha5?

nicholasthompson’s picture

Pretty much - I need people to test it and find anything wrong.

I've got it running on http://www.pponline.co.uk/ and everything seems fine... But I'm just one person using it on that site. Others might find things wrong with it based simply on the grounds that they use it SLIGHTLY differently...

Devis’s picture

subscribe

nicholasthompson’s picture

Version: 5.x-2.x-dev » 6.x-1.x-dev
Status: Postponed » Fixed

Ok - due to popular demand, here is Page Title 2 for Drupal 6...
http://drupal.org/node/253981

I've tested it on my dev server and all appeared to work OK - but undoubtedly there will be issues. When you find them can you please open new tickets (or reply in existing appropriate ones).

You still need to add the extra lines of code to the _phptemplate_variables function... This is what my Garland one turned into...

/**
 * Override or insert PHPTemplate variables into the templates.
 */
function phptemplate_preprocess_page(&$vars) {
  $vars['tabs2'] = menu_secondary_local_tasks();

  // Hook into color.module
  if (module_exists('color')) {
    _color_page_alter($vars);
  }
  if (module_exists('page_title')) {
    $vars['head_title'] = page_title_page_get_title();
  }
}

If anyone has any suggestions about how we can remove this step - I'D LOVE to hear it (in a separate issue maybe).

Cheers for all the support guys!

nicholasthompson’s picture

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

Created wrong branch - oopsy!

Supercus’s picture

I can't access to download...

nicholasthompson’s picture

you need to wait for Drupal.org to generate the Tarball which happens twice a day. Alternatively you can check it out of CVS.

Supercus’s picture

I try it and it work perfectly, thank's a lot! great work!
I think that you insert the php code for template.php in the main page of the project so everyone can what to do!

wayland76’s picture

Well, I'm still not seeing it. Do you have to create a dev release or something? Is it showing up when you click the "View all releases" link?

nicholasthompson’s picture

wayland76’s picture

Thanks. I see it now; maybe it only runs once a day or something :).

nicholasthompson’s picture

There is also a known issue with the Project/Release module used here that you have to edit-submit a release node after you've made it to get it to appear on the project page. No idea why though!

Anonymous’s picture

Status: Fixed » Closed (fixed)

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

mustafau’s picture

Category: feature » task
Status: Closed (fixed) » Needs review
StatusFileSize
new12.56 KB

Attached patch eliminates coder.module warnings for 5.x to 6.x upgrade.

wayland76’s picture

mustafau: please open a separate issue for this.

mustafau’s picture

Category: task » feature
Status: Needs review » Closed (fixed)
BioALIEN’s picture

Status: Closed (fixed) » Active

Wanted to open this issue to seek clarification.

Will there be a 6.x-1.x-dev branch release of this module?

I get the feeling this module is starting to become over developed and I liked the simplicity of the 1.x branch.

nicholasthompson’s picture

Status: Active » Closed (fixed)

Why did you reopen this ticket?!

The reason I started at a 2.x branch was to keep the major releases between 5 and 6 in sync. The version 1.x branch was simple built-in token replacement whereas the 2.x branch is integrated with the Token module which allows more dynamic allocation of tokens in the Page title (eg, if you wanted something like the cat path or the node creation date).

If you'd like to discuss this further, please open a new ticket.