Yup, after defining id in *_info() there is an "id" thing in $params.  But extract() didn't create $image_id.
extract only takes the keys and make them into variables...
actually, I just hate the use of extract in plugins
scope pollution
causing plenty of notices, unclear source of the value
extract($params, EXTR_SKIP, EXTR_PREFIX_ALL, 'image');
Trying to isolate the function's values by adding the image_ prefix.
did it create imageid?
$imageid*
Manual says it should be $image_id because the underscore is forced.
hmm
I would just use $params['id'] to access the value
Both $image_id and $imageid are NULL.
Yeah, but I was following the practices found in other plugins.  Didn't want to rock the boat whose characteristics I don't know.
no need to
$params['id'] does have the value.  Wonder why extract ain't finding it thar.
But then, several things haven't been behaving as PHP should behave.  Had to recode stuff which looked OK.
Maybe I shouldn't have used include('HELL');
:-)
tikilib.php does that already
That explains a lot.  There also seem to be a typo in 'HELLo World' then.
Replaced all $image_* with $params['*'] so of course I get the white blizzard of death.  Sigh.
Guys, I just installed the Eatlon theme into tikiwiki 2.2 - now no matter what theme I choose, the Eatlon skin is the only one that displays.
What have I done wrong?
If it were a file permission problem, the original theme should still be available.
Or do you have different themes configured for various content or users?
well, if i change the theme via Look & Feel panel - say, to fmsc.css, and then click apply - I don't get an error, and when the page loads again the selected theme IS fmsc.css - but the wiki is still using the eatlon theme.
Flush your Tiki caches?
no change.
So the Look & Feel page says the theme is fmsc.css but the decorations are still eathlon?
yes.
Same for tikineat?
same for any theme whatsoever.
I don't know.  Try turning off Eathlon?
eheh.  turning off as a process distinct from selecting a different one?
You said you "installed" it, as if it was a mod rather than a builtin.
i extracted it to the themes directory.
I am not familiar with that theme so don't know what it does.  I don't know what it might do which could get it stuck as the active theme.
dude, it's a theme.  it is a css file and some images.
this is a tikiwiki issue.  :p
Nobody else seems to be answering now.  Try again tomorrow earlier in the day?
very well.  thank you for trying.
Or just lurk and see if someone else pipes up later.
Good luck.
Be glad you have something to look at.  Took me a half hour to get something other than a white screen after a code alteration earlier.
I'm about to spend a load of time setting up a new Tiki, making LDAP work, and creating a highly specalized theme... should I use 2.2 or 3.0 as my starting point ?
i guess i'm marginally glad?  i've been having a lot of problems so far and my setup isn't weird at all.  i am basically kicking myself for not using mediawiki.
although mediawiki's security is durr hork retarded.
2.2 is stable.  You might not want to invest "a load of time" on 3.0 if you want to be able to use the site.
LOL - I'm choosing Tiki because my old mediawiki setup was so ghastly I can't stand it anymore.
So - 3.0 is seriously that unstable then ?
care to define ghastly, cnd?
3.0's instability depends upon what has been done to it now.
Not then, but now.
And this now also.
i mean, i basically can't switch because i need the revision control to stay in tact and for tikiwiki the best case transfer scenario involves losing revision data.
ghastly = I spent a week doing a new theme, and the next mediawiki upgrade hosed all my work.  Spammers have bots that search and deface sites faster than you can imagine.  no security.  way too few features.  WAY.
neat.
that is concise and helpful.
thank you.
kerin: The best case transfer scenario actually involves someone (maybe you) writing a mediawiki import tool which keeps revision information.
For some meanings of "best", that is.
SEWilco2... I don't suppose you happen to know of any point in recent time when the 3.0 work was reasonably stable?
3.0 tends to work, but it is where new things are added and things are altered.
SEWilco2: the best case transfer scenario is contingent on things and abilities that i actually have access to :p
You can grab a copy and test it with your data.  If it works, great.  Just retest before moving an update into production.
The odd broken thing here-and-there I can handle... but I really prefer the idea of possible 3.0 things I'll need being in place, and me not having to upgrade 2.2 to 3.x in a few months time, and importantly, my work on the theme not getting ruined and needing a re-write later.  Having spent 0.1 minutes looking at how they work - I can imagine that going from 2.2 to 3.0 will pose all kinds of theme-compatability issues...  I'm talking about radica
cnd: OK, then you have priorities which fit 3.0 better than 2.2.  It's your site and what is important is how it works for you.
I'll take a deep breath, cross my fingers, and hope it all works out :-)
thanx.
cnd, Tiki 3 is basically stable, but atpit isn't too different from Tiki 2 as far as themes are concerned. But there's a user interface improvement going on that will bring some fairly major changes to Tiki 3 before it's released in March.
You can see at http://ui.tikiwiki.org. Or see the files at Tikiwiki's subversion experimental/ui-revamp/ .
The layout basics will be more or less the same, but how some details are handled will change quite a bit.
Feel free to give input or ask questions on the tikiwiki-devel mailing list, etc.
Or register and post at ui.tikiwiki.org.
Actually between Tiki 2 and 3 there is a basic shift as we get away from table-based layout. From Tiki 3, there's a no-table liquid layout as default. The old method was default in Tiki 2.
(Made the shift in my head so long ago, I forgot in reality Tiki 2 still has a table-based default theme.)
kerin, if you check back, normally theme-changing works as expected. Did you try logging out and back in to clear session info, or try a different browser?  
Mornin.  I'm looking for some help on troubleshooting the calender_new module; the day of the week is incorrect even though the date and month is correct.  
for instance, today is shown as Wednesday, 30 December 2008
When viewed through the calendar that the module references, the day is correct.  Any ideas?
hi on 1.3 I cannot enter inside folder menus ?
mornin all
does anyone know what the field linkto in the DB table tiki_articles currently does??
hi
i need help with tiki
hi
sry my english is not so good but i hope you unterstand me
or is anyone german here?
hello?
amette speaks German
FrankP_german : as well
probably others
marc, do you know what the field linkto in the DB table tiki_articles currently does??
probably the url reference for the article?
marclaporte : yes, I think
i have the problem when i create a site and i will save it i bocome a error but he save the site
looks to be mostly empty---cant find any code the reads or writes the field
what db?
what tiki version?
2.2--mysql
did you change any config to article types?
can you duplicate problem on opensourcecms's demo tiki?
hello?
missing 'tiki-index.php?page=' in Links
somebody an idea, what's wrong
sefurl enabled?
'Search engine friendly url' was enabled
yes
this is not a good future, if the page links do not work anymore
Bucky had this problem
hum... they work if you set-up the htaccess file properly
base requirement of sefurl
SVN:  Commit by marclaporte :: r 16153 /trunk/lib/setup/prefs.php: Default forum threading to be more like other forum applications as per the discussion (Some suggestions related to the Official Tikiwiki forum) on the Tiki users mailing list, started by joomlagate.com on Dec 16th, 2008. Previous behavior is still available by changing __Default thread sort mode__ at tiki-admin.php?page=forums  
SVN:  Commit by lphuberdeau :: r 16154 /branches/experimental/perms/: [BRANCH] Creation, trunk 0 to 16153  
right now, I'm really amazed by the amount of useless code in the tiki foundations
oh wait, that branch might only be merged in for 4.0
oh well
polom
hey amette
heya lphuberdeau 
got your travel arrangements set for March?
not yet, I received a mail from them, if I could provide them a photo...
there should be some of those from previous tikifests
... when I then asked, if I should take that as an official acceptance of my session..
... they answered: woops, you didn't get any previous email? I better check, if we're taking care of your flight and accomodation! :P
be sure to provide them with one, otherwise they will find one for you, and that may not be at your advantage
what kind of travel arrangements should I have to make?
hehehe, ok - thanks for that hint ;)
I think there was some cost issue, but check the prices and email them
hmm, ok... so what is the usual way to handle that stuff?
anyway, I will see them shortly and get more details
ok, kewl - lemme know then please! :)
usually you get refunded at the conference
but the amount has to be predetermined as a check is waiting at the desk
ok, gotta e-mail them again... haven't yet heard anything more of them
busy people doing this on their free time ;)
hehe, I can imagine ;)
SVN:  Commit by lphuberdeau :: r 16155 /branches/experimental/perms/ (17 files in 7 dirs): [MOD] Restructuring base DB layer to remove code duplication  
anyway, all this dead code exhausted me... going back home
alright, happy chillin' :)
doc.tw.o: Search for "dynamic variable" in Documentation tries to download tiki-searchindex.php of type PHP file.
works for me
FF and Konq
err... mom...
actually I get the white screen of death
The search box still tries to download that .php file.  The "search by page name" box does find the page.
searches don't finish for me...
any search works for me - but not when I start the search term with "dynamic"...?!?? :O
So it's a dynamic failure, then.
LOL :P
"dynamic"
This is doc.tw.o so just document the dynamic crash feature.
:-)
I wonder if there's a bad page called "dynamic".  Maybe "Dogfood" should say see also Dynamic.
I'm guessing I need to install extra things before using 3.0?  Anyone know what?  I'm seeing this after a fresh unzip:-
[client 203.206.137.129] PHP Parse error:  parse error, unexpected T_STRING, expecting '{' in /var/www/html/pbcc/lib/core/lib/DeclFilter.php on line 9
requires PHP 5
>5.1 actually
which is at least 3 years old
dev.tw.o: The style for trackers doesn't make the Rating links apparent.  They look like "-2-1012" rather than as selectable options.
I finally figured out what "1012" meant.
SEWilco2: can you fix?
I am not aware of having css edit priv on dev.  I'm just a TW editor, as far as I know.  And I've got my hands full.
SEWilco: : you can fix in SVN
SEWilco: : was that a yes? :-)