New Site Woes
I've taken over a website for my fraternity. I'm not very qualified to be doing so but I am the only person that stepped up. I've got a general question and a more specific question.
First, my knowledge of html and Drupal is limited. I took joke classes of Visual Basic, html, and java in school. I've built a few web pages on my own with geocities and frontpage. I'm majoring in engineering so I don't really have time to get fully educated with html and drupal to make an amazing website. What I do have is time and knowledge to make it a functioning website that serves its purpose to get information to members, alumni, and potential new members. How user friendly would you say drupal is? I've already gone around and taken the time to upgrade all the information on the site that was over a year old including the membership, contact info, news, etc. I just installed my first module and I'm getting crazy crap all over the site. This leads into my more detailed question..
I just installed weblinks module, my first module here: http://www.ruskullhouse.com/ and now there are a bunch of errors at the top of the page. I installed it in html/modules/weblinks and the weblinks stuff is showing up when I try and add content but I still have errors all over the place. Did I install it wrong, is there something I'm missing?
=-=
if your not customizing drupal for a full blown web application, drupal is user friendly.
Looking into the warning: you are getting now. Looks to me like something isn't correct with PHP
what is your environment setup?
version of Apache?
version of PHP?
=-=
Seems similar to this:
http://drupal.org/node/36148#comment-68569
It seems related to Token
It seems related to Token module... technically if Weblinks requires Token to work it shouldn't let you install without it, though there's a chance it wasn't coded to do that. Try installing Token and see if that helps (unless you already have it, which you may since it is required by a variety of other modules).
Also, you should migrate all modules out of the core modules folder. Leaving them there "technically" does work, though makes a big headache during upgrades. The correct location for them is sites/all/modules (you need to make the modules and themes directories within "all"). This way you can upgrade Drupal much easier without worrying that some of your modules will get misplaced (your sites folder is left alone during upgrades... you just delete all the rest of Drupal but leave sites alone, then replace the rest of Drupal... then Drupal is upgraded and all your own stuff is still separate and safe). I'd suggest that to move the existing modules, first put the site in Offline mode, then move the modules one or a few at most at a time (to narrow down problems if any arise). Test that the site still works, then do the next ones. Make sure you do "not" move any core modules though. You may be best off to extract a copy of Drupal on your desktop so you can see which modules should be there by default, and don't move those.
Hope this helps.
*Edit: Yeah what VM said... you may have a setup issue with the server handling include files. For info check http://www.google.com/search?q=php+failed+opening+for+inclusion
-- David
davidnewkerk.com | absolutecross.com
View my Drupal lessons & guides
Token is enabled and for
Token is enabled and for weblinks:
Web Links 6.x-2.0 Web Links provides a comprehensive way to post weblinks to your site. All links are nodes, which can be put into taxonomies/categories and administered.
Depends on: Help (enabled)
Required by: Google and Alexa Rank (disabled), Weblinks Blocks (disabled), Web Links Checker (disabled), Web Links Convert Janode Package (disabled), Web Links Convert Links Package (disabled), Web Links Convert LinksDB (disabled), Web Links Filter (disabled)
I feel a little stupid though in regards to the php.ini. Where can I locate this file?
Depending on your host (only
Depending on your host (only some give access to it for end users) you usually would (if allowed) make one in the root of your web directory... and it would be able to alter a variety of pre-selected PHP settings that the host permits. Other hosts may not allow this and you'll have to contact them to see about them making the changes for you. Or some hosts do it through your .htaccess file (which may not have as many possible options, not sure). You might want to just email them in either case and ask for confirmation about how to proceed (or check their site's knowledge base if they have one, which usually explains what to do about these sort of things).
-- David
davidnewkerk.com | absolutecross.com
View my Drupal lessons & guides
Location of module was the problem
I was the previous maintainer of that site, you nailed it with your comment about migrating all modules out of the core modules folder. It should have been put into /html/site/defaults/modules , not html/modules .
I doubt there was a PHP issue with includes, as other includes work just fine; more likely something to do with the module returning an incorrect path for the include statement (and obviously, PHP can't 'include' a nonexistent file).
And...
When you move the modules like that, each one will have to be disabled (but not uninstalled) and then re-enabled to pick up its new location.
BTW, Weblinks can use Token, but does not have to.
NancyDru