Category: Closed - Outdated

I can't login to http://wiki-translation.com (using 1.10svn from june'08) with my openid account
http://xavidp.openid.es

I successfully used that openid account months ago to create a linked tiki account here (xavidp), but it seems that currently it doesn't work. Using the openid box I get the error:

"Authentication error; not a valid OpenID."

Maybe openid is broken? We are using kubrick theme there...

Between Tiki2 and Tiki3, behavior of PlginFile changed, and is causing "No such attachment on this page" errors

http://www.google.com/search?hl=en&q=%22No+such+attachment+on+this+page%22+site%3ATikiwiki.org&aq=f&oq=&aqi=

I only activated the feature and clicked on "Maps" in the menu - that gave me the mentioned 500 Error.

The contents from the Tracker comments tab is not shown here in dev.t.o (using 12.x)

Clicking at the button "notabs" doesn't help either.

Wiki 3D (through the morcego java applet) used to work with previous versions (Tiki6, probably Tiki9 also, even If I can't confirm), and I can't make it work nowadays with current 12.x

See ((doc:Wiki 3D)) and the screenshot below:

{img fileId="769" thumb="y" rel="box[g]"}

Error shown in the java console:

{CODE(ln="1")}
Java Plug-in 10.55.2.13
Using JRE version 1.7.0_55-b13 Java HotSpot(TM) 64-Bit Server VM
User home directory = /home/foo
----------------------------------------------------
c: clear console window
f: finalize objects on finalization queue
g: garbage collect
h: display this help message
l: dump classloader list
m: print memory usage
o: trigger logging
q: hide console
r: reload policy configuration
s: dump system and deployment properties
t: dump thread list
v: dump thread stack
x: clear classloader cache
0-5: set trace level to <n>
----------------------------------------------------
Exception in thread "AWT-EventQueue-3" java.lang.IllegalMonitorStateException
at java.util.concurrent.locks.ReentrantLock$Sync.tryRelease(ReentrantLock.java:155)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueuedSynchronizer.java:1260)
at java.util.concurrent.locks.ReentrantLock.unlock(ReentrantLock.java:460)
at java.awt.EventQueue.getNextEvent(EventQueue.java:545)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:211)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:91)
Exception in thread "AWT-EventQueue-4" java.lang.IllegalStateException: Applet's parent container not set up
at sun.plugin2.applet.Plugin2Manager.start(Unknown Source)
at sun.plugin2.main.client.PluginMain$StartAppletRunner.run(Unknown Source)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:312)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:733)
at java.awt.EventQueue.access$200(EventQueue.java:103)
at java.awt.EventQueue$3.run(EventQueue.java:694)
at java.awt.EventQueue$3.run(EventQueue.java:692)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:703)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:91)
{CODE}

So probably this is just a question of fine tunning some security setting in the applet or in the local settings of the Java Virtual Machine?

a module would be wonderful for the new slideshow features (mootols and jquery) . So far, you can use the slideshow in a wiki page embedding through the iframe plugin the url of the slideshow, but it's way too difficult for newbies.

That module would need some param to let the user choose whether to autosatrt the slideshow, or not (liek the flash plugin with movies).

And another param for automatic loop or just play once. I would say

HTH

After a new calendar is created, the create calendar form is still populated, and subsequent changes will edit the already created calendar instead of creating a new one. This behavior is not apparent to the user until the edit has taken place.

In Opera and IE7 (didn't check yet in IE6), all sublevels of the Tiki Magic admin menu display all the time. Sublevels aren't top-level item sensitive as in Firefox.

These are more patches on aulawiki.1.6.2 posted by xavi

* Versions 1.6.2x are intended just to make aulawiki work on tikiwiki
2.2, the way it worked before.
* Versions 1.6.3x -1.6.4 were transition step.
* Versions 1.6.5x -1.7.x has put back capability to add groups to the
workspace (not only users), and see all child's groups, starting from
the topmost a user can admin, when adding perms to single workspace
resources.
This was be done by adding some new functions to workspaceslib.php:

- get_includable_child_workspaces_groups : will get all groups in WS and child workspaces, starting from the uppermost on which one has admin objectperm down, purged by veryfing a list of includable groups to avoid loop inclusion.
- user_can_admin_workspace_or_upper(), an alias of
get_topmost_workspace_Iadmin(): will get up in the workspace path and
return an upmost parent workspace one can admin, thus gives him admin
capability on the ws and children, or false.
And in lib/workspaces/userslib.php, function group_can_include_group() will check if the group we are trying to include can be included.

with these functions a RolePerm with tiki_p_admin_workspace has
view of all child workspaces and their groups down from the
topmost one he can admin, no matter in which of these he is actually
(current workspace), and be able to add groups and assign perms to
groups within all these ones (only) without need of of having
tiki_p_admin_workspaces also on any child ws.

To the intermediate objectperm tiki_p_create_workspace_resour has been given as a gift the possibility to add single users, not groups, to the workspace predefined groups. On the other hand he can grant objectperms to his resources choosing among any group that belongs to his 'workspace-level'(brothers workspaces) + his parent's (dad, see what I am doing!)

This behaviour is easily changeable in the code, as the ability to do things is stated at the top, where (object)permissions on the workspace are tested once and translated into variables used throughout the code.

In practice:
===========
*'tiki_p_admin_workspaces' as an objectperm on a WS (got
from the RolePerms template for that type of Workspace) is de-facto a
local Workspace administrator. He can do everything (create new sub workspaces, add groups, change perms) except define new
workspace types and roles, and he sees only groups starting from the
topmost workspace he can admin to the bottom.
*tiki_p_create_workspace_resour, as objectperm on a WS (got from the
RolePerms template for that type of Workspace), can manage objectperms
of his ws resources (excluded the ws object itself) choosing among
a tree of groups that starts at his parent's level (dad, see what I am doing), includes 'brother workspaces' (on the same level, child of the same parent), down to bottom. He is a ''resource manager''. For adding users/groups to the ws, he can only add single users by typing the name, no groups. But if his ws has an admin group, he could add himself there. So __tipically workspaces either have a ws_admin role OR a ws_resource manager role__. On the other hand, a top, empty (no resources) workspace, with only an ws_admin role, would grant administration to all childs.
* For global tiki_p_admin_workspace nothing changes, although he is now prevented from including groups that include the includer, something that would put the entire site down.

For a user that has the approriate objectperms from the roles template
to the workspace (tiki_p_admin_workspace or, with less possibilities,
tiki_p_create_ws_resour, for the workspace object), everything can be
done starting from the resources module that has extra links to create child ws, add users/groups, and assign perms to resources.

The resouces module will show/hide Buttons and icons next to each
resource accordingly to what can be done by the actual type of user.


Most of the modifications happened in :

- tiki-workspaces_objectpermissions.ptp + templates
- modules/mod-workspaces_users_groups.php + templates
- lib/workspaceslib.php (new functions only)
- lib/users.php (new functions only)

With respect to the connection workspaces-categories, nothing should be changed. All categories related code is still there and used as before.

---
New permission scheme 1.7.0:
{CODE()}
1.6.2
------------------------------------------------------------------------
perm allows as allows as
name group perm objectperm
------------------------------------------------------------------------
view_ws - -view the ws

create_resour - -create resour onws

admin_ws do all on any ws -add group/user to ws


1.7.x
-----------------------------------------------------------------------
perm allows as allows as
name group perm objectperm
------------------------------------------------------------------------
view_ws - -view the ws

create_resour - (1) -create resour on ws
(de facto admin resour)
-change perms on ws
resources (excluded
the ws itself)
choosing from the
father ws groups and
childs
(father+brothers-to-bottom)
(3)

-add single users(not groups)
to ws predefined groups

admin_ws -do all on any ws(2) -create child workspaces for
any ws from the topmost ws
he has admin rights

-change perms on ws object
itself & resources &
child-ws objects and
resources choosing from
the topmost ws groups
he has admin rights

-add any groups to any ws
choosing from the
topmost ws groups
he has admin rights

-create child workspaces to
any ws from the topmost ws
he has admin rights

notes:
(1) this slot is free! Can't we use it to allow the creation of an
'organic workspace' of some predefined type with himself as
tiki_p_create_resour objectperm on it?

(2) as he can add the 'admins' group, and add users to it, he is
defacto a tiki_p_admin.
maybe he should only be able to add 'workspaces groups'? This would
make him different from a tiki_p_admin_groups and tiki_p_admin.
see comments and examples of different possiblties in
mod-workspaces_users_groups.php

(3) see comments and examples of different possiblties in
tiki-workspaces_objectpermissions.php
---------------------------------------------------------------------
TODO:
there's quite a lot I think, especially in the interface, making it
nicer and more intuitive.
-Add confirmation steps for various deletion actions
-Deletion of workspace does not delete its objects (should it?)
-test it really hard
-understand first, and maybe integrate, the working of 'Private Zones'
and 'user Workspace types' (isuserWS and userws filed in table).
{CODE}
---
LATEST NOTE:
Version 1.7.x has been committed to svn trunk.
You can now download the up-to-date version (not in mods format though) from:
https://tikiwiki.svn.sourceforge.net/svnroot/tikiwiki/mods/trunk/features/aulawiki/
The mod in the repository does not provide a working example of these new features, it has the usual Teacher/Student Roles. One has to define roles with 'tiki_p_admin_workspace' and 'tiki_p_create_workspace_resour' to see this in action

Hi, I've just added a new banning by ip rule at tw.o:

Title User/IP Sections Action
IP_dedes151_81.18.70.166 81.18.70.166 blogs, categories, cms, directory, faqs, featured_links, file_galleries, forums, galleries, gmaps, mytiki, poll, user_messages, wiki page

but I got message
^
Notice: this variable may not be empty: user
^
On a tiki screen as if I was not logged (and I was, as user xavidp with admin rights).
But below, after the footer section, a new tiki header and the rest of another tiki page appeared, and it looked as if Tiki recognized me as logged on the header (my picture is shown), but the login module was also shown for anonymous to log in, on the right column.

See html attached.

The rules seemed to be saved.

References to the external_link.gif image don't work in articles when in mobile mode, and TW is installed in a subdirectory. The reference points to /img/icons/external_link.gif instead.

Example: http://www.vic-fontaine.com/forum/tiki-read_article.php?mode=mobile&articleId=1

Test user/password: smarty

I have a comment on a wiki page. When I click Reply to post a follow-up comment, I get an error. It looks like the Reply button is generating a bad URL:

__Not Found

The requested URL /mywiki/page=IVR_Revitalization&post_reply=1&comments_threshold=0&comments_reply_threadId=5&comments_offset=0&thread_sort_mode=commentDate_asc&comments_per_page=20&comments_grandParentId=0&comments_parentId=5&thread_style=commentStyle_plain was not found on this server.__

This would be a show stopper using Tiki threaded comments is very important feature requirement for us.

Thanks,

Paul

when you click on the polls icon on the Admin Home page, you are taken to the polls comments admin page instead of the polls admin page. User should not have to make an additional click to start work.

The tw.o-maps are mostly out of date - due to a human-bug (messed up longitude and latitude) I live in Somalia since I enter my geographic data on tw.o some months ago.

I can understand, that the admins got other things to do than re-generate the maps. And I can't think of any other needed cron job in tw.o, but never the less it would be cool to have some cron-table to execute certain PHP-function (at least I guess map-generation is some kind of PHP-function).

for users with tiki_p_wiki_view_comments perm only, it displays the ~np~[comment]~/np~ link on the wiki page bar even when no comments there yet to read, so clicking it does literally nothing...

Please see:
http://www.google.com/webmasters/gadgets/

This happens in Tiki4 when using session_storage in the database (which was not the default) when using PDO (which is now the default in Tiki4)

After checking out 1.10 from svn and enabling FCKEditor, attempts to use the editor fail with an error claiming the tikiwiki toolbar does not exist. More specifically, FCKEditor loads, but there are no toolbars.

This is a problem which is very difficult to debug because some people see the images and some don't. We have not yet been able to find a correlation of what causes the issue.

Doesn't work (for some people):
{img src=images/code.png}%%% {CODE()}
{img src="show_image.php?id=76" width=800 }
{CODE}

The source of the problem seems to be something between the GD image library, Windows and TikiWiki. I have never seen such a problem with Linux/GD/TikiWiki.

The alternate method we are now using is totally bypassing the GD image library (works for all):
{img src=images/code.png}%%% {CODE()}
{img src="img/wiki_up/Dashboard_Selection.jpg" width=800 }
{CODE}

I found the other day a chat that looks like is no more on develpment and is used to chat over irc (nice way to chat) is named Eteria IRC and u can find it at sourceforge (http://eirc.sourceforge.net/)

Might this be usefull to change the chat (that in my opinion) that does not work right.

I post this cuz the few times i used the tiki's chat module gave me a few problems with cpu usage and db's saturation

Hope u find this usefull for new vers for the tiki's chat module.

Current mod GMAP does not work in 4.2.

Not sure about other versions

That's what the mod descritpion says:
{CODE()}
author: mcfarland
last modification: 2006/12/22 01:49:26
by: mcfarland
features/phpcas/COPYRIGHT -> lib/phpcas/COPYRIGHT
features/phpcas/README -> lib/phpcas/README
features/phpcas/source/CAS/CAS.php -> lib/phpcas/source/CAS/CAS.php
features/phpcas/source/CAS/PGTStorage -> lib/phpcas/source/CAS/PGTStorage
features/phpcas/source/CAS/PGTStorage/pgt-db.php -> lib/phpcas/source/CAS/PGTStorage/pgt-db.php
features/phpcas/source/CAS/PGTStorage/pgt-file.php -> lib/phpcas/source/CAS/PGTStorage/pgt-file.php
features/phpcas/source/CAS/PGTStorage/pgt-main.php -> lib/phpcas/source/CAS/PGTStorage/pgt-main.php
features/phpcas/source/CAS/client.php -> lib/phpcas/source/CAS/client.php
features/phpcas/source/CAS/domxml-php4-php5.php -> lib/phpcas/source/CAS/domxml-php4-php5.php
features/phpcas/source/CAS/languages/english.php -> lib/phpcas/source/CAS/languages/english.php
features/phpcas/source/CAS/languages/french.php -> lib/phpcas/source/CAS/languages/french.php
features/phpcas/source/CAS/languages/greek.php -> lib/phpcas/source/CAS/languages/greek.php
features/phpcas/source/CAS/languages/languages.php -> lib/phpcas/source/CAS/languages/languages.php
{CODE}

And that's what it says to me when attempting to install it:
{CODE()}
Warning: mkdir(lib/phpcas/source/CAS/PGTStorage): File exists in c:\archivos de programa\easyphp1-8\www\branch-1-9\lib\mods\modslib.php on line 68

Warning: copy(mods/features/phpcas/source/CAS/PGTStorage/pgt-db.php): failed to open stream: No such file or directory in c:\archivos de programa\easyphp1-8\www\branch-1-9\lib\mods\modslib.php on line 375
features/phpcas/source/CAS/PGTStorage/pgt-db.php to lib/phpcas/source/CAS/PGTStorage/pgt-db.php impossible to copy
{CODE}

If you go to this page:
http://themes.tikiwiki.org/tiki-index.php?page=legacy_themes

You see links to download themes. Good.

However, these could be older versions. Bad.

Suggestion: a permanent link.

http://mods.tikiwiki.org/Dist/themes-matrix.tgz
which links to the latest version. Ex.:
http://mods.tikiwiki.org/Dist/themes-matrix-1.2.tgz

Of course, if people use the mods installer, they don't need. But still...

Moving nodes in structures moves to wrong places in some cases (!): weird behavior in tiki 2.3.

If someone wants to track this bug down, I can provide a db backup of the site where this can be reproduced.

The theme using mozilla.css places the full screen icon mostly behind the right-side modules unless the Top Bar is enabled.