drupal 4.7

Hi to all! I'm using Drupal 4.7.X platform on one of the landscaping ideas sites as a gardening tips section (actually, I like the easiness of using Drupal to add small articles to this section). I saw 5.2 is now available where some problems are fixed concerning security vulnerabilities.

Is it still OK if I use 4.7 or upgrading is needed?

Mike

Hi, everyone.

I am having a problem with a site that I set up a short while ago, http://www.make-a-statement.net. Other than having edited the blog module to make them private blogs, it's a standard 4.7 installation. What's happening is that the site is rejecting all non-admin logins, period, even when valid, and it's not allowing the admin user to gain access to the administrative functions. This is my livelihood, so if someone can help me out ASAP, I'd be very, very appreciative.

Dheeraj
http://www.dheerajchand.com
dheeraj[AT]dheerajchand.com

After a lot of work we have now released rc1 of v3.0.

I think we have fix all the major bugs, and we feel that this is the best release that we have had mainly due the the new release system which has enabled us to do things the right way and release several betas and now an rc.

As long as there are no new major bugs we should be able to release a final version of 3.0 this time next week.

Well we have still been working very hard to get the best release that we can.

This is the forth and final beta version of E-Commerce, and from what I gather the bugs have started slowing a lot, and E-Commerce has even dropped of the top of the list as the Most active project. E-Commerce has been there for about the last 4-6 weeks and so I think that we are getting there.

All going well next Saturday the 3rd March I will be doing the first release candidate.

Thank you all for helping test, and making this a great release.

You can download beta 4 from

Over the last couple of weeks since beta 2 was released all the E-Commerce maintainers have been working extremely hard to fix all the bugs, (and there was a lot of them) and get out a new Beta to allow people to continue testing.

As you can see from the http://drupal.org/cvs, 4 of the 5 E-Commerce maintainers are in the most active developers list, with the last one being there a few days ago. Also you will see that the E-Commerce project is the most project ATM.

The token module is now required by E-Commerce core.

Modules added to the system are:

Core modules
ec_anon (anonymous purchasing) - Developed by Sammy Spets
ec_mail (mail handler module) - Developed by Sammy Spets
invoice (Back office system to create transactions for customers) - Developed by Gordon Heydon

I just released flexinode's 4.7 third preview release.
If you want to keep up-to date, follow flexinode news here (RSS).

I just released flexinode's 4.7 first preview release.
If you want to keep up-to date, follow flexinode news here (RSS).

The (削除) stroked (削除ここまで) fields are confirmed, tested and thus ready to go for 4.7:

Critical fields:

• (削除) textfield (削除ここまで)
• (削除) textarea (削除ここまで)
• (削除) datefield/timestamp (削除ここまで)
• (削除) number (削除ここまで)
• (削除) image (削除ここまで)
• (削除) general file (削除ここまで)
• (削除) selectlist (削除ここまで)
• (削除) checkbox (削除ここまで)
• (削除) url (削除ここまで)
• (削除) email (削除ここまで)
• (削除) multiselect (削除ここまで)

None critical fields (contribs)

• podcast_author
• address
• table
• usergroup
• colorpicker
• external_attachment
• gallery
• mp3
• imagegal

Sorry i havent posted in while been busy with so many different things, so much to learn/do so little time hehe :D.

Anyways for past few weeks i have been attempting to create a plan of how go about each stage of the project. But because of what i need to learn and acheive the project just seemed bigger everytime i had a look at it :(.

After a session with drupals SoC pyschiatrist (webchick ;P), I do believe i have it figured out, well the first part anyways (first lesson learnt; dont think about the whole project, take it a chunk at a time).

I spoke to earls about it aswell and this is what i i think is the best way to get moving and seeing some progress will probably help,so to begin with i think its best if I got a list of exactly what i need from the schedule.module, whats missing.

This basicly means see if code is hijackable and what is needed on top of that code to make a ideal schedule module for our use.
Btw this could also be approached from the other end figuring out what i need form the views and whats missing etc.

From the views point, whats missing is an ID, an Entry point, and way to control the schedule.

now taking into consideration the schedule.module db design which i see as: