Help me build my own website

Status
Not open for further replies.
cpanel.jpg
Is this where you made the changes?

If you have modules like pathauto installed, then run cron and see if that changes anything.

- - - Updated - - -
@blkrb0t

Try clearing your browser cache, or using a different browser and see if that changes anything.

Whats your site address?
 
Last edited by a moderator:
ch@ts said:
View attachment 16157
Is this where you made the changes?

If you have modules like pathauto installed, then run cron and see if that changes anything.

- - - Updated - - -
blkrb0t

Try clearing your browser cache, or using a different browser and see if that changes anything.

Whats your site address?
Click to expand...

No, I didn't add through sub-domain. I did it through permanent redirection through my cPanel. I will PM you my website address.
 
Do it through here, and remove the redirection.

- - - Updated - - -

Also, if you can host more than 1 domain on your server, then do a drupal multi-site setup.

You can use it for any sub-domains you create as well.

What you need to do is create directories in the drupal/sites folder.
so you have
drupal/sites/default (your current site)
drupal/sites/subdomain1.webaddress.com
drupal/sites/subdomain2.webaddress.com
drupal/sites/nextsite.in

etc.

That way you can run multiple sites of the same code base, and share tables (for users for example, so that people don't have to register separately on all your sites) if you want.

Just point all your domains and subdomains to your drupal directory. (public_html/drupal)
 
I think for your main parked domain you cannot change the root directory.
it can be done only for addon domains and subdomains.
 
In that case he'll need to copy-paste the contents of the drupal directory into the public_html folder
 
ch@ts said:
In that case he'll need to copy-paste the contents of the drupal directory into the public_html folder
Click to expand...

So I just copy all the contents of my Drupal directory into the public_HTML directory? What should I do with the original Druapl directory then? Delete it? Or just keep it as it is?
 
I've deleted everything now. Have made a support ticket to reset all my data and settings. I'll start a fresh install again. Will install directly into the public_HTML now.

- - - Updated - - -

Reset everything and installed Drupal directly into the webroot this time around. The basics are covered for now and everything working as intended.

Now that I have installed I need help with what to do after installation. How do I customize the site according to my requirements? I want to add a website header and different background. However I am confused with the themes and modules as of now and how they interact with each other when it comes to how my site functions.

These are things I want to add: A home section(that displays everything on the site in some order), a Blog section(for all my blogs), a Photography section(kind of a gallery, with the option of adding some text at bottom for each image), and an About section.
 
Facing a problem of another kind since the day I got my hosting. At first I thought it was some problem with my hosting. I can't access my website for sometime, say for an hour after every 4hours. The website is down only for me, it works fine through a proxy service like anonymouse. It works fine when I check it on 'down or not' too. The problem is from my end, something to do with my DNS I guess, though I'm not sure. How do I fix this problem?
 
Changed to google DNS, everything fine so far. Still learning the ropes around Drupal.
 
I'm having problem with memory_limit. When I try to access settings of any new theme I install, or when I try to install new module on Drupal. Example of error is as listed below.

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 29843 bytes) in /home/salmania/public_html/includes/common.inc on line 5885
 
It seems like your php mem limit is only 32mb.
Drupal can work on that, with quite a few modules enabled, but you've got to be choosy.
Disable modules you don't need before installing new ones, or ask your host if they can up the mem limit.
 
@blkrb0t

You on hostdime right?
The allow custom php.ini based on the chat i had with the live support..
Also I got shared hosting from them yesterday, and they do support it.

Just do these steps:

go to your public_html (or www.. they are the same) and create a file with name php.ini
place this line in it

memory_limit = 96M ;

and then try it out again.

- - - Updated - - -

P.S. why do i not get emails when something has been posted in this thread?
 
Last edited by a moderator:
techygeek and @ch@ts I tried asking them about this problem yesterday and also made a support ticket. They told me that as I'm on shared hosting my memory will be limited and I'd have to go for VPS or dedicated hosting if I wanted more, but they did increase mine from 32MB to 64MB, after which I'm able to access the theme settings again now. Can I just make a file like what you've said and increase my memory limit? I thought the web host admin had that power and not the shared user. If at all I enter into such a problem in the future, I can try what you've said, for now 64MB is doing fine.

And I need some help with theming. After much experiments, I've decided and installed the Omega base theme and am have created a sub-theme with it's HTML starter kit, as said in its handbook. However, the documentation looks too technical sometimes and am not finding some aspects of it comfortable. Can you show we towards any beginners guide from which I can learn?
 
Last edited by a moderator:
@blkrb0t
Yes that did work. I did that on the shared hosting i got from hostdime yesterday to see how the servers are. I am running on 96M as memory limit.

- - - Updated - - -

Regarding the sub themeing.

There will be a starter theme in the omega folder. copy it outside the omega directory

rename all instances of the theme name with a name you desire. (rename files, also do find and replace inside .info and template.php)

and then use it as your theme. basically u get everything from the core theme. now add css to style and if you need to alter the html then copy the template files (*.tpl.php) from the core to the sub theme and then edit it.
 
Last edited by a moderator:
@techygeek I've made my sub-theme with the starterkit HTML5 theme provided and have renamed all instances and done all the other basics like renaming .info file, unhide it from Appearance menu. I couldn't get the third point you said - about CSS and HTML, how should I go about them?
 
Last edited by a moderator:
You so subtheme is your theme
core theme is the base omega theme ok.

in the subtheme if you have any css file then that is where you put your custom css to style your page. (many things can be done by only css) . if there is no css file let me know. I wil tell you how to add

however if you want to edit html structure then you will need to edit the *.tpl.php files.
There wil be lot of tpl.php files in the core theme. based on what you want to change you might need to edit one of those. but follow the golden rule do not edit anything in the core theme. So copy the file you want to edit to your subtheme. and then edit them. after adding any tpl.php files to your subtheme make sure you clear theme registry (by doing a save configuration button at the appearance page even if you don't want to make other changes)

I am not really good at explaining via text. So if doubts ask again.

P.S. Tip: download and install the adminisration menu module and disable the default toolbar module for a better admin toolbar that comes on top. Its really very good.
 
I'd suggest you use the Zen theme for now.
Omega's good, but Zen will be easier to customise. All the values are there in the starter kit, you just need to add your css to the elements you want to customise.

You can always move back to Omega once you've got the hang of things.

If you're sticking to Omega, then you can override the Omega default css by copying the values you want to the global.css file, and putting in your own code.

For example: in the omega-text.css file you've got the "body" class. Copy that to your global.css file, and put in your own code. Do it for all the elements you need.

I don't know if there's a better or more correct way, but this is how I've been customising Omega.
 
Status
Not open for further replies.
Top Bottom