121
Mithrandir
Re: AMS and SmartSection.......GRRRRR

try this, in smartsection_items_spot_show()
(blocks/items_spot.php line 20 AND 119)

$sel_items explode(','$options[3]);


$sel_items is_array($options[3]) ? $options[3] : explode(','$options[3]);
"When you can flatten entire cities at a whim, a tendency towards quiet reflection and seeing-things-from-the-other-fellow's-point-of-view is seldom necessary."

Cusix Software



122
Mithrandir
Re: AMS and SmartSection.......GRRRRR

Quote:
In 2.0.x, I beleive that each option within the $options array was check to know if it was itself an array. If so, then the option was implode and transformed into a string. So the actual $options saved in the database was a serialized version of :


Nope. XOOPS 2.0.x saves block options as an imploded string with | as delimiter, effectively making it impossible to use multi-valued options (multi-selects etc.)

The "normal" approach used in some modules is to have the multi-select as the last option and when figuring out, which options have what value, an array_slice is used to put all option values above a certain index into one option (a little difficult to explain).

I'll look at the spotlight block and see what I can find.
"When you can flatten entire cities at a whim, a tendency towards quiet reflection and seeing-things-from-the-other-fellow's-point-of-view is seldom necessary."

Cusix Software



123
Mithrandir
Re: Multisite HACK for 2.2.3 Final

Quote:
So, a single code core install of XOOPS supporting multiple sites with their own, dedicated, databases. Single point to patch. Possible?

Much easier than hacks and stuff.

On a Apache/Linux server, you can use symlinks so you would have

/websites/common
with all the files and directories except mainfile.php, templates_c, cache and (perhaps) uploads

and for the subsites, you'd have
/websites/site1
/websites/site2
/websites/site2

that would only have mainfile.php, templates_c, cache and (perhaps) uploads and everything else would symlink to the /websites/common files and directories with the sites themselves being virtual hosts on the webserver.

That way, you would only have one core to maintain, but could use individual databases (and database servers) for the sites. No sharing of database tables would be involved, though.
"When you can flatten entire cities at a whim, a tendency towards quiet reflection and seeing-things-from-the-other-fellow's-point-of-view is seldom necessary."

Cusix Software



124
Mithrandir
Re: ergent help mplease : groups_users_link table was emptied!!!!!

Quote:
Yes i can explain it easily
in Preferences --> General setting --> set USE CUSTOM SESSION to "YES"

then groups_users_link table will be emptied.

Didn't empty for me.
"When you can flatten entire cities at a whim, a tendency towards quiet reflection and seeing-things-from-the-other-fellow's-point-of-view is seldom necessary."

Cusix Software



125
Mithrandir
Re: Xoops 2.2.3a on a home server....

do you in your apache configuration have a line somewhat like this one:

DirectoryIndex index.html index.htm

?
If so, try adding index.php to the line:
DirectoryIndex index.html index.htm index.php
"When you can flatten entire cities at a whim, a tendency towards quiet reflection and seeing-things-from-the-other-fellow's-point-of-view is seldom necessary."

Cusix Software



126
Mithrandir
Resigning

Just to let you know, in case you notice that my rank is no longer "XOOPS Core Team" - my motivation for being in the official XOOPS teams has dropped and my commitment vanished, so in order not to stand in the way of progress, I have decided to relieve myself from all my official XOOPS positions.

Skalpa has a strong team around him so there is no reason to fear anything for the future of the XOOPS core. If anything, you will experience a minimal prolonging of request processing on dev.xoops.org, but that will be it.

I'll still be around, but "just" as a community member like anyone else.

This is not the beginning of a discussion, it is not the result of any evictions, fights or anything like that - it is quitting while I am ahead instead of waiting until everything has gone fubar.
This post is simply to keep you informed so you don't second-guess or make wrong assumptions.
"When you can flatten entire cities at a whim, a tendency towards quiet reflection and seeing-things-from-the-other-fellow's-point-of-view is seldom necessary."

Cusix Software



127
Mithrandir
Re: [design] The design framework

Thanks, Snow. Much appreciated.
"When you can flatten entire cities at a whim, a tendency towards quiet reflection and seeing-things-from-the-other-fellow's-point-of-view is seldom necessary."

Cusix Software



128
Mithrandir
Re: XHTML & CSS [designing without tables]

Yes, there is initiatives to get theme developers and module developers work closer together to allow for better possibilities of a theme deciding the look of a module without the module's templates making it look out of style.

What XHTML and CSS validation has to do with tables, you'll need to explain further. To my knowledge a well-formed table is not against any XHTML or CSS validation rules.
"When you can flatten entire cities at a whim, a tendency towards quiet reflection and seeing-things-from-the-other-fellow's-point-of-view is seldom necessary."

Cusix Software



129
Mithrandir
Re: How to make registration work for 2 separate sites (mith?)

If all you want to do is to sync the users, using my multisite may be a bit over the top (and as I continously say - you WILL need a FREQUENT backup procedure to be sure that you don't mess up during the configuration. One can lose entire site contents if not used properly, or it can behave "weird" if stuff that shouldn't be shared is shared - or if stuff that could be shared is only shared partially) but that's an entirely different discussion.

What you could do is hack the user registration, removal and editing files (register.php, edituser.php, user administration - in root (2.0.x) or Profile module (2.2.x) ) so that whenever a user is added, edited or deleted, a message is sent to the other server with the new information and that database is updated.
SOAP might be handy here - but will naturally need some kind of security mechanism (password... preferably encrypted... perhaps two encrypted passwords where one depends on the other) so not just any user can be edited by anyone.

IF on the other hand, you have access to the other site's database from the first site, you could hack in the code directly, to update the other database table as well, whenever a user account is saved or deleted.
"When you can flatten entire cities at a whim, a tendency towards quiet reflection and seeing-things-from-the-other-fellow's-point-of-view is seldom necessary."

Cusix Software



130
Mithrandir
Re: [content] The framework

Quote:

davidl2 wrote:
Quote:

kapeman wrote:
Since module compatability varies greatly by XOOPS version, I would like to see the modules categorized by version compatability at a high level and then by category.

For example:

2.2.3 Modules
Admin tools, Community etc.

2.0.13.2 Modules
Admin tools, Community etc.


Splitting up the modules by compatible versions would be a good idea...


I have looked at the downloads module and how to add something like a filter for core version compatibility. Right now, I am just wanting a stable version of wfdownloads 3.0 out, so I can make the changes to that version and apply it here.

I would also like module translations to be accessible on the module itself - so when you go to a module in the Repository, you can also download other translations from that page.
"When you can flatten entire cities at a whim, a tendency towards quiet reflection and seeing-things-from-the-other-fellow's-point-of-view is seldom necessary."

Cusix Software




TopTop
« 1 ... 10 11 12 (13) 14 15 16 ... 506 »



Login

Who's Online

140 user(s) are online (65 user(s) are browsing Support Forums)


Members: 0


Guests: 140


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