... by modifying a theme.
halp, what do I do? My job is in danger!!
Just kidding. I am evaluating drupal as a feasible CMS. So what I did was a fresh install, then copied over the garland theme files to sites/all/themes/garland-test/ and took it from there.
I then edited a few css files and installed the cck module. I began to like what I saw. Except that reordering fields in the cck input forms doesn't work.
I searched the web and found this: http://drupal.org/node/275931
I followed this link in the comments http://drupal.org/node/98253 because this is exactly what I want. Custom cck input forms. Except it doesn't work for 6.x. Drat.
Ok, so I tried to figure it out for myself. I read the documentation for the template system and (among others) this comment seemed to suggest the right thing: http://drupal.org/node/269319#comment-893493
So I looked for something like form.tpl.php somewhere to copy that to my sites/all/themes/garland-test/ folder. There is no obvious *.tpl.php file for forms though.
Well, I thought, no danger in creating one and having a look whats happening.
My was I wrong. As soon as I flushed he cache, my site was broken. Many admin pages are just blank now. Including the page where I can flush the cache.
Still I thought, no biggie, Ill just delete this file (sites/all/themes/garland-test/form.tpl.php) and I should be fine, right?
Wrong! Drupal now insists there should be a file ./sites/all/themes/garland-test/form.tpl.php and the install is b0rked. Great going.
So what database entry do I have to manually reset, alter or clear to get this site going again?
Oh and also: What is the rationale behind this? I can break my site install by making a simple change in the file system which I then cannot undo easily by reverting said change?
I don't know if I want this on a production site. Let me be clear on this: I didn't edit any core files. All I edited were files IN A COPY OF A TEMPLATE. This could easily have been a designer on a production website. THEN my job would be in danger (for choosing a system that allows this and not securing it against it).
But for now: Is this easily fixable (meaning no reinstall, or database drop). Just pretend (like me) I got valuable data in there.
Comments
=-=
Seems to me you can clear the cache tables in the DB to get rid of the problem.
or navigate to admin themes, set a new theme as default then switch back
just for the record or if it helps s/o else
clearing the cache tables did not help. I had tried that first thing, but no luck.
I solved the problem in the meantime with help from a post further down.
Probably just clearing the
Probably just clearing the cache data in performance settings will clear things up.
Dang nabbit, I keep cross posting on you VM, whats going on tongiht:)
Pimp your Drupal 8 Toolbar - make it badass.
Adaptivetheme - theming system for people who don't code.
=-=
were both just eager to help today! extra help is better than none, which the forum support seems to be accused of far too often!
Even when the lack of help isn't typically true.
...
Yea, I have some free time, amazing eh?
Pimp your Drupal 8 Toolbar - make it badass.
Adaptivetheme - theming system for people who don't code.
=-=
Feel free to whip me up a theme! : )
I'm in process of networking with local bands in my area and have taken on my first site pro-bono. Theming is my nemesis. I'm just never happy.
Sure, I'd be happy to, band
Sure, I'd be happy to, band site sounds like lots of nice graphics, which is my nemesis (takes me ages), but you caught me at a good time (nothing going this week), send me some details.
Pimp your Drupal 8 Toolbar - make it badass.
Adaptivetheme - theming system for people who don't code.
If I remember correctly,
If I remember correctly, just visiting the admin/build/modules page (or was it the admin/build/themes page?) rebuilds the theme registry.
If not, you can always add a
drupal_rebuild_theme_registry();temporarily in your theme's template.php file, while you are doing theme development.thanks cog.rusty
Visiting the admin/build/modules page fixed it indeed. Still scary though, because I can imagine s/o breaking the install later on in the same way.
I looked around everywhere and still have no clue how to go about customizing the cck input forms.
Its strange: the Drupal looks abyssmal to me. Seriously. Lots of information but all in loose strands, very version dependent, no hands on examples in the docs. The Api docs are good only if you already know whats going on as a reference, I guess.
Fex. finding out how to find out how these cck forms are created (which files are involved, where are the hooks etc. Can one get s.th like a call trace in php btw?) is next to impossible.
Forum response is excellent, though. So if you have useful pointers to what I have to read to see the light, don't be shy and hide them.
You mentioned reading the
You mentioned reading the documentation. Did you mean this
http://drupal.org/node/173880
and the other pages around that?
About breaking the layout later, it is better not to do any development work on a live site.
...as for that CCK design problem (!)
check out form defaults and form editor modules (one wraps cck fields in span or div for styling without touching templates, and without using content templates module) and the other allows for on-the-fly reordering of all fields in a form...VERY useful modules, the latter should be in core imho because about 90 million people want to know how to move stuff around on node edit forms (like move subscriptions above body but below title, but put og stuff at the bottom and so on - and when they are *not* cck items)
........................................................................
i love to waste time: http://twitter.com/passingnotes
thanks
> check out form defaults and form editor modules [...]
looking around on Google I found this: http://drupal.org/project/formdefaults
No luck with "form editor modules" though. Can you elaborate on this?
http://drupal.org/project/formdefaults seems a nice thing. But I guess if I decide on Drupal sooner or later I have to get my feet with the code, so: Where do I look for a hands on description of the code flow?
form defaults breaks cck field names
All cck field names get changed to the first cck field, whenever I edit one of the cck fields in a form.
Not good. Not ready for prime time. I guess the right thing to do now would be to file a bug. I have no Idea where and for which part actually (Drupal, cck or form defaults).
But since I doubt drupal is gonna make it as my CMS, I guess I just keep looking and pass this on to whoever feels interested.
Bug description:
System:
Drupal 6.6
PHP 5.2.6-pl2-gentoo
mysql Ver 14.12 Distrib 5.0.40, for pc-linux-gnu (i686) using readline 5.2
Linux 2.6.22-vs2.2.0.7-gentoo
additional modules:
cck-6.x-2.1.tar.gz
formdefaults-6.x-1.0
link-6.x-2.5
nice_menus-6.x-1.2
Description:
add a new conten type
add a few custom fields (cck) to it (among them a link)
edit one of the custom fields with formdefaults on the cck input form
-> all fields now appear with the same name on said form.
reproducible: always
please s/o send it were it belongs. TIA.