1
JohnDoo
Re: Blocks in wrong order for ANON USERS ONLY on top page after 2.3.2a upgrade
  • 2008/12/9 17:45

  • JohnDoo

  • Just popping in

  • Posts: 14

  • Since: 2003/9/30


I had the same problem after update from 2.0.18 to 2.3.1. As you say the problem just happens to anonymous users. I tried everything: updating groups permissions, editing blocks, changing weight,... nothing worked.
I finally sorted it out by cloning the blocks and deleting the originals.





2
JohnDoo
Re: RSS feed modules encoding problem -> bug in utf8_encode function?
  • 2008/10/27 20:16

  • JohnDoo

  • Just popping in

  • Posts: 14

  • Since: 2003/9/30


I'm using 2.3.1 so I think this is not solved yet.



3
JohnDoo
Re: RSS feed modules encoding problem -> bug in utf8_encode function?
  • 2008/10/27 18:54

  • JohnDoo

  • Just popping in

  • Posts: 14

  • Since: 2003/9/30


I managed to solve the problem by removing all xoops_utf8_encode calls in backend.php. For example:

$tpl->assign('channel_title'xoops_utf8_encode(htmlspecialchars($xoopsConfig['sitename'], ENT_QUOTES)));


should be changed to:

$tpl->assign('channel_title'htmlspecialchars($xoopsConfig['sitename'], ENT_QUOTES));


So the problem could be that htmlspecialchars() is already returning UTF-8 characters and xoops_utf8_encode() is badly re-encoding the characters, could it be?
I've seen xoops_utf8_encode is in the end calling XoopsLocalAbstract:utf8_encode() and at the beginning of utf8_encode it says:

// Each local language should define its own equalient utf8_encode

What does it mean?

BTW, backend.php seems to be the only XOOPS core file calling xoops_utf8_encode.

Any other having this problem? I think it should affect to all utf8 installations using non-english characters.





4
JohnDoo
Re: HTML Editor
  • 2008/10/23 16:45

  • JohnDoo

  • Just popping in

  • Posts: 14

  • Since: 2003/9/30


Dou you mean blank page? Any errors in debug mode? Did you change the modules/news/xoops_version.php file too? I'd try adding echo "bla bla bla"; lines at different parts of xoops_version.php and functions.php, for example at the beginning of news_getWysiwygForm, ...
Just to check where is the problem.



5
JohnDoo
Re: RSS feed modules encoding problem
  • 2008/10/23 11:26

  • JohnDoo

  • Just popping in

  • Posts: 14

  • Since: 2003/9/30


I'm having the same problem with my site. I think there's a problem in backend.php. The generated html claims to be utf-8 encoded but the characters seems to be iso-8859 encoded.
I'm getting things like "Asociación" instead of "Asociación".



6
JohnDoo
Re: HTML Editor
  • 2008/10/23 10:52

  • JohnDoo

  • Just popping in

  • Posts: 14

  • Since: 2003/9/30


With news module you have to modify 2 files:

/modules/news/xoops_version.php

/*** Editor to use */
/** Comment the old defines
$modversion['config'][20]['name'] = 'form_options';
$modversion['config'][20]['title'] = "_MI_NEWS_FORM_OPTIONS";
$modversion['config'][20]['description'] = '_MI_NEWS_FORM_OPTIONS_DESC';
$modversion['config'][20]['formtype'] = 'select';
$modversion['config'][20]['valuetype'] = 'text';
$modversion['config'][20]['options'] = array(
_MI_NEWS_FORM_DHTML=>'dhtml',
_MI_NEWS_FORM_COMPACT=>'textarea',
_MI_NEWS_FORM_SPAW=>'spaw',
_MI_NEWS_FORM_HTMLAREA=>'htmlarea',
_MI_NEWS_FORM_KOIVI=>'koivi',
_MI_NEWS_FORM_FCK=>'fck',
_MI_NEWS_FORM_TINYEDITOR=>'tinyeditor'
);
$modversion['config'][20]['default'] = 'dhtml';
*/
 
/*** Editor to use (Xoops 2.3) */
$modversion['config'][20]['name'] = 'form_options';
$modversion['config'][20]['title'] = "_MI_NEWS_FORM_OPTIONS";
$modversion['config'][20]['description'] = '_MI_NEWS_FORM_OPTIONS_DESC';
$modversion['config'][20]['formtype'] = 'select';
$modversion['config'][20]['valuetype'] = 'text';
xoops_load('xoopsEditorHandler');
$modversion['config'][20]['options'] = array_flip(xoopsEditorHandler::getList());
$modversion['config'][20]['default'] = 'dhtmltextarea';


/modules/news/include/functions.php:

/** Comment the old news_getWysiwygForm function
function &news_getWysiwygForm($caption, $name, $value = '', $width = '100%', $height = '400px', $supplemental='')
{
...
}
 */
/**
 * Retreive an editor according to the module's option "form_options"
 */
function &news_getWysiwygForm($caption$name$value ''$rows 35$cols 60$supplemental='')
{
    
$editor_configs = array();
    
$editor_configs['name'] = $name;
    
$editor_configs['value'] = $value;
    
$editor_configs['rows'] = $rows $rows 35;
    
$editor_configs['cols'] = $cols $cols 60;
    
$editor_configs['width'] = "100%";
    
$editor_configs['height'] = "400px";

    
$editor = new XoopsFormEditor($captionnews_getmoduleoption('form_options'), $editor_configs);
    return 
$editor;
}


And finally go to system modules administration and update news module. Then you should see the right list of editors at news module preferences.



7
JohnDoo
Re: X-Center 1.09 -> HTTP_GET_VARS vs _GET
  • 2008/10/22 21:03

  • JohnDoo

  • Just popping in

  • Posts: 14

  • Since: 2003/9/30


I'm having a problem with this module. It's based on HTTP_GET_VARS and HTTP_POST_VARS which have been deprecated and set them off by default on newer php versions so the module will not properly work if this is the case (mine is PHP 5.1.6 and HTTP_GET_VARS doesn't work too by default). Are you planning to migrate to $_GET[] and $_POST[] variables?

Regards and thanks very much for this great module.



8
JohnDoo
Re: HTML Editor
  • 2008/10/22 19:24

  • JohnDoo

  • Just popping in

  • Posts: 14

  • Since: 2003/9/30


Maybe it's the same problem I had. Check the content of xoops_data/caches/xoops_cache/xoops_editorlist.php file. If you have an empty array then try modifying class/xoopseditor.php, just after xoops_load("XoopsLists"):

xoops_load("XoopsLists");
   
/** ADD-BEGIN */
   
$this->root_path XOOPS_ROOT_PATH."/class/xoopseditor";
   
/** ADD-END */
   
$_list XoopsLists::getDirListAsArray($this->root_path.'/');


It worked in my xoops.

I don't know why but in my XOOPS 2.3.1, at the moment of calling getDirListAsArray, the value of $this->root_path was the real root dir from my server instead of root path from xoopseditor classes. I've tested on two different platforms (clean install and upgraded from 2.0.18) with the same behaviour.

XOOPS Version - XOOPS 2.3.1
PHP Version - 5.1.6
MySQL Version - 5.0.22
Server API Version - apache2handler
OS Version - Linux



9
JohnDoo
Re: change in server name
  • 2006/3/14 7:16

  • JohnDoo

  • Just popping in

  • Posts: 14

  • Since: 2003/9/30


The file where XOOPS_URL is defined is mainfile.php

Regards,
Marco.



10
JohnDoo
Re: Moving from 2.0.7.3 to the latest 2.0.13.2
  • 2006/3/13 20:41

  • JohnDoo

  • Just popping in

  • Posts: 14

  • Since: 2003/9/30


I think the right way is always installing each patch one by one. Jumping from 2.0.7.3 to 2.0.13.2 will probably not work.
Anyway remember backing-up db and files before updating

Regards,
Marco.




TopTop
(1) 2 »



Login

Who's Online

284 user(s) are online (180 user(s) are browsing Support Forums)


Members: 0


Guests: 284


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