Hi, I just have some time to improve and check the Manual at dokuwiki.org. Is it possible to get upload rights? I would like to add some images and there is no group for the manual to ask for.
quit
Tukeke (~Tukeke@unaffiliated/tukeke) has quit (Quit: Tukeke)
flam: afaik only andi (splitbrain) and anika (selfthinker) can give upload rights and afaik it's not that easy to get them, i.e. it is likely you will be told to use an external image hoster
hm, changing all links to a page could be easily implemented with my pagemove code. the only question is what kind of user interface I should implement...
flam, I was just talking to splitbrain, and we have decided to add a group for the (non-existing) "Documentation Team" whose members will be allowed to upload images ... I'll put you in and Klap-in as well ... just give me 5 minutes
I know, its great to have this functionaloty in the pagemove plugin, but I think to do such search an replace jobs its better to do this with a bot script. its just a feeling
hmm, flam, I'm not sure if moving the deprecated tips is a good thing ... it looks like those you moved are not relevant at all anymore, so I would be bold and just delete them
if it's something that is just for an older version, it could be kept because someone might want to update it ... otherwise if it hasn't been updated since ages, it's an indication that no-one is interested in that fix anyway
some of the stuff that you've moved is not just old, it's very, very old ... so you're not moving "sick code" to the sick room, you're moving dead code to the cellar, instead of burying it ;-)
join
mastro (~mastro@host190-67-dynamic.20-79-r.retail.telecomitalia.it) entered the channel
if you don't want to be bold, because you feel it's impolite, I can go ahead and delete them ... then you can feel better by pointing the finger at *me* :)
btw, it would be great if we had some statistics how many people have visited those pages during the last year or so ... I think for most of them it would be '0'
for the documentation on my wiki, we delete when an information is no more valid for all the supported versions. if it's only working for some version, we add this information
it would also be great to weed out some plugins that way ... although in that case I would only add a filter to the main table: if it doesn't work in any of the latest 4 versions, don't display it
selfthinker: yes, but: we have the two iterations in the core code - so the tip has these two iterations ;-) when some deprecated code is removed we can remove the documentated tip as well
yeah, I also wanted that not compatible because as soon as you use jquery the plugin is no longer compatible with older versions and it's not "unknown"
dommel1, what do you mean with "we have two iterations in the core code"? ... although we try to make things backwards-compatible, it doesn't really always work that way
join
ThomasWaldmann (~twaldmann@test.moinmo.in) entered the channel
selfthinker: i.e. the jquery stuff - it's deprecated but you can still use it. the tips using the old js are still working (but should be also deprecated). when the old js stuff is removed from the core, the documentation should also be removed (both had two iterations) -> the documentation should always reflect the current stable
on the one hand dokuwiki only comes with *one* namespace, on the other hand it has several links to [[playground:playground]] in its core ... so people are likely to use it and *then* they will have 2 namespaces
it all depends on the likelihood of people doing that ... if there was a stupid trending article of advising people to do that, then yes, we should have a page explaining it
splitbrain just gave me access to google analytics ... that page was viewed 26 times during the last month ... but it was also linked from faq:toolbar, so it might have been just from people wanting to go through all of those described steps to get their toolbar back
why did you have it activated? one point you mentioned earlier that only people who know what they're doing would activate it ... does that mean you didn't know what you were doing? ;-)
oh, okay ... when you said there was a "problem with js and the toolbar" and you were "one of the 26", I assumed you were on that page because you had the same problem
quit
Mister_X] (~Mister_X@91-121-58-28.ovh.net) has quit (Remote host closed the connection)
so far I found that screenshots are a common source of problems ... fetch.php doesn't seem to cache some external images (it return a 302) ... any ideas why?
join
Ari| (~Ari@HSI-KBW-134-3-145-209.hsi14.kabel-badenwuerttemberg.de) entered the channel
selfthinker: i looked last on https://github.com/splitbrain/dokuwiki/blob/master/lib/scripts/linkwiz.js i know sofar that when i have a function, i can use it with new to make new objects of it (sorry for not correct terms), but linkwiz isn't function, so that doesn't work. It has before that also hard code links to itself, so i can not reuse linkwiz on other places. is it an idea to rewrite linkwiz so i can use it in more situations?
that basically means that one single rogue plugin or other screenshot means that a whole page has to suffer (where those get aggregated like templates, plugins, dokuinstall, etc)
mhh there is also a a timeout of 25 ms and a filesize in media_image_download() if this fails media_get_from_url() fails and this causes a 302 redirect
selfthinker: i like to use the linkwiz for a input field of bureaucracy and data plugin. But linkwiz is loaded at the initializing for the edit window, and has hardcode links to itself. So i guess i cannot clone it for my purpose.
I can imagine the authors of the link wizard meant to make it so it can be re-used ... but it's also possible they failed ;-) ... so, if it cannot be re-used, open a bug report
hm, is there any reason why the "Get involved" link in the sidebar has a completely different target page than the "Get involved" link on the start page?
Michitux and selfthinker i'm trying to improve my knownledge on javascript, do you have maybe good readings on internet on this? especially i'm looking for a more fundamental understanding of objects/functions
hm, what's still on my to read list is the book "javascript the good parts", so I can't tell you if it's actually good, but maybe it is (if a book is okay for you)
quit
NEOhidra (~Miranda@83.142.20.4) has quit (Quit: Miranda IM! Smaller, Faster, Easier. Get it here: http://miranda-im.org)
join
Anael (~Anael@ip-187.net-82-216-176.lyon5.rev.numericable.fr) entered the channel
hmm, for the first time in my life I just did a google books search of the term "dokuwiki" ... I am surprised by the big number! (of books not necessarily about dokuwiki, but which are at least mentioning it)
but you should still be able to use prettyPhoto with the plugin-repo by just adding this to script.js => jQuery(function(){ jQuery("a [rel=lightbox]).prettyPhoto(); });
Michitux, there's nothing wrong with the gallery plugin ... I think it was just working automatically for the plugin-repo because the markup used to be the same (`<a ref="lightbox" .../>`)
I just looked further, the gallery always had the class "lightbox" and used to have rel="lightbox", now (since the introduction of prettyPhoto in June this year) it has a "lightbox[gal-'.substr(md5($ID),4).']" ... so, my above code needs to be changed to: ...
[dokuwiki] kazmiya opened pull request #146: Fix useless use of $auth->isCaseSensitive() in auth_aclcheck() (master...2012_11_AclCaseSensitiveFix) http://git.io/N74khg
part
dokucommit (~dokucommi@sh3.rs.github.com) has left the channel ()
quit
lolmaus (~lolmaus@home-pool-188-244-44-6.com2com.ru) has quit ()