I am about done with fighting this piece of crap CMS that all you say is so great. I can not get blocks not to show or to show based on the spec in the hand book. I get no SEO after 12 weeks, and you guys make wise ass remarks instead of helping. I have posted help and How to questions and get no or maybe 1 response.
I am a business person not a tech dweeb, I can read and I do follow instructions. My site is www.dataforceone.com
So if you can and will, please help:Why can I not get a block NOT to appear on a page? Or to appear on a page only. does not work, the node ID does not work. I can not get blocks to show and/or not show
How are you supposed to post a calendar event so a user can see an activity?
How do you get a form to work?
Why do my edit screens go off the screen making it impossible to make and edit? Forcing me to scroll and scroll?
J
Comments
Dweebs
> I am a business person not a tech dweeb, I can read and I do follow
> instructions. My site is www.dataforceone.com
Not to offend, but perhaps you should consider having a technical person ("dweebs", as you lovingly put it) to handle the setup of Drupal, since you seem to be having difficulties.
--
Douglas Muth, Philadelphia, PA
http://www.claws-and-paws.com/ (Soon to be Drupal-powered!)
I feel your pain.
I am not a tech dweeb either and Drupal isn't for the faint of heart. I'm still slogging.
Take a deep breath, grab a beer and start reading the manual.
I know it sucks, but that's how it is.
I have been richly rewarded for my dedication to Drupal. In the long-run, you will thank your lucky stars that you stuck with it.
As far at the blocks go: Do you have the checkbox on?
As far as the SEO: It's possible you are still in the Google sandbox.
As far as the calendar: What theme are you using? I know in Goofy, you can barely see the diference when an activity is scheduled.
As far as everything else: Consider hiring one of the dweebs.
Working on it!
Thanks for chipping in, brainshrub.
The Drupal handbook is packed with information that sheds light on Drupal's trickier aspects. It's important to note, though, that the handbook is VERY much oriented towards 'reference' and not 'tutorial.' A number of active Drupal developers are working on improving the handbook and its organization, and assorted projects are springing up to produce training and tutorials.
Naturally, all of those involved are volunteers -- same as the developers working on core code. ;)
--
Jeff Eaton | I heart Drupal.
--
Eaton — Partner at Autogram
thank you...
thanks for your reply
dweebs is not derogatory... thanks for response..Is manual..
the hand books.
Yes I do have the check box on and have tested both the show block on listed pages and not on listed pages.
I am testing different themes and if you have a suggestion that will enable the calendaring and or showing events,that would be great.
My tech team set up drupal, by the way.
What is the sandbox?
can you recommend a drupal person that I can hire to help?
not derogatory?
Let's see some definitons:
but I repeat, I have not banned you for calling us this but because you called g.k. something very rude (but have no fear, g.k. is banned, too -- I do not care whether I agree w/ someone, certain kinds of language is not tolerated here).
--
Read my developer blog on Drupal4hu. | The news is Now Public
--
Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.
trolling
Just so you know, us dweebs frown upon using deconstructive criticism to get attention. We even have a word for such obnoxious whining: "trolling."
I think this guy needs to be
I think this guy needs to be banned. This is the most intemperate language I have seen on these forums in the last one year.
Some clean up
I blocked two users (among them the original poster) and removed two comments. It was *not* because calling us dweebs or trolling but because they used rude words to describe the next user. Be civil or be banned immediately.
Because the original poster raised valid questions, I have not yet removed the whole node, but rest assured, it'll be gone in case of need.
--
Read my developer blog on Drupal4hu. | The news is Now Public
--
Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.
OK you seem to be reasonably knowledgable..
Do you have any suggestions to the challenges the guy is having?
Sorry
I do not do newbies, especially offensive ones. There are 46K users on Drupal.org , I leave this task to them.
--
Read my developer blog on Drupal4hu. | The news is Now Public
--
Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.
not really
he provided insufficient information and his original post was not one that I cared to spend time on. I have decided that rather than 'get into it' with everyone that posts questions leading with insults and name calling, I will ignore them. He doesn't pay me and I can better spend my time on things like the handbook that better benefit the entire community.
Evidently I missed a nice little flame fest too which is a good thing.
-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
Sepeck is right. He allowed
Sepeck is right. He allowed his emotions to get the better of him and ended up posting without clear information. Anyhow, I will try this as it might help someone:
The trick seems to be to configure the block *first*, save its configuration and then come back to admin>>blocks, enable it and save the configuration *again*.
Most people (including me initially) enable the block first, then go to configure, save it and expect to see the block working. This doesn't work.
Also, whenever a block has not worked, I notice that I have done something foolish like choose the wrong visibility setting. That is, I may choose "Show only on listed pages", but put the paths for "Show on all pages except the listed pages".
What is missing from all this is the stuff like blog* etc. If you put the wrong paths here, the blocks will obviously not show up. Had the poster been more clear on this (and a lot more civil), he would have most probably got an answer.
Edit: I suspect that even if people choose the second method above (enabling the block first), it would work provided they remembered to go back to admin>>blocks and save the configuration again. I am writing this off the top of my head, so please feel free to correct me if I am wrong.
Block bug??
If you have an enabled block you can configure it as many times as you want. It'd be a very serious bug if enabled blocks could not be configured, but they can.
--
Read my developer blog on Drupal4hu. | The news is Now Public
--
Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.
Thanks, chx. This is the way
Thanks, chx. This is the way I remember it working and I spent hours trying to figure out what was wrong before I tried the other method. But I will test it again and submit an issue if necessary.
hmmm
"piece of crap system"
"dweeb"
[Edit: after removing their original, some real ugly quoted text deleted by chx]
And you wonder why nobody really feels like helping you, when they could just spend that time helping someone likely to be more appreciative of their efforts.
--
Anton