Classifieds for 6.11?
Thepennycup - May 3, 2009 - 00:46
Does anyone have a classifieds ads module or theme for 6.11?
Thank you?
Edited by WorldFallz - moved to appropriate forum.
Does anyone have a classifieds ads module or theme for 6.11?
Thank you?
Edited by WorldFallz - moved to appropriate forum.
_
Please don't cross posts duplicate threads. I deleted the dupe. Thanks.
Regarding your question--
1) modules are easily searchable: http://drupal.org/project/modules?filters=drupal_core:87&text=classified
2) the one module appears to have been recently abandoned and not picked up by someone else yet. More than likely because classifieds is something that can be easily assembled with core plus views & cck.
_
Don't be a Help Vampire - read and abide the forum guidelines.
If you find my assistance useful, please pay it forward to your fellow drupalers.
@WorldFallz, I am curious as
@WorldFallz,
I am curious as to how you would make the adds auto expire using views, how you would set adds under specific taxonomies to require payment, how you would set ads to notify the poster via email at a set period of time prior to the ad's expiration, how you could set an add to be 'renewed' thus extending the duration...
As far as I can tell, these are the most critical issues with any add site, and none of the above functions can be implemented with "core plus views & cck".
So since I found it mildly irritating that you would try to pass off the lack of classifieds in 6x as something that should be easily created per instance by any skilled drupal user; I will tell you the real reason:
The people who develop these mods do so when they have a client requesting these features. Once the client is no longer doing business with the developer and the module is no longer used, the developers drop the mod like a hot potato UNLESS you pay them to continue working. That is the case with Classifieds and Drupal 6. (May not be the case with every mod, but it certainly is with this one).
Classified adds are the easiest way to make money on a drupal site, and as such, nobody wants to help anyone else make money without monetary compensation for themselves. I understand that completely and do not blame them; but don't try to gloss it over as un-needed or redundant functioning. The bottom line is, someone will have to pay a developer to code a classified module for Drupal 6 before we see a solid build, then maybe, if generosity suits them they will make it public...or maybe they will keep it for themselves
Oh, and don't get me wrong, I
Oh, and don't get me wrong, I am not saying that coders *should* do it for free, or are wrong for not doing it for free or that we, the drupal end user are 'owed' anything by any of these coders or mod developers...we are not.
I just felt you were steering the OP in the wrong direction. I too have been searching for a classified solution for a D6 installation; but after searching various options, have come to realize that one will probably not be implemented soon; this is the case with many D6 modules and if you want to be able to use ALL of the most useful modules for Drupal, you should stay with D5... end of story. That may not be the case 6 months from now, but with all the more mods that were ported to D6 in the past 6 months, I wouldn't expect to see a full modules section for D6 anytime soon.
_
Sorry if my response seemed flip, it truly wasn't meant to be. I also didn't mean to imply that views + cck = all. However, the fact is you'll notice that many of these single purpose modules are being abandoned. The simple fact is, whether you agree with it or not or find it convenient or not, the trend is away from vertical modules toward a more building block approach that was enabled primarily by the cck and views modules. And i don't see that trend reversing anytime soon.
The op doesn't mention anything about ecommerce or payment or I would have suggested first selecting the payment module-- the current choices being ecommerce, ubercart, and lm_paypal (if you all you want is paypal integration). Then, once you've installed your selection and evaluated included functionality, you can add all sorts of features with contrib modules. I'm not up to date on the current features of the ecommerce modules, but things like expiration (which you mention specifically) can easily be added with the node_expire or rules modules.
Sorry, but I'm not steering the op in the wrong direction. With cck in core for d7 and views on it's way to core-- cck and views are the future of drupal and therefore the correct direction. Combined with other build block modules like nodequeue, flag, rules, imagefield, filefield, etc you can build almost any type of site.
At this point modules without even a dev d6 version are probably not going to be ported.
_
Don't be a Help Vampire - read and abide the forum guidelines.
If you find my assistance useful, please pay it forward to your fellow drupalers.
Ok, i suppose in retrospect,
Ok, i suppose in retrospect, my reply may have seemed a bit harsh as well and for that I apologize. What many people at Drupal fail to see (because they are too close to the project) is there is an ever widening divide in drupal users, and it is the elite of those who are being catered to. Two years ago anyone could come to drupal.org, download the CMS and associated modules and put up a site on par with http://www.nysenate.gov. Now, that site took an entire development team of presumably professional coders to get a site that in 5x could have been done with the event module, embedded media, one of the map mods, and of course pieces of the non core 'core' modules (views, CCK, etc) by ANYONE with minimal code experience.
All forums have people who feel they are the elite and that anyone who cannot write a module in 15 mins while simultaneously running SQL queries shouldn't even be posting, so I am sure I will catch some flack over this if it is seen; however, I would venture to guess that 50% of the current drupal users do not know how to patch a mod or even what a tarball is. That was the beauty of Drupal! I have been developing sites using Drupal for a few years now and am not an expert in CSS, PHP or anything. If I was I would be working for a major development firm rather than running a computer repair small business and cobbling Drupal sites; but as I mentioned earlier, that makes me part of the vast majority of Drupal users.
I will consede that you are correct steering the OP to views and CCK as the 'trend' that approaches within Drupal. Unfortunately, that is a dark tide approaching for many of us. True, you can use views, date, calendar and CCK to produce the same results as the Event module; however, I would venture to guess that less than 50% of us posess the understanding of those modules to do so. Some of us could cobble our way through it using tutorials etc; but the big question there is why would we want to when Event is so much easier to acheive the same results? True there is a development snapshot 6x version of Event, but there is nothing for D7... I used event because it was perhaps the best example I could think of.
I understand that any project has to be able to handle the growing requests of the 'Pros' that want to implement it; however, Drupal gained it's fame on the backs of simple cobblers such as myself, and I feel we are being forgotten...
_
I totally get what you are saying-- and you do have a good point. The thing is-- the skills it takes to create and maintain a vertical module like classifieds requires exactly the type of coder that prefers to work on the building block approach. And the people that need such a module, generally don't have the skills to create and maintain it. So I don't see the current trend changing.
The good new is there's a HUGE emphasis on improving usability which is also on the way to including 'installation profiles' which I think will address this need. These will be preconfigured vertical installations packaged up so as to be as easily installed as drupal itself. Personally I like this approach-- it keeps the coders happy working on building block modules and yet provides accessibility to the masses of non-coders. And the skills required to create an installation profile should be far less then those necessary to code a vertical module-- hopefully it will hit the sweet spot and we will see installation profiles popping up like dandelions!
_
Don't be a Help Vampire - read and abide the forum guidelines.
If you find my assistance useful, please pay it forward to your fellow drupalers.
Ok that sounded sort of
Ok that sounded sort of reassuring, and I say sort of because I have no idea what an installation profile is lol (no need to waste time explaining it to me hehe).
Thanks for replying!
P.S. I know I shouldn't be using D5 as it has much weaker security, but personally, I may try to ride that wave till it crashes on the beach and hope to drag a few dozen more sites out of it. Probably a bad idea, but I'm old and really don't have brain power or time to learn to master the above mods without a personal tutor lol
So in trying to develop a
So in trying to develop a newer approach to designing my sites, I began to install the directory module and then remembered what you (WorldFallz) said about single purpose modules and thought I'd look into a better (or at least different) solution. Do you think I would be better off creating a directory site using the category module as opposed to directory?
I am trying to embrace the building block module concept, but it really is hard for me (and many others I would guess) to implement.
_
I wouldn't recommend the category module because, of its own admission on the project page, it's a complex module that pretty much commits you to its usage (you can't "undo" it). I also wouldn't recommend directory-- it's been in alpha since jul 08, the last commit was 32 weeks ago, there's only a few hundred sites using it, and the issue queue seems largely ignored. I doubt there's very much it can do that can't be done with views2. My guess is it did some things that couldn't be done prior to view 2 but once that was released it became essentially obsolete. That's just a guess though.
My current process, and what I recommend to others, is to start with cck and views as the basis for any site, get as far as you can, then add other modules as needed. The great thing about this approach is once you've invested to the time learning cck and views that knowledge is applicable for every site you build-- no matter what 'type'. You don't have to spend time learning the directory module for one site, the category module for another, jobs for another, classifieds for another, etc. You learn the modules once and use them for everything.
The list of modules currently in my toolbox are:
Course this is what works for me-- as with anything, ymmv.
_
Don't be a Help Vampire - read and abide the forum guidelines.
If you find my assistance useful, please pay it forward to your fellow drupalers.
Outstanding! that gives me a
Outstanding! that gives me a great place to start then. I have of course read the online handbook for CCK here, but I think I am going to google that and views tutorials and see what shakes loose.
Sure is different, I remember when the biggest worry in throwing up a drupal site was modifying css that hadn't been formatted properly for the theme, of course some of my D5 sites have 3 times as many modules as you list above...
Thanks for taking the time to help :)
_
Glad you found it useful.
I should add I have one caveat with this approach-- ecommerce sites. If you're planning an ecommerce site I recommend picking the ecommerce module you're going use first. It's the one big vertical type application that does actually justify a large encompassing module.
The current choices are ubercart, ecommerce, & lm_paypal. For simple needs with only paypal payments lm_paypal deserves an evaluation. For a full featured site you'll want to pick ubercart or ecommerce (as you can see above I have chosen ubercart).
Then once you've familiarized yourself with the module's available functionality and add-ons, you can add other modules as necessary.
Good luck!
_
Don't be a Help Vampire - read and abide the forum guidelines.
If you find my assistance useful, please pay it forward to your fellow drupalers.