61
technigrafa
Re: Need to display longer quote in Random Quote

Ok, answered by own question. Duh! Use phpmyadmin and look for xoops_citas and change the character length of the "texto" field to 600 or whatever.

Hope this helps someone!



62
technigrafa
Re: Need to display longer quote in Random Quote

*BUMP*

Anyone got randomquotes to work with longer quotes than 256 characters?



63
technigrafa
Re: Online course/teaching module - Help Please

Thanks guys!



64
technigrafa
Re: Online course/teaching module - Help Please

Are these modules still available? I tried the links above and both sites are down. I need a way to establish a homepage for each teacher at a school. I've tried "Member Hompages" but it is a bit too complicated for them. Basically, they just need a simply content module that supports a WYSIWYG editor that can be configured to give each user a page, or let users share access to editing a page. They also want a counter on each page.

Right now they are using TinyContent, but that means any user has access to any other user's page, and that is bad. And there is no type of counter.

Thanks!



65
technigrafa
Re: ERRATUM

Sorry for bringing this back from the dead, but I was checking out another site and noticed that even if I turn off javascript, the mailto: code is still there.

Did this get changed in a recent XOOPS update? I put an email address in as just text, no link, in the content module, and XOOPS converts it to a mailto: link. That used to happen, but when I turned off javascript, it didn't work, but now it still works without javascript/java on. Is is still safe from spam spiders?



66
technigrafa
Re: Rewriting module URLs

Okay, what if you want to rewrite so that any user visiting a particular module, such as liaise, gets https: and not http: and then if they leave liase, they automatically get http: back?

This is close, it makes any non-liase page go back to http:, but it makes my SSL break on liase pages, but only in Firefox:

Options +FollowSymlinks
RewriteEngine On
RewriteCond 
%{HTTPSon [NC]
RewriteRule !^modules/liaise http://%{HTTP_HOST}%{REQUEST_URI} [R,L]


I think it has something to do with the images referred to in the CSS of the theme? I tried hard coding all those to https, but that doesn't help.


So I tried this:
Options +FollowSymlinks
RewriteEngine On
RewriteCond 
%{HTTPSon [NC]
RewriteRule !^/*(^modules/liaise|^themes/themename) http://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]


Hoping to include anything in the themes folder as well as the liaise folder, but no joy. Still broken lock icon in Firefox Anyone know what I'm doing wrong here?


**Edited*/



67
technigrafa
Re: SSL problems

Thanks again.

I don't think this is what I'm going for. That changes http to https all the time.

I am saying this:

If SSL login is enabled in XOOPS and a user types in yoursite.com, but your SSL requires www.yoursite.com, the XOOPS SSL login won't work, unless the user manually visits www.yoursite.com (which is where they are authenticated to).

So I used mod rewrite to make any requests to yoursite.com go to www.yoursite.com, which is great, BUT if a user goes directly to yoursite.com/modules/news, my trick won't automatically change the URL to www.yoursite.com/modules/news

Does that make sense?



68
technigrafa
Re: Trouble implementing SSL login

I thought this might do it:

RewriteEngine on
RewriteRule 
^www.{REQUEST_URI}/$ {REQUEST_URI}$[R=301,L]


But no luck as for the longer URLs.



69
technigrafa
Re: Trouble implementing SSL login

Well,

This seems to do the trick in .htaccess:

RewriteEngine on
 
RewriteCond 
%{HTTP_HOST} ^www.domain.net/$ [NC]
 
RewriteRule ^(.*)$ domain.net$[R=301,L]


That will make sure that anyone typing in domain.net will get www.domain.net, which is important because SSL is specific to one or the other.

The one thing this DOESN'T do is change:

domain.net/modules/news to www.domain.net/modules/news

So if someone has the non-www page bookmarked, this won't work. Any mod rewrite experts out there now how to through in a wildcard?



70
technigrafa
Re: Trouble implementing SSL login

Thanks! This sounds promising! But what file do we add that code to?

Edit:
Okay, I answered by own question. You must mean mainfile.php. Sorry for not being terribly savvy

That seems to work nicely.

I have found a problem though. If someone visits the sitename.com rather than www.sitename.com and tries to use the SSL login, it looks like it doesn't log them in, unless they manually change the URL to www.sitename.com. Is there any way to automatically change any request for sitename.com to www.sitename.com? I suppose this can be done with mod_rewrite.




TopTop
« 1 ... 4 5 6 (7) 8 9 10 ... 13 »



Login

Who's Online

217 user(s) are online (146 user(s) are browsing Support Forums)


Members: 0


Guests: 217


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