By m3avrck on

Just in time for DrupalCon 2006, Vancouver, the Drupal development team is pleased to announce the fourth beta release of Drupal 4.7.0! It is available for immediate download at http://drupal.org/files/projects/drupal-4.7.0-beta4.tar.gz. This beta release is hopefully the final beta release for Drupal 4.7.0 and marks a significant improvement in the Drupal 4.7.0 codebase. Since beta 3, over 120 bugs have been fixed, bringing the total to nearly 300 bugs fixed since the first beta release. All of these changes are detailed in the changelog. However, there are still more bugs to be found, reported and fixed before a release candidate can be made. The good news is that, with your help, we can release Drupal 4.7.0 RC1 much sooner!

Here are some ways that you can help out and allow us to release Drupal 4.7.0 RC1 sooner:

  1. Download Drupal 4.7.0 beta 4 and install it on a test platform. You can use the development module to quickly populate an empty database with sample data or you can upgrade an existing Drupal 4.6 database.
  2. Get your users to participate on a test site. We've found the best way to discover new bugs is for many people to try many different things with the Drupal site. You may find bugs by looking through the log files as well.
  3. Participate in the Drupal bug hunt. Prizes are awarded to the people who find the most bugs!
  4. Go to the patch queue and review some of the latest patches.
  5. Fix bugs! You can learn a lot about the Drupal system by fixing the bugs others find. You can ask questions and work on debugging with other Drupal developers on our IRC channel, #drupal on the irc.freenode.net IRC network. They're busy fixing bugs too, but many, if not most, are willing to give pointers and assist anyone who wants to help!

Release notes

  • Important database changes have been made in this release. If you are upgrading, make sure to run the database upgrade script. Instructions for installing or upgrading Drupal can be found in INSTALL.txt or UPGRADE.txt, as well as the handbook.
  • As with anything still in development, take precautions with your data before upgrading.
⋅ Categories: Drupal 4.7.x

Comments

Gurpartap Singh’s picture

Gurpartap Singh commented

Just little more closer to final released. Hurry up guyz i am holding my breadth! lol but security more prior haha. thanks a lot! just a suggestion: have an option to configure block title display (toggle show/hide) and block displayed on access control profile basis. maybe if anyone can build separate module for this?

thanks

jasonwhat’s picture

jasonwhat commented

At what point did what was in CVS become beta 4? What I mean by that is that I assume 4.7 beta 4 is a snapshot of CVS at some point in time, so when did that snapshot occur. I upgraded to CVS about a week ago, would switching to beta 4 today be "downgrading" or "upgrading?" What if someone upgraded to CVS yesterday?

killes@www.drop.org’s picture

killes@www.drop.org commented

I think that Dries took what was in cvs shortly before he made this post and labelled it as beta 4.
--
Drupal services
My Drupal services

--
Drupal services
My Drupal services

Gunnar Langemark’s picture

Gunnar Langemark commented

Gunnar Langemark
http://www.langemark.com

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

Here is an issue list

Drupal itself
Versions:4.7.0-beta1/2/3/4 and cvs
Componenets: all
Categories: bugs, tasks, feature requests
Priorities: Critical
Status: active, patch(anything), fixed

This is the group that should either be fixed or recategorized if necessary (many "normal" bugs are in the "critical" priority because "critical" was the default for a while).

It's possible 4.7.0 will ship with open issues from this list if they are in the list erroneously or only show up sometimes or the like, but this is the group that needs attention.

It's fun to watch the number of bugs/pages change over time. This issue list is currently 121 issues long (just onto the 7th page).

If you remove the "fixed" items: 73 issues.

Both numbers as of 26-January.
--
Knaddison Family Blog

--
Morris Animal Foundation

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

list of issues:

  • January 26: 121 issues
  • February 13: 84 issues

list (minus fixed items)

  • January 26: 73 issues
  • February 13: 64 issues

This does not take into account any new bugs created during that time frame, so the truth is that more bugs have been fixed/triaged than this simple listing shows.

--
Knaddison Family Blog

--
Morris Animal Foundation

enthusaroo’s picture

enthusaroo commented

I've never upgraded from a Drupal beta release before. I'm currently using Drupl 4.7 Beta 3. How can I upgrade to Beta 4 without losing any data? Is there anything in the SQL tables that needs to be added? Can I simply copy over the files that are already in my Drupal directory?

Any insight from a knowleadgeable person is much appreciated.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

loveacrossborders - it is mostly very possible, but of course "make a backup" ;)

From the announcement:

installing or upgrading Drupal can be found in INSTALL.txt or UPGRADE.txt

http://cvs.drupal.org/viewcvs/drupal/drupal/INSTALL.txt?rev=1.26&view=ma...
http://cvs.drupal.org/viewcvs/drupal/drupal/UPGRADE.txt?rev=1.2&view=markup

What questions do you have that are not answered in those documents?

--
Knaddison Family Blog

--
Morris Animal Foundation

enthusaroo’s picture

enthusaroo commented

Excellent!! The upgrade went without a hitch. I love the graphic interface of the upgrade page. Good job, fellas!

kecinzer’s picture

kecinzer commented

Well done.
Finaly mysql set correct charset.

introfini’s picture

introfini commented

Yes, that was a mega issue for me.

Thanks,
introfini

José Fernandes
Bloomidea

yched’s picture

yched commented

the 4.7b3 release contains drupal.css vesion 1.138 while the version in HEAD is 1.132 ??

Rewted’s picture

Rewted commented

The instructions say:

3. Remove all the old Drupal files then unpack the new Drupal
files into the directory that you run Drupal from.

I assume this means delete all old data and replace with the new install, right? I've done that and edited 'sites/default/settings.php', then can the update and got the following errors:

Warning: Illegal mix of collations (utf8_general_ci,COERCIBLE) and (latin1_swedish_ci,IMPLICIT) for operation 'like' query: SELECT * FROM access WHERE status = 1 AND type = 'host' AND LOWER('myIPaddress') LIKE LOWER(mask) in /var/www/mydomain.com/beta4/includes/database.mysql.inc on line 124

Warning: Illegal mix of collations (utf8_general_ci,COERCIBLE) and (latin1_swedish_ci,IMPLICIT) for operation 'like' query: SELECT * FROM access WHERE status = 0 AND type = 'host' AND LOWER('myIPaddress') LIKE LOWER(mask) in /var/www/mydomain.com/beta4/includes/database.mysql.inc on line 124

and then...


warning: Cannot modify header information - headers already sent by (output started at /var/www/mydomain.com/beta4/includes/database.mysql.inc:124) in /var/www/mydomain.com/beta4/includes/common.inc on line 143.
warning: Cannot modify header information - headers already sent by (output started at /var/www/mydomain.com/beta4/includes/database.mysql.inc:124) in /var/www/mydomain.com/beta4/includes/common.inc on line 143.

kzeng’s picture

kzeng commented

I got the same problem when I attempted to update drupal from beta3 to beta4.

--------------------------
http://www.kzeng.info

Rewted’s picture

Rewted commented

I too am going from beta3 to beta4.

kzeng’s picture

kzeng commented

but it does not affect my updating process. Although I got the above warning message, I succeeded in completing update and now my test website fucntions well.

--------------------------
http://www.kzeng.info

Rewted’s picture

Rewted commented

Mine did too... since i'm just testing, i had nothing to loose and proceeded. All seems well, except those errors.

ponkarthik’s picture

ponkarthik commented

Hi,

I am also getting same error after upgrading from beta 3 to beta 4. Any solutions ?

Karthik

rays’s picture

rays commented

I also received the same error and was able to correct it. There may be a more elegant approach, but this worked for me as my data bases only contained test data.

1) With PhpMyAdmin delete your beta 3 database.
2) Use PhpMyAdmin to create a new beta 4 database and be sure to specify utf8_general_ci as the collation.
3) load your tables as required during normal installation.

Hope this helps.

Ray
sulsh.com

ponkarthik’s picture

ponkarthik commented

I ran the update script again. It corrected a lot of tables - ALTER statments. And the error got rectified.

Thanks

Karthik

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

There are several solutions posted in this issue which tracks the problem:
http://drupal.org/node/46934

--
Knaddison Family Blog

--
Morris Animal Foundation

greg_y’s picture

greg_y commented

I got the same message upgrading from a hosted 4.6.3 database to 4.7 CVS as of 2006-02-12.

What worked for me was exporting the database using phpMyAdmin, but under the Structure settings, set "SQL export compatability" to MySQL40. This has the effect of removing “DEFAULT CHARSET=latin1” from many of the CREATE TABLE statements in the export file. When I imported this cleansed version into my new empty database, the subsequent upgrade worked flawlessly.

I will cross post this in http://drupal.org/node/46424 and http://drupal.org/node/46934 in case it helps anyone else.

thinker’s picture

thinker commented

Download Drupal 4.7.0 beta 4 and install it on a test platform. You can use the development module to quickly populate an empty database

I downloaded 4.7.0 beta 4 and the suggested devel module.
I enabled the devel module under the menu administer->modules.

However, when I clicked the menu administer->settings->devel, I got a blank page.

The error_log reported that:

PHP Fatal error: Call to undefined function: form_select() in /var/www/html/modules/contrib/devel/devel.module on line 259

I wonder whether this is caused by the current devel module itself as its version is 4.6.0, or something else.

If the error is caused by the incompatible version of the devle module, please either take the suggestion off or make it clear. Or add more detailed comments to explain how to deal with such errors.

Thanks,

rbrooks00’s picture

rbrooks00 commented

For the most part 4.6 modules aren't going to work in 4.7 because of the forms API change. To run the devel module you are going to need to download the CVS version.

============================================
BuyBlue.org

atticus’s picture

atticus commented

Thanks, guys!

Upgrade went smoothly on my test site. Haven't updating my production site yet, but I do like to keep up on progress with 4.7.

Looks fantastic!

Best,
Brent
Wanderings.net

alexis’s picture

alexis commented

Hi guys, congratulations, each day we are nearer to final 4.7.

I'm currently working in two projects using CVS, I just did a "cvs update -dP" in one of the sites (which I updated like 4 days ago) and everything went ok. The other site, which was created from scratch yesterday, seemed to be already using the new database structure and it's working fine too.

I'm sure I will be finding some bugs in days to come and will submit them or do my best to fix.

Regards!

Alexis Bellido - Ventanazul web solutions

TurboChef’s picture

TurboChef commented

As a true Drupal beginner, I'd like to thank everyone who has put so much work into these releases. I am just learning Drupal, and don't have any programming experience, otherwise I wish I could help code.

I did notice one thing immediately, though. Upon creating the first user, then immediately changing the User 1 password and clicking submit, I got the following error:

Type php
Date Thursday, January 26, 2006 - 15:59
User IT
Location /?q=user/1/edit
Referrer http://vm.turbochef.com/?q=user/1/edit
Message Missing argument 1 for password_confirm_validate() in D:\Intranet\includes\form.inc on line 595.
Severity error
Hostname 192.168.10.101

I noticed that some patches were commited to form for the Beta4 release, and I'm sorry I don't know how to submit a bug. Is this something I've done or should I blow it all away and try again?

Thanks,

John @ TurboChef

UPDATE: I deleted all files, deleted the DB, reinstalled everything, created the first user, changed the password on that screen after it is created, and got the same error:

* warning: array_merge() [function.array-merge]: Argument #2 is not an array in D:\Intranet\includes\form.inc on line 180.
* warning: Missing argument 1 for password_confirm_validate() in D:\Intranet\includes\form.inc on line 595.

So I guess I need to read up on how to submit bugs on the site. Sorry to leave this in a comment.

lunatix’s picture

lunatix commented

To fix this quick and dirty:

Change line 180 in /includes/form.inc from:
$args = array_merge(array($elements), $args);

into
$args = array_merge(array($elements), array($args));

This removes the error!

Note 1: I have no experience in drupal development, just php hacking.
Note 2: This is NOT an official fix!!

a-t’s picture

a-t commented

Thanks for an explanation...

-----
My T.Reader 1.0.2

lunatix’s picture

lunatix commented

I don't have one.

I just tried something and it worked :-)
That's why I said: this in no official fix!

JHBrewer’s picture

JHBrewer commented

Thanks for the fix, however dirty. It's a little worrisome that a bug so immediately disabling as this one should still be present in the tar file I just downloaded and installed today, ten days after it (this bug) was reported. Minor glitches don't need immediate attention, but stuff like this gives a very bad first impression. Maybe I shouldn't be using a Beta...

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

still be present in the tar file I just downloaded and installed today, ten days after it (this bug) was reported.

The tar file is not updated with any fixes. No matter how many bugs are fixed or security holes are found, drupal-4.7.0-beta4.tar.gz will always contain that exact set of files and bugs. There are updates going into the CVS server (lots of them, even!) and I believe this bug is probably fixed there but I'm not 100% certain.

Maybe I shouldn't be using a Beta...

I think everyone should be using Beta on a test server or in a place where they don't mind having some problems. Betas are guaranteed to have problems - sometimes people will make funny warnings about them and how they will "eat babies". But it is important to test it in live (or pseudo-live) situations to find the bugs and fix them

Since it was released, more than 40 issues have been fixed or cleaned from the issue list I posted below. It's pretty exciting!

--
Knaddison Family Blog

--
Morris Animal Foundation

gboudreau’s picture

gboudreau commented

A probably 'cleaner' fix would be:

In system.module:
change
'#validate' => array('password_confirm_validate' => ''),
to
'#validate' => array('password_confirm_validate' => array()),

- Guillaume Boudreau

gorm_mrog’s picture

gorm_mrog commented

Nice to get going!

jakeg’s picture

jakeg commented

Upgrade went well and now working on a live multi-site installation.

One usability suggestion I have is to add helper text to the pre-selected version number to begin updates from on update.php. I've rolled a simple patch ready for review/committing at http://drupal.org/node/46680 . Please +1 the patch if you think its a good idea/the code is good.

I think this will help a lot of users.

Also, it would be good to see this patch (http://drupal.org/node/45098) in 4.7, which enables e.g. when on home page, the primary link to home page to be marked as 'active'.

kybber’s picture

kybber commented

The upgrade from 4.7.0-beta3 to beta 4 seemed to work fine until i noticed
that the Norwegian characters æ, ø and å had been messed up. The
translations were:
æ -> æ
ø -> ø
å -> Ã¥
Norwegian characters still work as expected, and there is no problem editing
these messed-up characters back to what they were originally. Except it is a
big job ;)

I'm guessing this was related to the UTF-8 update? If so, then this problem is
probably not going to happen again for all future upgrades, since you'll be
sticking with UTF-8, is that correct?

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

Makes sense to me - too bad it screwed up those characters in this update, though :(

--
Knaddison Family Blog

--
Morris Animal Foundation

killes@www.drop.org’s picture

killes@www.drop.org commented

Drupal has been using utf-8 for a while now. But only recently we tell MySQL that we do that. Before that we simple stored it without telling. the database conversion might have failed for you. Please file a bug report with a detailed description of what you did and which version of MySQL you have been using.
--
Drupal services
My Drupal services

--
Drupal services
My Drupal services

tangibre’s picture

tangibre commented

... along with the text following it.

I have been looking forward to this update, since I hoped that some problematic character encodings related to Norwegian characters should be solved. I have converted my site and database from a Post-nuke site to Drupal. I haven't figured out how to avoid the messed up characters without manually changing them. I have been too lazy to yet change all my text. When I ran the update.php to update from b3 to b4 the remaining strange faulty characters where removed along with the preceding text.

Any suggestions?

Luckily I have a backup. I am happy that

killes@www.drop.org’s picture

killes@www.drop.org commented

Take an SQL dump, check the encoding, then convert to UTF-8 using recode or iconv. Create empty database with correct collation, import.
--
Drupal services
My Drupal services

--
Drupal services
My Drupal services

osherl’s picture

osherl commented

I get the following error in a new installation after I created my first user ID and tried to change the password in the subsequent screen:

warning: array_merge() [function.array-merge]: Argument #2 is not an array in C:\xampp\htdocs\drupal47\includes\form.inc on line 180.
warning: Missing argument 1 for password_confirm_validate() in C:\xampp\htdocs\drupal47\includes\form.inc on line 595.

Laszlo

rbrooks00’s picture

rbrooks00 commented

That is a PHP5 compatibility bug I believe. I'd submit it to issue tracking so someone can fix it, as show further up in the thread the value needs to be cast as an array. PHP 5 is picky about this for some reason when using the array_merge function.

============================================
BuyBlue.org

robertDouglass’s picture

robertDouglass commented

I want to track it.

- Robert Douglass

-----
My Drupal book: Building Online Communities with Drupal, phpBB and WordPress

gboudreau’s picture

gboudreau commented

See my comment above.

- Guillaume Boudreau

subversion-1’s picture

subversion-1 commented

In my logs after testing comments:

You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'FROM node WHERE node_comment_statistics.nid = node.nid AND node.nid = 14' at line 1 query: UPDATE node_comment_statistics SET comment_count = 0, last_comment_timestamp = created, last_comment_name = '', last_comment_uid = uid FROM node WHERE node_comment_statistics.nid = node.nid AND node.nid = 14 in /www/nerdnet/includes/database.mysql.inc on line 124.

Any takers?

BlueRonin’s picture

BlueRonin commented

I get a similar error when deleting comments. PHP 4.4.2 and MySql.

user warning: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'FROM node WHERE node_comment_statistics.nid = node.nid AND node query: UPDATE node_comment_statistics SET comment_count = 0, last_comment_timestamp = created, last_comment_name = '', last_comment_uid = uid FROM node WHERE node_comment_statistics.nid = node.nid AND node.nid = 1 in /path/to/site/includes/database.mysql.inc on line 124.

holger’s picture

holger commented

I updated my little drupal experience http://cms.stnetwork.de from 4.7. beta 3 to 4.7.beta 4 and I want to say *Thank you* to the Drupal Community for this great work.
The updating processed without any error :-)

Only 1 question: If i go to /user/help#drupal the *#* converts to this uri http://cms.stnetwork.de/user/help%23drupal

Do you know why?

with kind regards, holger

www.ebec.net | www.stnetwork.de

toemaz’s picture

toemaz commented

Might be the apache mod_rewrite issue... but I'm not sure.

netbjarne’s picture

netbjarne commented

Great! The work on drupal 4.7 really has gained momentum the last months - I'm looking forward to see the final results...

I'm wondering a bit though, why the unaligned search block issue has not been addressed.

I have submitted (my first ever) patch during beta 2, and there's probably a million good reasons it didn't make its way into beta 3 or 4 - just, nobody told me.

Now, I recognize that this issue is a itsy bitsy tiny issue, but I find, that its a very nice exercise for getting to know all this CVS patch submission stuff, that imho does seem a bit daunting at first.

If anyone would like to follow up on the issue, heres the link:
http://drupal.org/node/41512

Kind regards
Bjarne, testing drupal 4.7 beta 4 at http://drupaldanmark.dk/

akor’s picture

akor commented

Hi,

From changelog:

added the PHPTemplate theme engine and removed the Xtemplate engine.

Can I ask about reason for this step? Creating themes for phptemplate engine is a terrible. :(

--
Alexei A. Korolev
http://www.akorsoft.com

robertDouglass’s picture

robertDouglass commented

I think PHPTemplate is very easy to use and super-powerful. What don't you like about it?

- Robert Douglass

-----
My Drupal book: Building Online Communities with Drupal, phpBB and WordPress

lekei’s picture

lekei commented

I have been attempting to convert any of my sites that copyright material from phpTemplate to Xtemplate to meet the license requirements. It is not easy.

Will Xtemplate be kept current with 4.7? Should I use Smarty?

robertDouglass’s picture

robertDouglass commented

Why do you feel it is necessary to not use phpTemplate due to copyright issues?

- Robert Douglass

-----
My Drupal book: Building Online Communities with Drupal, phpBB and WordPress

killes@www.drop.org’s picture

killes@www.drop.org commented

He believes that as the templates have to be GPLed, he isn't able to use copyrighted materials in them. Or at least that is what I think he believes. More can be found here:
http://drupal.org/node/37504
--
Drupal services
My Drupal services

--
Drupal services
My Drupal services

xand’s picture

xand commented

He believes that each template designed and released for public use on drupal.org:

1) is considered to be code, because of the way phptemplate works (i.e. the template contains php, so the template is considered to be code);

2) is forced to be licensed under the GPL, because Drupal itself is GPL licensed, and the "creeping effect" of GPL; and

3) cannot contain any copyrighted code, because the GPL licence will remove the copyright.

Provided that he's right about point 1, points 2 and 3 necessarily follow. From what has been said about templates created under phptemplate, it sounds like 1 is accurate, because a template written to work with phptemplate is semantically identical to a piece of code.

---

PS: Perhaps I should also say that this should not be a problem for most people. If you have already decided to contribute, it should not really matter that you lose copyright to the work.

Also, if you never release the work for public use there is no implication.You can use whatever you please in the theme and you will not lose copyright.

However, the specific set of people for whom this could be overly onerous are those designers who create templates for others. Because gpl licensed works which are distributed must include source code, it is potentially a breach if a designer obfuscates the theme delivered in any way. If it also not possible for the designer to prevent his work being distributed by making the client sign an NDA or something similar, becuase the terms of the GPL would make all of these ineffective.

killes@www.drop.org’s picture

killes@www.drop.org commented

I think this is pretty much off topic for this thread, can we move elsewhere?
--
Drupal services
My Drupal services

--
Drupal services
My Drupal services

xand’s picture

xand commented

XTemplate has not been changed for a very long time.

I believe the version in 4.7 and 4.5 (and even before 4.5) is the same. Please check.

drewish’s picture

drewish commented

I've got a patch to update XTemplate to 4.7: http://drupal.org/node/58803

KimVette’s picture

KimVette commented

Try sitting a graphic designer down with PHPTemplate and GoLive sometime. You'll INSTANTLY see the value of Xtemplate.

Removing Xtemplate is a stupid move, IMHO. Speed of implementation was one of Drupal's greatest strengths, and now that's going to be going away.

kbahey’s picture

kbahey commented

Did you see the step by step Guide to Converting CSS HTML design to PHPtemplate?
--
Drupal development and customization: 2bits.com
Personal: Baheyeldin.com

--
Drupal performance tuning and optimization, hosting, development, and consulting: 2bits.com, Inc. and Twitter at: @2bits
Personal blog: Ba

sepeck’s picture

sepeck commented

Oddly enough, you are still welcome to download XTemplate and continue using it's limited and inflexible capabilities to you or your designers hearts content.

That's the value and strength of Drupal's having multiple theme engines.

-sp
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

styro’s picture

styro commented

Try sitting a graphic designer down with PHPTemplate and GoLive sometime.

Well, I've sat our designer down with PHPTemplate and JEdit with great results even though she doesn't really know much about PHP (yet).

IMO if your graphic designer doesn't know how to write HTML/CSS, they should just stick to handing you a mockup done in Photoshop or something. If I was being extra argumentative I'd probably rant about a designer that isn't willing to learn HTML/CSS should probably just stay away from web stuff anyway.

Removing Xtemplate is a stupid move, IMHO. Speed of implementation was one of Drupal's greatest strengths, and now that's going to be going away.

It's not like it has been banned or anything. It took less than 30 seconds to install PHPTemplate in Drupal 4.6. Would the extra 30 seconds to install Xtemplate in 4.7 really slow down your implementations that much?

--
Anton

StevenSokulski’s picture

StevenSokulski commented

I am a Drupal beginner and a designer and abandoned all attempts at using XTemplate because I figured why waste my time learning a lower level interface when i could just get right at the code that will let me do whatever I want.

Could be compared to using Photoshop Elements versus Standard. Why waste your time with Elements quirks when you could just do everything you need in Standard?

NaX’s picture

NaX commented

PHPTemplate is far more flexible and if I remember correctly it is much faster on high load sites. If you don't know much about php you need to spend some time with the handbooks and use a theme like Box_grey to learn. I know a bit of php and found it easier than Xtemplate.

akor’s picture

akor commented

Well, I have no problem with php :) I just don't see easy way to convertation html template to phptemplate. I found Xtemplate more suitable in this way.

--
Alexei A. Korolev
http://www.akorsoft.com

NaX’s picture

NaX commented

Maybe you should compare the XTemplate Bluemarine that comes with 4.6 with the PHPTemplate Bluemarine in the downloads section.

Maybe that will give you some idea of how to convert your templates.

sepeck’s picture

sepeck commented

xTemplate was also found to have issues with php5

-sp
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

kbahey’s picture

kbahey commented

Here is a step by step guide on converting an HTML/CSS design to PHPTemplate.
--
Drupal development and customization: 2bits.com
Personal: Baheyeldin.com

--
Drupal performance tuning and optimization, hosting, development, and consulting: 2bits.com, Inc. and Twitter at: @2bits
Personal blog: Ba

KimVette’s picture

KimVette commented

Yes! Please explain why it was removed!

If performance is a concern, why not make the PHPTemplate the default, but leave the Xtemplate engine in place as an option and let US decide whether or not we can deal with the performance penalty?

killes@www.drop.org’s picture

killes@www.drop.org commented

I think the main reason for removal was that it had problems with php 5 which nobody was interested in fixing. If somebody wants to maintain the engine in controb, he is more than welcome.
--
Drupal services
My Drupal services

--
Drupal services
My Drupal services

drewish’s picture

drewish commented

XTemplate is now a contrib module, I mentioned up thread, it's being updated to 4.7. Please review the patch.

jedbro’s picture

jedbro commented

Hi, first off I have to applaud you for 4.7 It rocks!

On issue I have found is that the API method getUsersBlogs is broken. It's only returning a blank array as seen below.

Previous version of drupal work fine.

<?xml version="1.0"?> <methodResponse>  <params>  <param>  <value><array><data> </data></array></value>  </param>  </params> </methodResponse>

Thanks
-Jed

toma’s picture

toma commented

I just update for beta 4 , check out

www.drupaldemo.org

Free Webmaster Directory
http://www.wdirectory.net

aikenben’s picture

aikenben commented

When I try to preview a comment about to be posted, I get a red error box that pops up at the top of the preview page noting a "Validation Error." If I post the comment, it posts fine. This is on a clean Beta 4 install.

Before when I tried updating from CVS to Beta 4, I had a similar problem, except I couldn't get it to post... just constant Validation Errors on every attempt.

Any ideas?

aikenben’s picture

aikenben commented

Seems like the same thing is a problem on Drupaldemo.org... :(

______’s picture

______ commented

Beta 4 was giving us all sorts of problems with comments. Installing the latest CVS version of the comments.module fixed evrything.

Thanks to all the Drupal developers for prompt fixes.

tfejos’s picture

tfejos commented

After istalled the latest comment.module from CVS today, it fixed comment deleting bugs, but introduced a new one. After sending the comment is it remains at the comment sending URL and not goes to URL of the node. So every time I hit Send it sends the same comment in. Do you have any idea what to fix?

Under 4.7 beta 4
--
TMS
http://fejos.hu

styro’s picture

styro commented

mixing and matching versions like that. You won't be able to tell whether the issue your having is a real issue or was caused by interactions between mismatched code versions. A bug fix might require changes to multiple files, and you'd only be getting part of the fix.

Obviously you're game for hitting some issues or you wouldn't be using the beta, so if you want newer than Beta 4 you may as well go the whole hog and follow CVS for all of Drupal core.

Just my 2 cents :)

--
Anton

iraszl’s picture

iraszl commented

If I had a previous beta version of 4.7 do I have to upgrade the database or there were no database structure changes have been made?

Thanks!
Ivan
---
http://raszl.net

sepeck’s picture

sepeck commented

Just follow the update.txt instructions.
In brief, Backup database and files dir, log in with UID1, replace all files, edit settings.php and run update.php..... go to admin pages. check for stuff.

-sp
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

peekj’s picture

peekj commented

I did the upgrade and everything went smoothly, except that I used to have some conditional statements in my node.tpl.php using

if ($main)

to display content only on the main page and not on the individual node page (actually it was the other way around - I had some ads below each post but didn't want them on the main page).

That no longer seems to work. Can anyone confirm that? Is there another way of doing what I was doing?

Thanks!

markus_petrux’s picture

markus_petrux commented

Have you tried using if ($page == 0) ?

Doubt is the beginning, not the end of wisdom.

grbitz’s picture

grbitz commented

Upgrading from 4.7b2 to 4.7b4 has caused all menu dropdowns to disappear, as on the settings page under admin. The text remains but is not clickable. I'm running PHP 5. Deleting and repopulating the database doesn't fix this. Clearly this is a matter of some urgency, as I can't change any of those settings on any page where that type of dropdown appears.