201
Draven
Re: Xoops 2.1 Module development Roadmap
  • 2003/11/6 23:02

  • Draven

  • Module Developer

  • Posts: 337

  • Since: 2003/5/28


Quote:

Catzwolf wrote:
And just you dare Draven!

Resized Image



I'd just like to sayResized Image





Resized Image


EDIT (Catz): Can we ban him now? Class, shear class!



202
Draven
Re: Apache mod_rewrite RewriteRule Success
  • 2003/11/6 22:50

  • Draven

  • Module Developer

  • Posts: 337

  • Since: 2003/5/28


I've looked into doing this myself but ran into one major problem, the only way to hide the ?var=value portion is to declare the full url in the mod_rewrite. This isn't feasible when talking about large dynamic pages like forums and WF_section articles.

While you can do it for specific pages like your example

RewriteRule ^products/$ /modules/wfchannel/index.php?page=3 [L]

what I believe would be optimal is the ability to pass var value pairs through folder like representation. So instead of mapping every single URL that contains var value pairs you do so something like this:

http://yourdomain.com/articles/articleid/3

and have mod rewrite conver that to

http://yourdomain.com/modules/wfsection/article.php?articleid=43

Basically it would match the article portion first, then anything after that would be broken in to var=value, in this case ?articleid=3. Another option is to use Apache's look back feature (Info on that found herehttp://www.sitepoint.com/article/485/1). But this requires some php code to run to further break down the URL and having the .php portion still messes up some search engine spiders. We could use the Force Type Derective but that would require renaming all major files from "filename.php" to "filename" which apache would then run as a php file because of the forced type.

Ultimately, your above way works well for small sites and for people that don't mind still using the ?var=value way of passing variables, but for true search engine friendliness you need to eliminate the ?var-value portion of the URL all togther. As far as I know googlebot is the only spider able to traverse dynamic pages. So if you want in to other search engines beyond your homepage, you need to eliminate these variables from the URL.



203
Draven
Re: German Help Needed!!! Please help translate (b1gMail Install).
  • 2003/11/6 5:22

  • Draven

  • Module Developer

  • Posts: 337

  • Since: 2003/5/28


Thanks! Unfortunately another problem; the whole install program is in german as well. The stupid thing is they have an english lang file once you have everything installed. Guess I'll just have to "guess" my way through.

Thanks for your help.



204
Draven
German Help Needed!!! Please help translate (b1gMail Install).
  • 2003/11/6 4:31

  • Draven

  • Module Developer

  • Posts: 337

  • Since: 2003/5/28


Could one of my German Xoop friends please translate these install instructions for me? Web translators do a horrible job and I'd like to port this for XOOPS but I need to install it and test it first.

I'm really amazed these guys haven't translated this to english yet, but yet they have a posting at hotscripts in english and 15 topics in their forums requesting an english translation.

Any help would be great, thanks.

Quote:
b1gMail V5.0.0
==============

Inhalt
------
1. Lizenz
2. Installation
3. Support
4. Hinweise



1. Lizenz
---------
Mit dem Download und der Installation von b1gMail erkennen sie folgende Lizenzbedingungen an und verpflichten sich, diese einzuhalten.

Lizenzbedingungen für B1G Scripte

§ Mit dem Download und/oder der Installation des Scriptes erkennen sie die folgenden Lizenzbestimmungen an und verpflichten sich dazu, sie einzuhalten.

§ Das Script wird von B1G kostenlos und ohne jegliche Garantie angeboten. B1G hat das Script sorgfältig geprüft und getestet, haftet jedoch nicht für eventuelle Schäden, die durch das Script entstehen KÖNNTEN.

§ Das Script ist Open Source, d.H. sie dürfen den Quelltext einsehen und an ihre Bedürfnisse anpassen. Sie dürfen jedoch nicht die Copyright-Verweise im Script modifizieren oder entfernen. Desweiteren ist es untersagt, Stellen aus dem Quelltext in eigene Scripte bzw. Projekte zu übernehmen.

§ Es ist untersagt, das Script oder Teile des Scripts in irgendwelche Form zu verkaufen bzw. zu versteigern. Das ist selbst dann untersagt, wenn Copyright Verweise existieren.

§ Wenn sie die Lizenzbedingungen nicht anerkennen oder gegen sie verstoßen ist es ihnen nicht erlaubt, das Script herunterzuladen, zu installieren, den SourceCode einzusehen bzw. zu verändern und das Script hochzuladen.

§ Nach der Eingabe der Seriennummer und des Keys werden diese durch einmaligem Abgleich mit dem B1G Server validiert. Es wird dabei nur die Seriennummer, der Key und die aktuelle URL übertragen. Dies ist aus Zwecken des Schutz vor Leuten, die gegen Punkt 3 und 4 verstoßen, nötig.


2. Installation
---------------
1. Richten sie die CatchAll Funktion ihrer Domain ein.
2. Richten sie eine POP3-Box ein und lassen sie die Mails der CatchAll Funktion in diese ankommen.
3. Laden sie alle Dateien und Ordner des Scripts auf ihren Webspace.
4. Geben sie den Dateien "config.inc.php" und "agb.txt" und dem Ordner "languages" die Rechte 777 (CHMOD).
5. Besuchen siehttp://www.ihre-url.de/pfad-zu-b1gmail/setup/ und folgen sie den Anweisungen.
6. Nach erfolgreicher Installation den Ordner "setup" mit komplettem vom Webspace läschen (wichtig!).


2.1. Cron
---------
Wenn sie einen eigenen Server oder Webspace mit Cronjobs haben, können sie einen Cornjob zur Steigerung der Performance und zur besseren Funktion des Autoresponders einrichten:
1. Rufen sie in der Shell auf: "crontab -e"
2. Fügen sie eine Zeile hinzu: "* * * * * /usr/bin/php /absoluter-pfad/zu/b1gmail/cronjob.php"
3. Speichern sie die Datei ab


3. Support
----------
Falls sie Fragen haben, schreiben sie diese bitte in unser Forum (unter www.b1g.de) oder nutzen sie das Kontaktformular unseres Support-Systems. Bevor sie im Forum posten benutzen sie bitte erst die Suchfunktion. Oft wurde die Frage schon einmal gestellt und auch beantwortet.


4. Hinweise
-----------
Die Copyright Verweise im Script dürfen unter keinen Umständen entfernt werden (siehe >>1. Lizenz<<).

B1G Webmail (b1gMail) ist ©2002-2003 by B1G - Free PHP Scripts
WWW:http://www.b1g.info/
http://www.b1g.net/
E-Mail: info@b1g.info
webmaster@b1g.info



205
Draven
Re: HTTP 500 - Internal server error when send email
  • 2003/11/4 21:11

  • Draven

  • Module Developer

  • Posts: 337

  • Since: 2003/5/28


Ok, it seems it's caused by the XoopsFormSelectUser call in main.php from preferences. It seems trying to grab the entire list of users kills my servers memory.

Why isn't this divided the way it is in groups etc for over 300? Trying to list 600 members in one drop down is too much.



206
Draven
Re: HTTP 500 - Internal server error when send email
  • 2003/11/4 20:14

  • Draven

  • Module Developer

  • Posts: 337

  • Since: 2003/5/28


I'm having this exact same problem right now with my new host. I'll let you know if I'm able to find the cause.



207
Draven
Re: A total waste of space this!
  • 2003/11/4 4:01

  • Draven

  • Module Developer

  • Posts: 337

  • Since: 2003/5/28


I too like the idea of a "dashboard", as it's generally called. Here's some idea's:

- Small stats window showing usage
- Waiting contents
- new & total user counts
- PM stats
- Most active pages
- moderator log (Last 5 actions)
- admin log
- server stas (PHP version, MySQL version etc)

Perhaps we could eventually have it like a small block system and have modules create "Dashboard" blocks for veiwing stats relevant to their module in the admin area. For instance, forums could include totals for posts, views, replies, new topics, most viewed etc, all in one dashboard block.




208
Draven
Re: XOOPS 2.1 Core development Roadmap
  • 2003/11/4 2:28

  • Draven

  • Module Developer

  • Posts: 337

  • Since: 2003/5/28


Quote:

Catzwolf wrote:
We are trying to take everything onboard (even if this is a core thread) about additions you would all like to see within the modules, but we will try to add these over a period of time and not in one go (the other guys would kill me if I said we would! LOL).









209
Draven
Re: XOOPS 2.1 Core development Roadmap
  • 2003/11/3 19:18

  • Draven

  • Module Developer

  • Posts: 337

  • Since: 2003/5/28


Quote:

Draven wrote:
Quote:

Quote:
Having this allows you to theme differently for each module

It's already there !
Check <{$module.directory}> and <{$module.name}>
Also, theme writers may want to try "Smarty debug" mode in PHP or insert <{debug}> in their templates to see all the defined variables.


See!! I went and made my own hack cause I had no clue it was there. Are you sure it was there in 2.0.3? I swear I did a smarty debug on each module looking for any current variables I could use and saw none. Is it possible this was only added in 2.0.5 after sending my hacks to Catz?


Skap,

I tried both of these out and it won't work. If you're on the Home page or any "system" module it says the last module active, in my case it always says IPBoard even it you're on the home page. Sorry bro.

Here's the hack I was using in the mainfile.php


// Added to identify Current Module
    
$module_handler =& xoops_gethandler('module');
    
$installed_mods =& $module_handler->getObjects();
    foreach ( 
$installed_mods as $module) {
        
$listed_mods[] = $module->getVar('dirname');
    }
    
$c "0";
    
    
//print($xoopsRequestUri);
    
foreach($listed_mods as $mod){
            
// check to see if the Uri matches a loaded module.
        
$pos strpos($xoopsRequestUri$mod);
        if(!
$pos === false){
            
$_SESSION["c_module"] = $mod;
            
$c 1;
            
$isHome 0;
        }
    }
    if(
$c == 0){
            
// We must be in a system module
        
$_SESSION["c_module"] = "system";
            
            
// Are we viewing the homepage?
        
if(strpos($xoopsRequestUri"index") || $xoopsRequestUri == "/"){
           
$isHome 1;
        }
    }


It's not pretty but it tells me what module is currently being viewed and if one isn't found (homepage or edituser.php) it labels it "system".

With this variable available in my templates I can then assign dynamic style sheets by using:

<link rel="stylesheet" type="text/css" media="all" href="<{$xoops_imageurl}><{$c_module}>.css" />

Then I can have a different style sheet for each module stored in my themes folder.

Also allows for different images by doing:

<img src="<{$xoops_imageurl}>images/<{$c_module}>/head/hub.gif" alt="" height="111" width="18" border="0">

This allows me to create image folders in my themes that hold different colors and/or images based on modules.




210
Draven
Re: preliminary summary of roadmap discussion
  • 2003/11/3 16:17

  • Draven

  • Module Developer

  • Posts: 337

  • Since: 2003/5/28


Quote:

Daigoro wrote:

Quote:
Draven wrote:
Error reporting for admin ONLY.


What about removing the error-reporting from the top of the html page? Store the errors in the database, or in a file on the server, and use a special php script to display the errors.
That would make debugging invisible to regular users, and it would allow for a smarter error display.


Actually all you have to do is wrap the error dsiplay in an auth check. It's easy enough to hack, my point is it would be nice not to have to hack each new version. Other than that I think the error reporting is already very helpfull.




TopTop
« 1 ... 18 19 20 (21) 22 23 24 ... 26 »



Login

Who's Online

160 user(s) are online (113 user(s) are browsing Support Forums)


Members: 0


Guests: 160


more...

Donat-O-Meter

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

Latest GitHub Commits