1
spudrussell
Re: SEO hack for CBB v3.08
  • 2008/6/13 21:27

  • spudrussell

  • Just popping in

  • Posts: 7

  • Since: 2005/6/27


This post was a lifesaver. I moved hosts and my forum broke. Nothing seemed to revive it. Then I found this hack. Now my forum is accessible again. Thank you. Thank you.



2
spudrussell
Re: site bookmarking
  • 2007/12/21 2:41

  • spudrussell

  • Just popping in

  • Posts: 7

  • Since: 2005/6/27


Of the two,

http://www.xoops-magazine.com/modules/wordpress/new-module-social-bookmarks/

is by far the better one. The first one is not a true module, has only a handful of social sites and not all of the major ones, and requires customizing the theme. In my incompetence, I failed to get it to work.

Then, I tried the one at xoops-magazine. It is a real XOOPS module, supports about 20 social sites, and requires very little administration. You just choose where you want to put the block.

If you want to reorder the listing of social bookmarking sites, then just reorder the list in this file:
/modules/social_bookmarks/blocks/social_bookmarks.php

If you want to see it working, I have it in a lower left hand block on all pages of my site, The Skilled Investor.

By the way, you will need to register first at xoops-magazine to download it. The site is in German, so click the small British flag, if you want English.

... a very nice module with the best icon that I have seen yet in the XOOPS system administration window. A big thanks to Rene Sato for this one!



3
spudrussell
Re: Correct syntax for the XOOPS Virtual Path (URL) during installation?
  • 2006/11/14 18:28

  • spudrussell

  • Just popping in

  • Posts: 7

  • Since: 2005/6/27


Lance,

Thank you for the suggestion.

Unfortunately in my hosted environment, the suggested XOOPS Virtual Path (URL) was not accepted as valid by the XOOPS installer.

I used normal URL syntax, which was accepted as valid by the XOOPS installer, that is:

define('XOOPS_URL', 'http://www.mysitename.com');

Is there any downside to using this statement?

Thank you to anyone for advice.



4
spudrussell
Correct syntax for the XOOPS Virtual Path (URL) during installation?
  • 2006/11/11 1:46

  • spudrussell

  • Just popping in

  • Posts: 7

  • Since: 2005/6/27


What is the correct syntax for the XOOPS Virtual Path (URL) during installation?

I am installing on a multi-user hosted server. In searching through this site and the XOOPS documentation site have seen a variety of expressions, but not a definitive answer. Sometimes I see a directory path -- other times a www.yoursite.com style URL. Which is correct?

Would the following work on a new installation of XOOPS 2.0.15 on a hosted environment?

http://localhost/public_html


Thank you for your advice.



5
spudrussell
Re: My "how to update a theme" school of hard knocks process
  • 2006/6/19 16:59

  • spudrussell

  • Just popping in

  • Posts: 7

  • Since: 2005/6/27


One thing I forgot for this list:

Do not change the folder name of your new theme directory. The name matters, including the case of the letters. If you change the directory name without making changes to other files (which I do not know or want to know how to do), XOOPS will lose track of your theme and other problems will ensue.



6
spudrussell
My "how to update a theme" school of hard knocks process
  • 2006/6/18 20:19

  • spudrussell

  • Just popping in

  • Posts: 7

  • Since: 2005/6/27


After what seemed to me as far too much stumbling around, I got a new theme working. From this forum, it seems that others stumble around and hit walls, too. This post summarizes some steps that might make it easier for others. Note that I was starting with a working site that had a working theme. I wanted to add a new theme and eventually ditch the old one, but the process turned out to be quite painful.

Here is the process I worked out via trial and error. Please correct anything. Some steps can be taken in a different order:

1) back up your working site and database(s) for disaster recovery
2) make sure all templates (not themes) are generated (system admin - template - then generate)
3) clone the default template set and switch to it (system admin - preferences - general-edit - select your clone as the "default template set" and submit)
4) download a theme from whereever to your local machine, unzip, read instructions if any, upload to your server themes directory. Your new theme file should have a similar file structure as other installed themes. Make sure permissions are the same as other installed themes. (Wrong permissions can cause the dreaded white screen.) I use Filezilla for FTP and chmod -- With Filezilla select a theme folder on the server - right click - file attributes - 755 I think is correct. (Everybody can read and execute and only you can write.)
5) make the new theme potentially useable (system admin - preferences - general-edit - Make two changes: A) turn "Update module template .html files from themes/your theme/templates directory?" to "Yes" -- This lets you see changes. and B) select your new theme under "Selectable Theme" -- However, make certain that your stable working theme is also selectable. (You want to have access to both. If you don't allow your stable theme to be selectable, you can lock yourself out of your site with the dreaded white screen.) Also DO NOT change you default theme to your new theme until the whole process is done and until you are sure your new theme is solid. Then, submit.
6) configure a viewable theme selector on your anonymous user front page (system admin - blocks - anonymous user top page - themes block visible - with a high weight so it is way down the page and most users will not see it if your site is live - then submit) This gives you a way to back out of trouble and get back into your site. Since your stable theme is still default, you can bring up a browser and go to your site and your stable theme will show. Next, you can select the new theme from the selector box on the anonymous user front page. If your new them shows, that is goodness. If it is a vast blank white space, you should be able to use your browser's back arrow to get to your old theme and then log in as admin.
7) To ensure that your changes show on your site, some advice tells you to dump your server XOOPS "template_c" directory (Do NOT delete index.html). These are your site's auto generated complied templates. Seems not to hurt to dump them, because they are automatically generated in response to users' clicks on your website.
8) Make your theme edits. Protect yourself by editing copies of files and not writing over the only copy of theme files that you know work. (There are many ways to do this.)
9) If your changes still do not show on your site, then flush your browser cache, and hopefully they will.
9) When everything is pretty and stable, then you can make your new theme your default, turn off the "Update module template .html files ..." and get rid of the theme selector on the anonymous user home page.

Also for general information, read the "Themes- Styles and Templates" forum at
https://xoops.org/modules/smartfaq/category.php?categoryid=17 , see some nice tutorials at
http://www.warpigw2.com, and check outhttp://www.macambridge.com/dummies/

Hope this helps...




TopTop



Login

Who's Online

166 user(s) are online (105 user(s) are browsing Support Forums)


Members: 0


Guests: 166


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Apr 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits