1
johny
Re: How to Change the Title Case (spotlight)
  • 2004/7/16 15:28

  • johny

  • Just popping in

  • Posts: 23

  • Since: 2003/8/25


A big Thank U to both of you!

I had to move my site to a new server and had so many problems with that that I forgot all about this setting.

The solution that worked was macnoludo's one - I had to edit (delete) the two lines in modules/spotlight/include/function.php and my problem was solved.

For additional reference: XOOPS itself also has the same function; class/smarty/plugins/modifier.upper.php (but spotlight module does not use that one).



2
johny
How to Change the Title Case
  • 2004/5/29 20:30

  • johny

  • Just popping in

  • Posts: 23

  • Since: 2003/8/25


The Spotlight module changes the capitalisation of my titles (change case).

Example:
This is my news title gets converted into This Is My News Title

Since I don't use XOOPS in English, and my language does not allow such capitalisation, I really need to disable this feature.

I've noticed that the News module also does something similar - it coverts the titles into the UPPERcase, so this is not something exclusive to the Spotlight module only.

Please share your ideas or even better - solutions



3
johny
Re: Tinycontent question - printer friendly bug
  • 2004/5/11 20:21

  • johny

  • Just popping in

  • Posts: 23

  • Since: 2003/8/25


And again, thank you very much.

Works like a charm...



4
johny
Re: Tinycontent question - printer friendly bug
  • 2004/5/10 21:06

  • johny

  • Just popping in

  • Posts: 23

  • Since: 2003/8/25


GIJOE, you have no idea how grateful I am to your solution.

I really appreciate your reply, even though this was an 'old' post.

Would you also be able to help me with line 60, which could also need text sanitizer treatment:
Quote:

'.$title.'

';


Also thank you for suggesting TinyD; but I think I'm going to stick to TinyContent for now

Thanks again!



5
johny
Re: Tinycontent question - printer friendly bug
  • 2004/5/8 20:24

  • johny

  • Just popping in

  • Posts: 23

  • Since: 2003/8/25


I know this post is quite old but I still haven't solved the problem.

In the meantime, I have installed XOOPS and TinyContent module on another server and I get the same problem again - line breaks, and all codes get displayed in the printer friendly page (codes, not their functions).

PLEASE help!



6
johny
Re: Tinycontent question - printer friendly bug
  • 2004/2/7 11:20

  • johny

  • Just popping in

  • Posts: 23

  • Since: 2003/8/25


OK I wrote a really extensive reply to my original post but I got logged out in between and everything was lost, so I'll just recap it briefly:

It seems that users who are not running the multilingual hack of Xoops, are not experiencing these problems.

I also should correct my original post - HTML codes DO get displayed properla, but XOOPS codes DO NOT. Also, the language codes (filter) are not taken into account.

This only applies to the printer-friendly page (print.php), while the base module (index.php) works OK.

News module also has a printer-friendly page and there there are no problems with neither XOOPS codes nor language codes.

I tried comparing the print.php file of the news module with the print.php file of the tinycontent module but they differ too much - my superficial knowledge of PHP and XOOPS isn't sufficiend to do any changes that would work around this.

A quick demonstation of my problem:

[en]<p><b>Englishbtextp>[/en][de]<p><b>Germanbtextp>[/de]


would get displayed

(en)English text
(-en)(de)
German text
(-de)

while this code:

[en][b]English[/btext[/en]

[
de][b]German[/btext[/de]


would get displayed

(en)(b)English(-b) text(-en)(de)(b)German(-b)(-de)

***I changed the bracket type so that everything gets displayed


PLEASE help me out - I've been struggling with this for over two months, and I can't fix it on my own ;(



7
johny
Tinycontent question - printer friendly bug
  • 2004/1/3 0:23

  • johny

  • Just popping in

  • Posts: 23

  • Since: 2003/8/25


I'm using Tiny content 1.5 and I think I discovered a bug - it has to do with the print function (which I suggested including) :)

There is something missing in that file (print.php) which doesn't get the text through the sanitiser (or something). You see, if you add HTML or XOOPS codes, they either are not taken into account there (HTML) or are displayed as they were entered (XOOPS). Line breaks, paragraphs, etc, are ignored. This only applies to the printer-friendly page (using print.php file), while the module itself works like a charm

I imagine that this is a no-brainer for those who are a bit more into coding, so please help me out (and others too, naturally)...



8
johny
Re: Tinycontent module - how to include a printer-friendly page
  • 2003/11/15 10:12

  • johny

  • Just popping in

  • Posts: 23

  • Since: 2003/8/25


OK. Thanks for the effort. I didn't actually expect a complete service :) but the help is definitely much appreciated and I'm grateful for your effort.

I'm sorry about the double posting; I wasn't exactely sure where to post...

Trying to exercise my patience



9
johny
Re: Xoops ML package
  • 2003/11/15 10:09

  • johny

  • Just popping in

  • Posts: 23

  • Since: 2003/8/25


I guess this is it: https://xoops.org/modules/news/article.php?storyid=1106

I'll try and implement my site with it now.

Thank you very much for this hack!
(the thanks goes to everyone)



10
johny
Tinycontent module - how to include a printer-friendly page
  • 2003/11/14 14:28

  • johny

  • Just popping in

  • Posts: 23

  • Since: 2003/8/25


I only miss one thing - Printer Friendly option.

Could someone guide me how to implement that into the module?

I tried to do it myself but I need help. I believe two files have to be hardcoded. First, in the index.php, an additional line has to be added. If we take an example from TINYEVENT module, where this line enables the printer friendly function:

$content .= "$id'>.XOOPS_URL."/modules/news/images/print.gif' border='0' alt='"._TE_PRINTERPAGE."' />
";



The second change is creating a printer.php file, or adding a print function into the index.php file, just like in the TINYEVENT module.

TINYCONTENT, however, has a different structure, and I don't know how to do all that. Here's the index.php file of the module:

include "../../mainfile.php";



if ( 
file_exists("language/".$xoopsConfig['language']."/modinfo.php") ) {

    include(
"language/".$xoopsConfig['language']."/modinfo.php");

} else {

    include(
"language/english/modinfo.php");

}



$id = isset($HTTP_GET_VARS['id']) ? intval($HTTP_GET_VARS['id']) : 0;



if (
$id != 0) {

  
$result $xoopsDB->queryF("SELECT storyid, title, text, visible, nohtml, nosmiley, nobreaks, nocomments, link, address FROM ".$xoopsDB->prefix(_MI_TINYCONTENT_PREFIX)." WHERE storyid=$id");

}

else {

$result $xoopsDB->queryF("SELECT storyid FROM ".$xoopsDB->prefix(_MI_TINYCONTENT_PREFIX)." WHERE homepage=1");

list(
$storyid) = $xoopsDB->fetchRow($result);

header("Location: $PHP_SELF?id=$storyid");

}

include_once 
XOOPS_ROOT_PATH.'/header.php';

list(
$storyid,$title,$text,$visible,$nohtml,$nosmiley,$nobreaks,$nocomments,$link,$address) = $xoopsDB->fetchRow($result);

    

      if (
$link == 1) {

        
// include external content

        

        
$includeContent XOOPS_ROOT_PATH."/modules/"._MI_DIR_NAME."/content/".$address;

        if (
file_exists($includeContent)){

          
$xoopsOption['template_main'] = 'tc_index.html';

        

          
ob_start();

          include(
$includeContent);

          
$content ob_get_contents();

          
ob_end_clean();

          
//$content = include($includeContent);



          
$xoopsTpl->assign('title'$title);

          
$xoopsTpl->assign('content'$content);

          
$xoopsTpl->assign('nocomments'$nocomments);

        }

        else{

            
redirect_header("index.php",1,_TC_FILENOTFOUND);

        }

      }

      else {

        
// tiny content

        
$xoopsOption['template_main'] = 'tc_index.html';



        if (
$nohtml == 1) { $html 0; } else { $html 1; }

        if (
$nosmiley == 1) { $smiley 0; } else { $smiley 1; }

        if (
$nobreaks == 1) { $breaks 0; } else { $breaks 1; }



        
$myts =& MyTextSanitizer::getInstance();

        
$text=$myts->displayTarea($text$html$smiley11$breaks);

        

        
$xoopsTpl->assign('title'$title);

        
$xoopsTpl->assign('content'$text);

          
$xoopsTpl->assign('nocomments'$nocomments);

      }



include 
XOOPS_ROOT_PATH.'/include/comment_view.php';

include_once 
XOOPS_ROOT_PATH.'/footer.php';



I could certainly use some advice. Please offer your thoughts; I'm sure many of you know how to fix that with no sweat.




TopTop
(1) 2 »



Login

Who's Online

200 user(s) are online (125 user(s) are browsing Support Forums)


Members: 0


Guests: 200


more...

Donat-O-Meter

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

Latest GitHub Commits