Delphine Masse

With the Deluxe GoDaddy hosting account, one  can host as many sites as desired, each in their own subfolder.

I had a blog, previously in its subfolder (www.mysite.com/folder/) and set that folder to be the new site (www.folder.com). Only, when I went to the site, it would redirect me to the root of the site (www.mysite.com). I looked at the mod-rewrite syntax and it seemed ok… wp-config.php did not have an option for setting the root address.

The solution was to login to wordpress and to change in settings->general settings the Wordpress address and the Blog address to be the new site.

The only thing left was to change any hardcoded hyperlinks!

In a page I have a drop down menu (in the #header div) and a h2 title (in the #content div, which is separate from the #header div).  Somehow, adding "position:relative" to the h2 will break the layout of the drop down menu.

Continue Reading »

The issue: The clickable area of some of my menu links (but only the first level links! Second level and h2 links worked just fine…) did not include the link’s padding. So the clickable area was very small even though the hover effect worked in the entire area.

The solution:  make sure the link has "HasLayout=true". Here is a demonstration of the influence of HasLayout on clickable areas.  An easy way to fix it is to set the height of the offending item to 1%. In my case:

#primary-nav li a { width: 1%}

A GoDaddy linux Virtual Dedicated Server (Plesk) that I am managing recently had the most unsettling problem. It acted as if there was no more disk space, even though it was only half full. All Inodes were full, but deleting files would only make the _total inode count_ decrease. So if resources were freed up they would then disappear, until there were no Inodes available.

Continue Reading »

Three options:

1. install from scratch, copy & paste (horribly time consuming if your site is complex)
2. save database, upload all files, create database on GoDaddy server, update config.php to reflect new settings. I tried that and somehow it didn’t work. I think the problem was root_path in config.php - it should not be /mysitename/mycmsmsfolder (or whatever your file directory may show when you view your files) but instead it should be something like :
   /home/content/a/b/c/yourusername/html/yourwebsitename/yourcmsmsfolder- Replace “a/b/c” with the first three letters of your godaddy username, and “yourusername” with your godaddy username
3. Take the middle road and run install with your new, transferred database (as in 2.) but do not worry about editing config.php. Check off the “create tables” and “install sample content” boxes. This is what I ended up doing and how I realized the root folder was not /mysitename/mycmsmsfolder but /home/content/a/b/c/myusername/html/mysitename/mycmsmsfolder

I’ve recently started using CMS Made Simple as a content management system. They focus on simplicity but still offer a blogging engine, which I wanted to try out. Well, in other CMSs you can just go to mysite.com/blog and see it, not here. So here are the steps to being able to access your blog in CMS made simple:

1. Make sure it’s installed (it was by default for me) - if not, check the modules section and install.
2. Create a post:
   1. Go to content -> Blogs made simple
   2. Create a new category (e.g. “general”)
   3. There will be a new tab called “entries” - go there and create a new entry. Write whatever you’d like.
   4. In blog-> settings, set the CMS alias for blog-rootpage to something meaningful, like “blog”
3. Attach a stylesheet to the blog module: this allows CMSMS to know how to display the blog.
   1. Go to layout->stylesheets
   2. Click on the yellow CSS icon for the “Modules: Blogs made simple” line
   3. Select a stylesheet to attach and submit (this should be the one corresponding to the page where you’ll show your blog, most likely similar to the rest of your website)
4. Create a page
   1. Go to Content->pages
   2. Create a new page and make sure it’s alias is the same as the one you set in the blog settings page, i.e. something like “blog” (you can set the alias in the “options” tab)
   3. Paste in the content the following tag:

{cms_module module=’Blogs’ }

The tag can also include parameters too.

Now you can go to mysite.com/blog and see the blog posts!

Well I guess it has to start with this blog… even though the pretty permalinks work on one of my other wordpress installs on this server (delphine-masse.com/nausicaa), they have not worked on the last two installs I’ve done (delphine-masse.com/SE, and this blog).

CodeRazor, as well as clueyblog say it might be some server caching problem (i.e. it works after a while), and other posts are conflicting. I’ll wait for a bit to see if this fixes itself.

– update: Maybe half an hour later, it works! Took a little longer than the other bloggers mentioned.

This is a work in progress, but I needed a spot to centralize portfolio/resume materials,  various training materials I’ve developed over the years, and install notes on the different systems I’m working with (Wordpress MU, Moodle, Plone, Drupal).

Custom design coming soon, but clients and school come first…