Website and email fields.

As well as cell phone.

hmmm I'm thinking that regular cck fields can fill that need?

maybe the fancy version of including those kinds of things could be generic: a user interface which could allow an admin to select other cck fields enabled on their site to be part of a meta location. Then that location could include the usual location stuff, and any other cck fields that were added, like a file/picture.

This might be possible now, create a content type meta location, add whatever cck fields you want, and add a location. Then in your content type, business directory entry, for example, add a meta location (or a node reference to it). Or, in your content type, business, allow multiple business diretory entries, or multiple meta location entries.

Tagging.

marked #349936: URL associated with location as a duplicate of this issue

if using this method though, how would the item be associated with the location in the location table?

I am using cck location field now and am having issues with proximity filters, etc.

if each node only had one location, and if you could make a view that would list the correct nodes, then in the fields, you should be able to select the website or email fields associated with that node (not with the location)...

I use location for venues. It would be great to add the venue url and email address as part of location just like phone or fax now. It is just easier. that's all. just a suggestion :)

I dont know... this sounds like location is turning into a directory module. Maybe it should be the other way around, use a directory module, and use location as part of that solution?

Or if not use a directory module, create a directory content type, then use location as PART of the solution for that content type. Let that other content type worry about having a venue url and email address.

Thoughts???

No sure to understand you.

My first idea for using location was to use location CCK as a repeatable field on the main node. This way, all location field (location phone ...) are repeated for each iteration of the location CKK field, with a clear association. If I put all the phone numbers on the main node, as CCK field, I will not know which one is going with which location, as, as far as I know there is no way to repeat groups of CCK fields, only individual fields can be repeted. This told, it would be extremly nice for me to be able to repeat groups of CCK fields.

I am also considering to have a main node type with references to a secondary node type for locations that way I could add as many CCK field as I want and one single (CCK) location field to the secondary node type. It seems simpler and more powerful from the drupal point of view, but it would be longer and more complicated to enter the data for the users of the site.

One idea is to arrange the phone, website and the cck location (so they are associated with the location as you say) in a field group in the cck content type. Give that a try.

I get where you are coming from now, because you have a node that has multiple locations and each location has a field (like phone or website) and so it is easier to just have that be part of the location module. But, like you said, the Drupal way seems to be instead to use the building blocks of location, cck, etc to build what you need. Harder to get going the first time, but is super cool, and you dont have to wait on a maintainer of the project to implement it for you! (any project, not dissing bdragon. love bdragon!)

I added website field.... here's the zip, unpack in contrib folder.

If anyone needs a email field for location let me know, I'll create it and post it here!

Cheers

email field would be great too!

Will look into that tomorrow!

Cheers

PS. if the add-on I added above worked for you, let it know so maybe it can get committed

Here ya go....

Cheers

PS. post back if it works!

Please post patch files instead of zip files.

It is much easier and also the standard on drupal.org

and mark the issue needs review if that is the case.

I think this is a great idea.

No more needing to use views and relations and arguments and stuff like that, just to achieve the simple purpose of putting things together where they should be.

Thanks for the implementation Bartezz .

@#14

I know patches are the standard... but erm there is nothing to patch here!
These are complete new files including within a directory...

This directory is supposed to be dropped into the contrib directory.
Not sure but as far as I know you can't create directories by means of a patch, nor can you patch none existing files...

Hence a ZIP file...

Cheers

FYI,

If you have a copy of the current location module and a copy of your new version (both the whole location directory with everything under it) you can use

Of those options, the u & the p are for readability and should be always used. The r makes it recursive, so you get your folders and the N treats missing files as empty, so if a file did not exist before it is created.

Fair enough... didn't know about that. Using Tortoise SVN.