This is a drupal 6 distribution for movie reviews.
It contains following features:

Content types:

Movie reviews
Movie events

The following things are done through views

Blocks:

Latest reviews
Latest events
Related movies of this genre

Slideshow:

Movie review slideshow (with image, short description and title created in movie review content type)
Movie eventslideshow (with image, short description and title created in movie event content type)

Listing page:

Movie reviews (10 lists pers page)
Movie events (10 lists pers page)

Theme:

A ready made theme called Neelambal based on 960 grid system.
This theme is contributed by me and could be found in http://drupal.org/project/neelambal

Project Page :
http://drupal.org/sandbox/nalan/1557778
GIT repository:
git clone --recursive --branch 6.x-2.x nalan@git.drupal.org:sandbox/nalan/1557778.git movie_base

This distribution is for drupal version 6.

My reviews for other projects:
http://drupal.org/node/1475048#comment-5826548
http://drupal.org/node/1475184#comment-5831278
http://drupal.org/node/1212602#comment-5831666
------------------------------------------------------------------------------------------
http://drupal.org/node/1475184#comment-5850086
http://drupal.org/node/1522378#comment-5855410
http://drupal.org/node/1522378#comment-5855904
http://drupal.org/node/1522378#comment-5861216
http://drupal.org/node/1522378#comment-5865560

Comments

klausi’s picture

Status: Needs review » Needs work

manual review:

  1. do not commit Drupal core and all the contributed modules/themes to your repository. Only include things that you specifically created for the distribution and use drush make files. See http://drupal.org/node/159730 and http://drupal.org/developing/distributions/drupalorg
  2. Your should only have the installation profile code directly in the repository root folder.
nalan’s picture

Thank you for the review. I'm working on the corrections.
Btw, what do you mean by "Your should only have the installation profile code directly in the repository root folder". What about the other files? At the end, how will it become a complete package? Are there any other tutorials links to understand the process? Thanks for your help.

AmbikaFR’s picture

Hi nalan,

I think klausi wants to say that you need to use drush make, to get drupal core code or contribued modules. Drush make should dynamically get the correct version of Drupal core, modules, themes, and so on.
You can find a nice tuto here in order to build your drush make file : http://wiredcraft.com/blog/drush-make-and-install-profiles-drupal-7/inde....

AmbikaFR’s picture

Hi nalan,

After a manual review i ve found minor issues in your profile file code :

  • You should comment the global variable declaration (NEELAMBAL variable)
  • You should remove hook_profile_task_list, wich is not really used in your code
  • You should also remove commented code, in moviebase_profile_tasks function

Regards,

AmbikaFR.

klausi’s picture

@AmbikaFR: please do not review applications in the "needs work" state. Review those in the "needs review" state instead. See http://drupal.org/node/532400 . Thanks.

nalan’s picture

Hi AmbikaFR,

Thanks for your review. I'll make the necessary corrections. By the way, sorry for the delay in reply, i was busy in someother work. It is been so many months, so i didn't check here regularly. Thank you once again :)

klausi’s picture

Status: Needs work » Closed (won't fix)

Closing due to lack of activity. Feel free to reopen if you are still working on this application.

klausi’s picture

Status: Closed (won't fix) » Needs review
Multiple Applications
It appears that there have been multiple project applications opened under your username:

Project 1: http://drupal.org/node/1666240
Project 2: http://drupal.org/node/1892212

As successful completion of the project application process results in the applicant being granted the 'Create Full Projects' permission, there is no need to take multiple applications through the process. Once the first application has been successfully approved, then the applicant can promote other projects without review. Because of this, posting multiple applications is not necessary, and results in additional workload for reviewers ... which in turn results in longer wait times for everyone in the queue. With this in mind, your secondary applications have been marked as 'closed(duplicate)', with only one application left open (chosen at random).

If you prefer that we proceed through this review process with a different application than the one which was left open, then feel free to close the 'open' application as a duplicate, and re-open one of the project applications which had been closed.

nalan’s picture

Status: Needs review » Closed (duplicate)
avpaderno’s picture

Title: Movie Base » [D6] Movie Base
Component: other » distribution/profile
Related issues: +#1892212: [D6] Project Management for Agile