PEAK XOOPS - Re: AltSys: Bug: Block Config Option (Multi-Select) Save Fails in englishin japanese

Re: AltSys: Bug: Block Config Option (Multi-Select) Save Fails

List posts in the topic

report Re: AltSys: Bug: Block Config Option (Multi-Select) Save Fails

msg# 1.3
depth:
1
Previous post - Next post | Parent - Children.1 | Posted on 2009/10/29 23:34 | Last modified
info  一等兵   Posts: 16
Hmmmm. Well, I haven't figured this out. You say it works fine. Generally it works fine, and I've not published a site without it, however there is ONE thing that doesn't work on my sites and it's causing problems with the content admins. I'm curious if you are using the type of options that I am.

For instance, in the spotlight block of the SmartSection module, if the content administrator wants to choose one or more specific articles, that is where it fails. That information never gets captured when saved. The block is empty. However, if I go to the system's block administration page and edit the block and choose one or more articles, then the info is saved.

This behavior is observed on every block that has a multi-select option, whether it is categories or whatnot, and only in the options, not the groups for some reason or another.

FYI, I'm using XOOPS 2.3.3 with AltSys 0.71a. As suggested, I ensured that the files are correct (they are) and updated both the system and AltSys modules (actually all have been updated). Again, it's not the general functionality of AltSys, it's ONLY this ONE issue.

So, do you use that particular type of option in your blocks and does it save that information for you?

FYI, XOOPS 2.3.3, ThAdmin 1.1 (as in XOOPS 2.3.3), Protector 3.22 (about to upgrade to 3.40) and numerous modules. (I don't use the extras/altsys_functions.php include file that comes with XOOPS 2.3.3 as it's an older version of what GIJOE is turning out now in 0.71a and it realistically should be pulled from the distribution at this point IMHO). I turned ThAdmin off, but that didn't help. I turned off Protector, but that didn't help. There is something else going on. I have globals off, safe mode on, MySQL 5.0.x, PHP 5.2.x.

I guess I could delve further into the code and see why it's not saving those options, but maybe it's a quick fix by someone who knows the code.

FWIW, here are the differences in the MySQL queries for those option updates:

Working (in System Blocks area):
UPDATE newblocks SET options='0|5|0|12,10,8|0|0|block', isactive=1, title='More Spotlights', content='', side=8, weight=1, visible=1, c_type='H', template='smartsection_items_spot.html', bcachetime=0, last_modified=1256826349 WHERE bid=120

Not Working (in AltSys Blocks area):
UPDATE newblocks SET options='0|5|0|Array|0|0|block', isactive=1, title='More Spotlights', content='', side=8, weight=1, visible=1, c_type='', template='smartsection_items_spot.html', bcachetime=0, last_modified=1256826310 WHERE bid=120

Two differences: in options: Array instead of 12,10,8 and the c_type is different too. I'm guess that it has to do with the options info passed and it's passing an array instead of the comma-delimited options.

Does that help anyone fix this? Many thanks!!!! This module should be in the XOOPS core and replace the current functionality (especially if we were to get the language stuff running, although I can understand wanting to use just files as they are quicker).

Mark
Votes:7 Average:7.14

Posts tree

  Advanced search


Login
Username or e-mail:

Password:

Remember Me

Lost Password?

Register now!