This module creates a content type called immoclient. Immoclient is built after the official German "openimmo" xml-standard to create real estates.
This is used in German speaking countries (Germany, Austria, Swiss).
What this module does:
It creates about 300 fields per click and gives a easy to use UI to manage real estates, used by real-estate agents in German speaking countries.
You only need to enable "immoclient", there are a lot of dependencies which are called then. Easiest way is to use drush. After that you have to build your views, because of the huge amount of fields, and some of them are only for the agencies itself, there is no way to show these nodes any clients.
First you should have a drupal with German language as default then install this module. I hope that you have activated clean urls.
Then follow these steps, the order of these steps makes it easier to use:
- Configure entity translation (admin/config/regional/entity_translation):
Be sure to activate all submodules. - Configure the language (admin/config/regional/language/configure) as follows: this gives the best result in my opinion:
URL, USER, SESSION - You should replace the title with the title module(de/admin/structure/types/manage/immoclient/fields)
- Configure gmap (de/admin/config/services/gmap)
- Configure location (de/admin/config/content/location)
- Create your impressum (admin/de/impressum), there are a lot of fields that are demanded by openimmo.xml.
- Create at least one contact. Salutation,name and telefone should be enough!
Now you can build your first object!
git clone --branch 7.x-1.x http://git.drupal.org/sandbox/maen/2469709.git immoclient
cd immoclient
Manual reviews of other projects:
If I should fall back to "needs work", here are some other projects too!
Comments
Comment #1
sagesolutions commentedAutomated Review
There are multiple issues in the automated review - check http://pareview.sh/pareview/httpgitdrupalorgsandboxmaen2469709git for details
Comment #2
maen commentedHello sagesolutions,
could you help me please solving my issues.
1. Problem:
The main module is "immoclient". So the name of the other 11 submodules in "contrib" starts with immo. Because each submodule creates an entity and entities can't have a "_" in their machine names I can't use this convention.
2. Problem:
I don't know how to move my translation to localize.drupal.org!? I am now a member of the German team, but the import fails. Perhaps because there is no project immoclient and for the submodules???
THX in advance,
Marc
Comment #3
maen commentedThere is no common way to create a module with 11 submodules, each containing an entity. The naming conventions therefore are always clashing!
Also it is a German tool, so the translation has to be there. Localize.drupal.org accepts only modules, not even in the dev status. So in my mind there is no other way than having de po file in the translation file into the project. When the project is accepted I can import this po file.
Comment #4
PA robot commentedWe are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)
Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #5
ravi.khetri commentedHi,
1. Remove unused comment line form module file.
line 30 to 32.
2. Use css folder for place css file separate.
Comment #6
maen commentedThx ravi, done and done!
Comment #7
saurabh.tripathi.cs commentedHi ,
Found below points which may need correction:
1)Unused Commented code: line 91 to 95.
2)t() missing from form_set_error :
line 68,78
3)Comment for form_alter missing in line 202.
4)Implement hook_help() to make users understand your module better.
Comment #8
maen commentedThx saurabh,
all 4 points are done!
Comment #9
babusaheb.vikas commentedHi maen,
1. Correct hook comment is:
Implements hook_HOOK().. So, go through your *.module file and change it.2. It would be good if you create a js folder and put your js files in it.
3. Add one empty line at the end of your *.module and *.install file.
Comment #10
maen commentedOk, thx babusaheb, everything made.
Although I added this line, I don't know what's the sense??? Could you explain please?
Comment #11
maen commentedComment #12
maen commentedComment #13
babusaheb.vikas commentedHi maen,
take up index.php file that comes with drupal 7, it has 21 lines of code but it actually has 22 lines (the extra one blank line. The same goes with update.php. The best way to identify and understand the coding standards is to open up the drupal core and compare it.
Also, take a look on Coding standards
https://www.drupal.org/node/318#indenting
Comment #14
maen commentedComment #15
maen commentedComment #16
maen commentedComment #17
fabianx commentedGreat project! Reviewed the code for obvious security problems and found none, code standards are generally followed.
=> RTBC
Comment #18
cweagansThanks for your contribution!
I updated your account so you can promote this to a full project and also create new projects as either a sandbox or a "full" project.
Here are some recommended readings to help with excellent maintainership:
You can find lots more contributors chatting on IRC in #drupal-contribute. So, come hang out and stay involved!
Thanks, also, for your patience with the review process. Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.
Thanks to the dedicated reviewer(s) as well.