Since I can't seem to get any response at all to my original query, I thought I'd try again with some incentive. I do a lot of research and experimenting before I post a question-- I really do need help with this one, folks.
I know $20 isn't much, but I think this should be relatively simple for someone who codes Drupal-- correct me if I'm wrong.
In short, here's the issue:
By default, when a user goes to post a new forum topic, the Forums select menu returns every single container, forum and sub-forum in the taxonomy.
Ideally, I'd like the menu to list only the forums from the user's location and below. If a user is at Container 1/Forum 2 /Subforum 1/
I'd like the menu to list *only* Subforum 1 + any children.
Is this possible? $20 for that solution. If that isn't possible, $20 to the person that gets solution #2 working--
I'd prefer that the Forums menu not show up at all [when submitting a new topic]. When a user creates a new post, it should default to their current location in the forum hierarchy. Ideally, I'd prefer that it output "You are posting to "Whatever Category," in case the user somehow gets lost.
Again, solution #1 is strongly preferred. My server is running MySQL 4.1 and PHP5. If you need more info, let me know.
There's a bit more info in my original post..
I WILL PayPal the first person that gets me going with this, but my power is on-again/off-again right now (I'm near Rita-ravaged Texas).
Thanks.
-jcv
Comments
I am formally retracting this offer.
We've decided to cut our losses and move our current projects to another CMS.
We did a lot of research before settling on Drupal. Though the learning curve is a bit steep, it is incredibly robust. The support community seemed great with a wealth of knowledge and helpful suggestions.
What we did not count on is the complete lack of response from the support community. Nope, we didn't pay a dime for the software, but we DID put countless hours and effort into three separate projects and we DO contribute financially to open source software-- just not to open source software that does not offer any support that's not already in the handbook and forums.
5+ days without even one response is a dealbreaker. If our sites had launched and needed critical support, would the response be any better? Rhetorical question because we just can't afford the risk.
Good luck, folks.
$20 doesn't get you much if any...
There is plenty of help on the forums and the mailing lists, and civicspace, and the various websites of different developers....
Waving $20 doesn't get you much attention from professionals, and your original request was quite complex, not just a simple 'how do I'....
So long and thanks for all the fish.
Re: $20 doesn't get you much if any...
I know $20 isn't much-- I'm a professional as well (believe it or not), however, I can only go by what I DO know--
All I can go by is the experience I have with other software, and with the other software I have used, this would have been a simple edit. My apologies for underestimating the labor involved, but again-- someone could have communicated that to me.
I spent a lot of time on a lot of web sites, in these forums, and digging in the code before I asked the question. That's how I got everything else to work the way we wanted.
Regards.
-jcv
Slipped through the cracks?
Honestly, I think the lack of response here is just a fluke. =-\
Sometimes I make posts that for some random reasons scare people away. It's some combination of post verbiage, how quickly people can mentally identify the problem, and whether Saturn and Neptune are in conjunction.
In any case, the #drupal-support channel on irc.freenode.org seems (to me) to be the preferred venue for support; it certainly has been nothing but effective for me, whereas with the forums you can't keep poking people until they speak up. ;)
NOW, as to your problem -- and I think this might be part of why you haven't gotten responses -- I can't duplicate it. I click on any forum's heading and it displays only that branch of the hierarchy.
Now, you're referencing paths like /container 1/forum 2/subforum 3. Are you using pathauto for that? If so, can you look up the URL alias and tell me what those paths are referencing?
Hope you haven't abandoned ship completely yet, =-\
SFT
Oops, you're talking about
Oops, you're talking about the menus. I can't read, either.
One moment please... *elevator music plays while I experiment*
Okay, I've found the code
Okay, I've found the code responsible for that menu. I could hack either of your solutions in -- solution 2, obviously, is the easier.
And as the guy below said, if you want to restrict certain forums to certain people, taxonomy_access will let you do that easily. If all you're going for is the illusion of separate forums... ...then that's what makes it tricky.
Let me know whether you're going to stick with Drupal, and if you are I'll hack something together.
SFT
Thanks SFT
I just wanted to thank you again publicly. I appreciate your efforts, but as mentioned, I won't be needing the code.
Thanks.
-jcv
Well, some of us have spent
Well, some of us have spent months and years with drupal and haven't regretted it because all the shortcomings, perceived and real, are being addressed one by one.
I am not a programmer, so there may be more to your query than what I can understand, but, if all you want to do is to limit specific forums to specific people, all you need is taxonomy_access module. And, when those people access those forums, the drop-down will display only those forums to which they have access.
If I haven't understood your question, you can ignore my response.
Thanks.
That isn't quite what I was looking for, but thank you for your effort.
-jcv
Thanks for the respones.
I no longer need the code-- don't waste your time trying to help me out, but a sincere thank you to those that have made an effort.
I'm not the only one making the decisions here-- we're moving away from Drupal for reasons already mentioned and a few other shortcomings.
I knew it had potential-- that's why I recommended it in the first place.
-jcv
Then what?
jcv,
I applaud you for "following" up on your posts - contributing feedback to the "community" even though you're moving on.
I would like to know what CMS environment you are moving TO, and what you are moving FROM. (in use today, prior to exploring Drupal)
If you would, please cite the TOP 3 requirements supported by features of the CMS you are moving too. Also, what were the TOP 3 requirements that led you to select Drupal in the first place.
Thanks.
I was curious if this could be done
Since no one answered the question I was curious about if it could be done. I don't think you can do this with phptemplate.
Commenting out this (line 529 ?) in the forum module will remove the drop down.
After that it gets to be very difficult. I can't really see a good place to change the list. The array in the above snippet does not seem to really be an array. I tried to explode it and got nothing. The code leads to the taxonomy module.
The only thing I could get was that it is possible to build your own dropdown by using the taxonomy functions for getting a the parent terms for where you are in the forum and then use another function to get any children from that point.
You are going to need someone that works with the taxonomy module. But since you don't need the code now I guess I will put on my jacket and be off to school :)
It can be fixed
If still the problem is not solved, please contact me, I can fix it.
Thanks
http://rareservices.com
------------------------------------------------------------------------
Interested in Oraganic Group , Module Developer, having experiance in Installing and customizing drupal several times
Here is my experience with your quesiton
From my point of view, I commented here on your post.
--
Drupal development and customization: 2bits.com
Personal: Baheyeldin.com
--
Drupal performance tuning and optimization, hosting, development, and consulting: 2bits.com, Inc. and Twitter at: @2bits
Personal blog: Ba
You are not alone
I am finding lack of support frustrating too.
I'm using Drupal with Postgres, and wishing I wasn't. If I could get some support in patching the bugs, things wouldn't be so frustrating but I've had no help at all. No response even when I posted a patch to fix one of the more severe bugs.
Now that is totally different
That is a totally different matter.
You see: Postgres is not widely used in the Drupal community, just like using Drupal with IIS, ...etc.
So the pool of people who know it is much smaller than the total pool.
Add to that they are (like everyone else) busy, overloaded, ...etc. and you see why you are not getting responses.
As far as I know, Cvbge is the Postgres maintainer (of sorts). Try contacting him and pointing him to your patch and see what he says. I am sure he will answer you.
--
Drupal development and customization: 2bits.com
Personal: Baheyeldin.com
--
Drupal performance tuning and optimization, hosting, development, and consulting: 2bits.com, Inc. and Twitter at: @2bits
Personal blog: Ba
Then drop official Postgres support
The problem is that Drupal claims to support Postgres (and to be fair, if you leave caching off, it will even work more or less out of the box if you don't use any contributed modules). The truth is that if you can possibly run it on MySQL, you really need to go out of your way to set it up this way.
My own site runs on Postgres (because everything else that uses a database uses that), but it's been a non-stop fight, and I've basically had to give up on access control (and that actually caused me a serious problem recently, forcing me to completely remove a huge chunk of content), caching, and custom node types completely, while spending a huge amount of time fighting to keep the basics running smoothly. If I hadn't been a coder, it would have been a complete loss. There is usually some breakage with every upgrade, as well, and worse, it's usually related to gratuitously nonportable code (good grief, people, what do you really gain by using
integer(11)instead of just the standard SQLintegerorKEYinstead of the standardCREATE INDEX-- and don't get me started onREPLACE INTO).If I had known about this in advance, I either would have made a point of running MySQL and Postgresql side-by-side (which strikes me as a massive waste of resources, but a heck of a lot less work than trying to keep Drupal running on Postgresql), or gone to a different CMS entirely. This is one of those things that should be plastered in big warning letters all over Drupal: Postgres for devs only! Not ready for production use!
(Yes, I'm immensely frustrated. Why do you ask?)
It is up to the community
It is easy to drop support for Postgres and be done with it. That is the easy way out.
We prefer that we keep it as a best effort thing. There is a maintainer, and some commercial sites using it.
It is up to those who use it to submit patches and keep it going. The rest of us who use MySQL cannot say they want it dropped, nor can they help by patches, since it is out of their domain.
Yes, most contributed modules do not work with it, but that is a side effect of it being less used that MySQL.
So, if you have issues, please log them. If you have patches, please contribute them.
Signup for drupal-devel mailing list and ask to be part of a yet-to-be-formed Postgres team or task force to address all these issues.
--
Drupal development and customization: 2bits.com
Personal: Baheyeldin.com
--
Drupal performance tuning and optimization, hosting, development, and consulting: 2bits.com, Inc. and Twitter at: @2bits
Personal blog: Ba
My problem...
... is not so much that it doesn't work, as that it doesn't work and claims that it does.
To be as blunt as possible, lying to the user is bad, and doesn't exactly contribute to Drupal's reputation.
I have, in fact, been submitting patches and filing issues. Some of those issues have been languishing for many months now, with no fix in sight.
Explanations
I am not trying to make excuses, but rather offer rational explanations.
What has happened (and others who are more versed with Postrgres can chip in) is that Postrgres was fully supported at one point (4.4 I think?). We also supported MS SQL as well.
The maintainer was too busy, moved to other projects, ...etc.
Just last month, there was a discussion on getting an official maintainer for Postgres in Drupal.
So, your patches may not have gone to anyone who can do much about them in that period.
What I suggest is to go dig up your patches, and send the URLs to the drupal-devel mailing list asking the Postgres maintainer to review them. You can refer him to this discussion as well.
I know it is frustrating to run against a wall, but that is not intentional, and a little communication ought to clear it ...
--
Drupal development and customization: 2bits.com
Personal: Baheyeldin.com
--
Drupal performance tuning and optimization, hosting, development, and consulting: 2bits.com, Inc. and Twitter at: @2bits
Personal blog: Ba
then contact the maintainer
He is listed in the maintainters.txt in the Drupal download:
http://cvs.drupal.org/viewcvs/drupal/drupal/MAINTAINERS.txt?rev=1.7&view...
and checking CVS logs, it appears we have a new one:
http://cvs.drupal.org/viewcvs/drupal/drupal/MAINTAINERS.txt?rev=1.7&view...
I believe he is one of a limited number of individuals using postgre and they tend to test core and what few contrib modules they use.
You yourself indicate that Drupal core did work in a previous post
so I am confused that your second post says it doesn't. To be blunt you are now confusing and well, inaccurate as well as mildly rude with the labels.
Contrib modules are contrib modules and what standards they are tested against are entirely the responsibility of their authors.
-sp
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide
I said 'more or less'
... and the nuance was deliberate, and entirely accurate.
Caching is completely broken and has been at least since 4.5.0, the forums are generating SQL errors any time they are accessed (a problem new to 4.6, I believe), and the node access API appears to be broken, and has been since 4.5. These are all issues with core, and all of these have had issues filed.
Also, there's the small matter that Drupal is of extremely limited utility without the contrib modules. (Seriously, how many people in this thread are running a site with no additional modules? Anyone?) If a module is nonfunctional under a theoretically supported database, it would be very helpful to have a way of clearly tagging it as such. Perhaps rather, tags should be kept of which databases modules are known to support, sortable by such, and caveat user if you want to pull something from another category. This would give a fairly quick overview of exactly how much functionality you'd lose by going to a different SQL backend.
Now as to getting the bugs to the attention of the right person, I'd been under the impression that the correct method was to file issues and let the bug tracking system make sure that things got filtered correctly. Should I be going through the bug list and sending the node numbers of any Postgres-related stuff to Cvgbe? I can't assign issues to him directly. I'd also like to avoid having him get spammed by everyone with a Postgres problem in a Drupal core module, unless he's agreed to such in advance.
I understand what you are
I understand what you are saying. I meant you should send Cvbge an email with his contact form.
I am absolutly sure that he would welcome any help and assistence in working on this (as the new maintainer especially). Together, you guys could combine resources and bounce the best approaches off of each other and what other postGRE users he is already aware of.
-sp
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide
Bitching will not solve your problems
Seriously, bitching about the lack of help from a group of volunteers will not solve any of your problems. Have you ever dealt with a volunter community??? I don't think you have. How much did you pay for Drupal? Nothing. So, don't expect people to move mountains just because you wish it. My experience with people here has been nothing short of fantastic! At the very least, people will point you in the right direction and it's up to you do something about it. If you want real support, pay for it. There's plenty of consulting companies out there that will provide that kind of service.
As for moving to another platform, good luck. I've used 3-4 CMS systems in the past and Drupal is by far the most complete and easiest to use.
Drupal Rocks
I have used several CMS systems and have done my research with each one. Drupal is by far the easiest and best supported. The code is clear and well thought out.
This guy is obviously trolling and does not deserve the time that has already been put in to this discussion. Does he really think he would get any positive feedback from that last post?
If he can find a free CMS system with better support than we have here, then I need to know which one it is so I can test it out.
Thats very true, there arn't
Thats very true, there arn't many free CMS's that have the quailty (especially its template engine) of Drupal anymore.
----
Play Addicting Online Games