21
chnwalkman
Re: about Smartsection 2.13 block -- Please help

I have tested it on my xoops2.2x/2.30, it is now OK :)

Thank you, trabis. Thank you very much

Best Regards,
chnwalkman



22
chnwalkman
Re: about Smartsection 2.13 block -- Please help

Thank you, trabis. But ohwada's patch can't slove my problem. It has not included the fix about to interrupt the title for multibyte language.
Quote:

(1) enable \"Print\" and \"PDF\"
(2) Parse error and Notice in print
(3) wrong style in print template file
(4) Invalid argument when guest view
(5) Undefined variable in admin\'s category
(6) Missing argument when save file
(7) many Notice when \"Disable comments\"
(8) keyword \"abc\" match \"abccccc\"
(9) cannot show keyword in Japanese and multibyte language



23
chnwalkman
Re: about Smartsection 2.13 block -- Please help

Thank you, catzwolf.

Yes, I set that "Length of the title" option in the recent items block. Maybe it cannot support multi-byte languages perfectly.



24
chnwalkman
Re: about Smartsection 2.13 block -- Please help

lovemp3, have you fixed that problem above it?



25
chnwalkman
about Smartsection 2.13 block -- Please help

I have downloaded smartsection 2.13 final and tested it on XOOPS 2.0.16/2.2.5. When I set title length option in the "recent and new items blocks" met a problem.

When XOOPS default language is "English", the title shows OK in the recent and new items blocks, it is interrupted according to my setting (it's by "..." ending).

But when I set language to "Chinese" by "Preferences Main / General Settings", the title length is invalid in that block. Whether I set how much characters, the item title always complete display in the "recent and new items blocks" at my homepage. How can I fix it?

Please help. Thank you.



26
chnwalkman
Re: News RC2 & spotlight problem
  • 2005/3/16 2:35

  • chnwalkman

  • Just popping in

  • Posts: 35

  • Since: 2004/8/25


I'm a real newbie for php and my english is poor.

I have 3 systems for the test, One of them has the php 4.3.7, and other all have the php 4.3.9.
I have met this problem on the system with php 4.3.7 (I'd tried to upgrade 1.2-1.3, and uninstall the 1.2 version, then enter a fresh install), and other all OK.
Quote:
When entering the website the spotlighted newsitem is viewable within the spotlight block. But, and this is where the problem lays,.... as soon you've clicked one of the other news topic-items tabs olf the enabled spotlight block, you cannot get to see the spotlighted news item back again. Although you see the tab 'spotlight', and click on it nothing will happen. Somehow the spotlighted news item block view gets blocked. Switching back doesn't work.
p.s. "other news topic-items tabs" click on it nothing will happen too.


So I put forward such suggestion to Shine.

Regards,



27
chnwalkman
Re: News RC2 & spotlight problem
  • 2005/3/15 14:35

  • chnwalkman

  • Just popping in

  • Posts: 35

  • Since: 2004/8/25


I found that News 1.3 required PHP 4.3.9 or higher. Am like this to me at least.



28
chnwalkman
Re: OK with PHP CGI but not with ISAPI
  • 2004/8/25 3:14

  • chnwalkman

  • Just popping in

  • Posts: 35

  • Since: 2004/8/25


Quote:

RVirtue wrote:
With debug mode on (with or without the added line in common.php) it outputs only the following PHP "notice-level" error: Notice [PHP]: Undefined offset: 2 in file F:\VIRtech\XOOPS\include\common.php line 253.

Is it possible that XOOPS is halting on PHP notice-level errors even though PHP itself has been configured to ignore them? Obviously, I'm "reaching" for this one.

BTW, I appreciate very much your taking the time to respond. I'll work with you as long as you think it's worth it, but don't "bust a gut" over one baffled tester.


Yes, I had a same question, too
Notice [PHP]: Undefined offset2 in file ...XOOPSincludecommon.php line 253.


OS versions:
Windows 2000 Server with IIS
MySQL version 4.0.16
PHP version 4.3.7
Xoops version: 2.0.7 to 2.0.7.1

so I searched some others posts, and now it's ok.

add to /include/common.php
$xoopsRequestUri = ($xoopsRequestUri)?$xoopsRequestUri:xoops_getenv('REQUEST_URI');
    
$xoopsRequestUri = ($xoopsRequestUri)?$xoopsRequestUri:(($rq xoops_getenv('SCRIPT_NAME')) ? $rq:getenv('REQUEST_URI'));

after:
$xoopsRequestUri $_SERVER'REQUEST_URI' ];        // Deprecated (use the corrected $_SERVER variable now)
    /**#@-*/


that's all. what do you think about this?
Sorry for my english.

Regards,




TopTop
« 1 2 (3)



Login

Who's Online

260 user(s) are online (153 user(s) are browsing Support Forums)


Members: 0


Guests: 260


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