Drupalistas rejoice (again) -- we've reached another major milestone on the road to the official 5.0 stable release! The latest 5.0 release candidate code is now installed and running on http://scratch.drupal.org. This means that all of the modules and themes installed on drupal.org have been ported to the 5.x API.
Running the release candidate on a large site like drupal.org is an important way to flesh out any remaining bugs in the code, and the first step is running it on our test site. Please help us get 5.0 stable enough to release by checking out http://scratch.drupal.org and seeing if you find anything that doesn't work how you expect. We need your help testing, so read more to find out how...
This test site is using a snapshot of the drupal.org database as of 2006-12-22, so you should be able to login directly using your drupal.org identity (you do not need the "[username]@drupal.org" trick, just the "[username]" part). If you find any problems, please submit an issue (here on drupal.org, not scratch.drupal.org). You should search the existing issue queues before you submit a new issue, in case you have encountered a known bug.
Please try to submit your issues for the appropriate project. In most cases, the code would be from Drupal core itself. However, if the page you are viewing starts with "/project/issues" or you have trouble submitting test issues on scratch.drupal.org, you should submit to the Project issue tracker queue. If the page starts with "/project" (but doesn't include "issues") please use the Project queue. If there is a bug regarding CVS integration (see below) you should report it to the CVS management/tracker queue. Otherwise, use your best judgement...
Contribution maintainers -- help test the release system
If you maintain a contribution (module or theme) on drupal.org, please help test out the new release system. There is now a scratch copy of the contributions CVS repository for making test releases. Please read http://drupal.org/node/105016 for more information about the scratch repository and how to provide feedback.
The official 5.0 stable release will be released when it is stable. ;) If no more critical issues emerge and Drupal.org has been running without problems, we will provide an official stable release. If problems emerge however, we may produce any number of release candidates in between. You can also help improve the quality and stability of the forthcoming 5.0 release by testing and reviewing patches that have already been submitted to address bugs and improve usability.
Comments attached to this post reporting problems are likely to get lost or ignored, so please use the issue queues as explained above. Thanks for helping to make the 5.0 release come more quickly, and happy bug hunting!
Comments
Great! Havn't found any
Great to see V5.0 run on official drupal site!
Havn't found any problem so far.
Happy to be 1st comment (even though it of no use as mentioned above.)!
Few issues
For the modules I was involved with, here are the issues I see:
1. I know that features is not working properly (links are only shown as
<?<#<with no text).http://scratch.drupal.org/features
Issue opened here http://drupal.org/node/105023
2. Donations gives an error. The page needs to change to call the correct function.
http://scratch.drupal.org/node/2227
3. Lists also need to call the correct function.
http://scratch.drupal.org/mailing-lists
--
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
these 3 are now resolved
i worked with kbahey to solve all 3 of these issues. should be fine now.
___________________
3281d Consulting
I just spent some time
I just spent some time clicking through a variety of links as both a logged in and an anonymous user -- In particular, I was looking for anything off in the UI of the modules section --
And, everything looked good -- I spent about 20 minutes trying to break something, and had no luck :)
About the only thing I noticed (and this is REALLY minor) is that the URL for the mailing list (and most of the urls on that page, actually) at http://scratch.drupal.org/contribute appears to be hardcoded, as they point back to drupal.org -- I was trying to check out the mailing-list issue as described on the dev list.
So, aside from one pretty meaningless detail, things are working well -- great work!
Cheers,
Bill
-------
http://www.funnymonkey.com
Tools for Teachers
-------
http://www.funnymonkey.com
contribute page links now site-relative
thanks for pointing that out. now fixed on scratch.d.o.
___________________
3281d Consulting
Its faster loading
My first impressions are that this Drupal 5.0 is faster than all previous versions. It was fast to open any pages at the test site.
no load
THe fact that there are not several hundred registered users and thousands of anonymous users looking at scratch does tend to help with performance as well.
-Steven Peck
---------
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
Donations
I am posting here since I don't know to which project this bug/feature belongs.
If you look at donations (http://scratch.drupal.org/node/2227) the name corresponds to the name on the creditcard. The donation is always linked to a useraccount if the emailadres is known.
However, I would think that the fullname/nickname of that user would be used (if exists). But it isn't. This is a bit akward (and makes it uncomfortable to donate with a creditcard not on your own name) and strange when clicking through.
Good idea
I think this is a good idea. I made a version with that change, and mailed it to Derek to install.
What it does is use the drupal.org name if the user is registered, otherwise, the name as entered in Paypal.
--
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
now installed
kbahey's latest copy is now installed on s.d.o.
___________________
3281d Consulting
Thanks for the quick
Thanks for the quick fix!
Another thing is, it is not possible to pay with different creditcards on the same drupal useraccount since, with payal, one creditcard is linked to one emailaddress. This is good for paypal but not necessarily for Drupal. Can we add an optional field "useraccount emailaddress", during the paypal payment process? This would make it possible to have multiple people pay on behalf of "one user", "an anonymous account", a "project" etcetera.
feature requests for donation.module are off topic
sadly, there's not yet a good place to discuss the donation.module, since it doesn't have a valid project and issue queue (yet). however, this forum post is not the place to submit feature requests for this module. i'll follow-up here once there's a better place, but for now, you should file issues into the Drupal.org maintenance queue.
thanks,
-derek
___________________
3281d Consulting
Search has an extra tab
The tab has no title, but when you click it you are taken to a page that says "Search results array".
Searching Users odd as well
If you are on the Search tab, enter a user, and click search it kicks you back to Content and reports, "Your search yielded no results". Clicking the User tab after that will show the correct search results.
now fixed
see http://drupal.org/node/105209
___________________
3281d Consulting
Just a personal opinion, But
1) Just a personal opinion, But I prefer the Bolded titles on http://drupal.org/user/22548 ...seems easier to read than http://scratch.drupal.org/user/22548
(Full Name, Interests, Gender etc.)
2) http://scratch.drupal.org/project/issues?projects=3060&versions=96923,10... does not show the different statuses of the issues in different colours.
3) on the front page, the top-left block (wishing you happy holidays) is missing. Just a big empty white space. - I'm using IE7.
4) I'm not sure if it is because scratch is not in main production yet, but it is denitely slower (or at least not faster) than drupal.org for me.
look at: http://www.websiteoptimization.com/services/analyze/wso.php?url=http://s...
and at http://www.websiteoptimization.com/services/analyze/wso.php?url=http://d...
5) Are you going to enalbe CSS Preprocessing on drupal.org? Total CSS imports: 13 (only 8 on production drupal.org - not sure why this is) - Let's eat our own dogfood here.
CSS
#1 and #2 are due to bluebeach's style.css now coming after project's css files. If I remember correctly this can be fixed by making project's css more specific so that the theme's selectors don't cascade over it. This might fix #3 too.
no, it's from classes changing
http://drupal.org/node/105192
please reply there, not here.
thanks,
-derek
___________________
3281d Consulting
Actually...
Actually, #1 is because profile.css is no longer loaded in Drupal 5.0 when viewing profiles. I have made a patch for this at http://drupal.org/node/105216
profile.css stuff now fixed
Chris and I finished up the patch at http://drupal.org/node/105216 which has been committed to HEAD of core. i just updated s.d.o with the latest code, reset the CSS preprocessor stuff, and user profiles look normal again. thanks for the report.
___________________
3281d Consulting
Enabled CSS preprocessor
The idea is sound, I switched on the CSS preprocessor.
--
The news is Now Public | Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.
--
Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.
#3 should be fixed
re: 3) on the front page, the top-left block (wishing you happy holidays) is missing. Just a big empty white space. - I'm using IE7.
that's just because a few of the "spotlight" images that rotate through that spot weren't copied over to s.d.o. i think i've got it all fixed now.
___________________
3281d Consulting
"Patches to review" link
"Patches to review" link points to
http://drupal.org/project/issues?projects=3060&versions=96923,103420,100...
..instead of
http://scratch.drupal.org/project/issues?projects=3060&versions=96923,10...
(scratch. not included in URL)
The site is significantly faster for me now that CSS Preprocessing is enabled - Good indication that this patch was indeed desperately needed :D
fixed on both sites
thanks for testing thoroughly. ;)
___________________
3281d Consulting
Filtering on "Download / Modules" page doesn't work
Hi,
I think the filtering on the "Download / Modules" page is broken:
the "Filter by Drupal Core compatibility:" on the "browse by category" tab always resets itself to "4.7.x", the one on "browse by name" always jumps back to "5.x".
This happens with both Firefox and IE.
...works fine for me. (IE7)
...works fine for me. (IE7)
That's odd because...
I checked the page(s) using Firefox/Safari on OSX and Firefox/Konqueror on Linux and the problem exists there too.
The filtering on "drupal.org" works fine on all systems/browsers.
Double checked just now, and
Double checked just now, and I can reporduce the problem with FF2, but IE7 is fine
it's broken on d.o, the difference is being logged in or not
as far as i can tell, this problem:
a) exists (and has existed for a long time) on d.o, not just s.d.o
b) the main difference is if you're logged in or not, not which browser you're using.
either way, please follow-up to the original issue about this bug (http://drupal.org/node/86806) instead of adding more comments to this thread.
thanks,
-derek
___________________
3281d Consulting
No "Contact" tab for the "my
No "Contact" tab for the "my account" page exists.
Can not login
I'm not sure where the bug exists here. I'm using IE6, and can't login to s.d.o I thought it might be related to this bug http://drupal.org/node/64726 so i played with all my cookie and security settings, but can't make it work. When using invalid login, i get an error message but when using correct login i just get sent back to the same page with no error message and no user blocks. I'm not sure where to post this bug.
--Ryan
--Ryan
Ryan Cross
James Cross Construction Services
Project Management Software
Yep
Yep I wasn't able to login with ie6 either, even after clearing my cookies and cache.
php in comments isn't color coded on scratch
take a look at the difference between
http://scratch.drupal.org/comment/reply/35728/155335
and
http://drupal.org/comment/reply/35728/155335
Code is much easier to read in the 4.7 version.
Filter changed?
On drupal.org we generate:
<div class="codeblock">... while on scratch.drupal.org we only generate:...</div>...Please remember
--
The Manual | Troubleshooting FAQ | Tips for posting | How to report a security issue.
What project?
You asked for help testing this from people who didn't know much about Drupal. I know I have no idea what project to report the issues on scratch under. Drupal? Drupal.org maintenance? And what component? website? other?
This helps...
But when newbies like myself see other people posting problems here... and more importantly those problems being addressed... it doesn't take a UI guru to figure out why people keep posting here.
I might help to have something like... If you are unsure where to post a problem, post it here... with a link to the specific project/component/version you'd like these posted in.
Re-read the initial post
Hello, kreynen,
RE:
Quoting from the initial post:
Hope this helps to clarify.
Cheers,
Bill
-------
http://www.funnymonkey.com
Tools for Teachers
-------
http://www.funnymonkey.com
Did you really think that would help?
That's like giving directions... "turn left where the old church used to be". When I click "submit an issue" I'm asked for information I don't know.
In the first paragraph it says submit using drupal.org, not scratch.drupal.org. Then next paragraph "or you have trouble submitting test issues on scratch.drupal.org"? Why would anyone have trouble with something they're not supposed to do?
Like I said, pointing to the Drupal core helps, but even when I get there I have to decide between several components; base system, node system, user system, menu system, search.module, drupal.css, other?
What would the errors I found with search tabs and code coloring be? What should I have done if I didn't know which component was causing the problem?
My point is if understanding the Drupal core structure to report issues was required to test scratch, you shouldn't ask people new to Drupal for help.
Yes, in all sincerity, I did.
I'm not posting in these forums to waste my time, or yours. I'm giving my time here because I have gained a lot from my contact with the members of this community, and the code and documentation they (we) have created.
To quote again from the original post:
Operative words: "Please" and "try."
Again, from the original post:
If you misfile an issue, it's not the end of the world. But, please understand -- the issue queue is the *best* place to give feedback because that is where the most developers will see it. Things get lost in the forums. This is less likely to happen in the issue queue, particularly with an issue filed against core.
RE:
I don't really know -- if I was to file an issue on this, I would probably lead with the css, as many of the classes change between releases -- My opening for this issue would be something like, "I'm filing this against css, but, really, I'm not 100% sure this is a css issue -- however, this is what I saw..."
RE:
I disagree. The more people helping, the better. And fresh eyes often spot things that more experienced users miss.
Anyways. Hope this helps to clarify.
Cheers,
Bill
-------
http://www.funnymonkey.com
Tools for Teachers
-------
http://www.funnymonkey.com
...
I re-read the original post. I didn't see anywhere it said new people only.
It asked for people in the community to test it. If it is beyond your current skills then you can either give it a try anyway, figure out how or ignore the call for help on a site that is fairly important to successfully using Drupal.
How are we to ask the community to participate and help? The stuff folks are doing is not simple. Drupal.org for all it's primarily core modules is a fairly large and diverse site. It has just undergone a complex update of Project module to add capabilities and a new foundation to our infrastructure for module and theme contributors maintaining modules and end users making appropriate tools to download modules. So far this has been the work of very few un-appreciated folks.
As with any open source project, help is welcome but that doesn't mean people actually will help. Many will find reasons not to and that too is their right. Perhaps with a little more experience they will no longer be new and be willing to help. In the meantime, please re-read the instructions and give it a shot, you've been around for almost a year now so should be starting to get the hang of things. :)
-Steven Peck
---------
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
Response
One of the key features to test is the 5.x port of project_issues, which would primarily be oriented around submitting, editing, and viewing issues. That is why Derek says "test issues."
Constructive feedback is well and good, but at no point were new users specifically asked to test scratch.drupal.org. Perhaps it wasn't clear enough, but porting feedback is not requested from new Drupal users.
This isn't something to worry about - if you pick the wrong component someone will switch it to the right one. I've never seen anyone yell at an issue submitter for picking the wrong component. You may be correct in implying that a working default value for components would be useful though (or not requiring a component).
You may submit them under the "base system" component for Drupal if you're not sure where they should go. It really isn't a big deal - any errors will be corrected by experienced developers.
Ultimately you seem to be asking for a complete explanation of the project_issue system within Derek's post. This is neither feasible nor effective. I think the best response to your arguments is that something to this effect be added prominently to Derek's post: "If you are new to Drupal, please ignore this post." There is also a fair amount of documentation already available in the handbook to interested users. See, for example, http://drupal.org/node/317 and the documentation linked afterwards.
Thanks for taking the time to post your concerns though.
Got it... if I am unclear about component, I'll use base system
Thanks for the explanations.
I've had an account for a year, but haven't been active until recently. The admin interface improvements in 5 were enough to get me to stop hacking 4.7 with custom includes and spend some time helping get 5 out the door. When Heine posted the RC1 announcement, he asked "everyone" to install Drupal 5 and submit issues. He went so far as to invite the technologically cursed as well.
I didn't say that scratch was only for new users, only that it was out there for ALL users and the process of submitting issues could be more straight forward if you wanted new users to get involved. If you aren't specifically asking for help from people who know how to do A, B, and/or C, you need give people like me default instructions.
I know how to submit an issue when I have a problem with a specific module, but trying to figure out what system caused the oddities I noticed was beyond me. I didn't need a complete explanation of the Drupal internals. All I really needed was ChrisKennedy's advice to default the base system for issues I'm unsure about (thanks again, Chris!).
Pointing me back to original post as if that should have been clear to begin with wasn't helpful.
5.0 Impressive
I installed 5.0 RC1 today. I am new to Drupal, and have only recently installed 4.7.4 for the first time.
I am very pleased with 5.0's more intuitive administration interface, and impressed at the flawless and fast installation of 5.0 base.
Kudos to the development team!
I'll keep you posted as I discover V 5.0.
John Lowe
johnjolowe@gmail.com