2
Within the xoops_data directory, I have the directories /caches and /configs. Within /caches I have /smarty_cache, /smarty_complie, and /xoops_cache and within /configs I have two files: index.html and xoopsconfig.php.
Are you saying to delete everything within the /xoops_data/caches/xoops_cache directory except for the index.html? OR ... in all subdirectories within /xoops_data?
Are you saying to delete everything within the /xoops_data/caches/xoops_cache directory except for the index.html? OR ... in all subdirectories within /xoops_data?
3
I can get to admin.php but all the Quick Links, including Prefs, all link to the old domain.
Hum ... I just looked at my site and realized only the Quick Links in the Admin area use the old domain. If I copy the Quick Link shortcut, paste it in the browser, chance just the top level domain name, it will load the correct page and the links within that page also link to the new domain. Interesting ... something in the code for the Quick Links must be off. Any ideas with this?
Hum ... I just looked at my site and realized only the Quick Links in the Admin area use the old domain. If I copy the Quick Link shortcut, paste it in the browser, chance just the top level domain name, it will load the correct page and the links within that page also link to the new domain. Interesting ... something in the code for the Quick Links must be off. Any ideas with this?
4
Great idea but unfortuantely I already canceled the old domain and no longer have access to it. It sounds like that probably would have worked. Any other ideas?
6
I changed the domain name for my xoops install, modified the mainfile.php and everything works great. I log into the administration area no problem. Once in the administration area, all the Quick Links in the admin menus are still using the old URL. Is there a file for the admin area that needs a code change with the new URL like the mainfile.php?
7
I have got most things worked out at this point ... at least the ones I know of ... except the JavaScript issue. Any suggestions on getting JavaScript implemented in the site would be helpful. I am not proficient enough to create this from the ground up so plan on continuing to use this one for now. 
8
I am assuming you mean in the theme.html doc because looking at the XOOPS Default Theme theme.html doc, it has <{$xoops_module_header}> in it. It looks like my theme.html doc is missing <{$xoops_module_header}> and possibly more crucial lines of code. Below is the entire Head section of theme.html. So ... do I just add <{$xoops_module_header}> within the head tag to fix the js problem? Thanks again!!
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<meta http-equiv="content-language" content="<{$xoops_langcode}>" />
<meta name="robots" content="<{$xoops_meta_robots}>" />
<meta name="keywords" content="<{$xoops_meta_keywords}>" />
<meta name="description" content="<{$xoops_meta_description}>" />
<meta name="rating" content="<{$xoops_meta_rating}>" />
<meta name="author" content="<{$xoops_meta_author}>" />
<meta name="copyright" content="<{$xoops_meta_copyright}>" />
<meta name="generator" content="XOOPS" />
<title><{$xoops_sitename}> - <{$xoops_pagetitle}></title>
<link href="<{$xoops_url}>/favicon.ico" rel="SHORTCUT ICON" />
<link rel="stylesheet" type="text/css" media="screen" href="style.css" />
<link rel="stylesheet" type="text/css" media="screen" href="<{$xoops_url}>/xoops.css" />
<link rel="stylesheet" type="text/css" media="screen" href="<{$xoops_themecss}>" />
</head>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<meta http-equiv="content-language" content="<{$xoops_langcode}>" />
<meta name="robots" content="<{$xoops_meta_robots}>" />
<meta name="keywords" content="<{$xoops_meta_keywords}>" />
<meta name="description" content="<{$xoops_meta_description}>" />
<meta name="rating" content="<{$xoops_meta_rating}>" />
<meta name="author" content="<{$xoops_meta_author}>" />
<meta name="copyright" content="<{$xoops_meta_copyright}>" />
<meta name="generator" content="XOOPS" />
<title><{$xoops_sitename}> - <{$xoops_pagetitle}></title>
<link href="<{$xoops_url}>/favicon.ico" rel="SHORTCUT ICON" />
<link rel="stylesheet" type="text/css" media="screen" href="style.css" />
<link rel="stylesheet" type="text/css" media="screen" href="<{$xoops_url}>/xoops.css" />
<link rel="stylesheet" type="text/css" media="screen" href="<{$xoops_themecss}>" />
</head>
9
Thanks so much. I did get everything to work ... check it out. It is very strange ... the only way I got the subMenu to padding-left to work was to repeat the code twice in the CSS file. I have not clue why this is but hopefully there will not be problems because of it. Thanks again both of you for all the help. 
Another question, although not related to my previous questions. None of the pop-up menus on my site work.
For example, when I am writing this post in this forum, above this text box is a title for the section called "Message" and to the right of the title "Message" are icons to add a link, email, image, image manager, smilies, code, and comment. In every situation on my site, when you click on these icons that are suppose to create a pop-up window, nothing happens.
Any clue on what could be happening here? Is there a preference setting I might have set incorrectly?
Thanks again.
Another question, although not related to my previous questions. None of the pop-up menus on my site work.
For example, when I am writing this post in this forum, above this text box is a title for the section called "Message" and to the right of the title "Message" are icons to add a link, email, image, image manager, smilies, code, and comment. In every situation on my site, when you click on these icons that are suppose to create a pop-up window, nothing happens.
Any clue on what could be happening here? Is there a preference setting I might have set incorrectly?
Thanks again.
10
Thanks again.
1) I got the align center to work.
2) I added the code:
#mainmenu a.menuSub, #system-block_mainmenu a.menuSub {
padding-left:20px;
}
but it had no effect. Am I missing something or did I put the code in wrong?
3) I think I did not explain this one correctly. I don't want the Main Menu to look different if logged in. The User Menu (once logged in) does not have a display: block like:
#mainmenu a {display: block;}
so the User Menu items do not text wrap. I am guessing I need to use similar code as:
#mainmenu a {display: block;}
but with an adjustment something like:
#usermenu a {display: block;}
but tried this and it does not work. Ideas?
1) I got the align center to work.
2) I added the code:
#mainmenu a.menuSub, #system-block_mainmenu a.menuSub {
padding-left:20px;
}
but it had no effect. Am I missing something or did I put the code in wrong?
3) I think I did not explain this one correctly. I don't want the Main Menu to look different if logged in. The User Menu (once logged in) does not have a display: block like:
#mainmenu a {display: block;}
so the User Menu items do not text wrap. I am guessing I need to use similar code as:
#mainmenu a {display: block;}
but with an adjustment something like:
#usermenu a {display: block;}
but tried this and it does not work. Ideas?
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | May 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|