Hello Alain,
I would think, that it would depend on your "categories settings",
respectively "group settings" related to categories.
Workspaces are mainly "constructed" with perspectives and categories. WS
are not an entity themself, like perspectives and categories, but more
or less just a result of a set of different category permissions of a
certain perspective.
I would guess it would work, if you make sure, that P ' would
automatically be set to the same category as P.
=> If P ' is set to the same category as P, it should be part of the
same workspace.
I am sorry that I am not yet enough used to category and goup settings,
for that I could tell you how to make this savely working automatically.
Hopefully my note is helpful for you anyway.
Greetz
Torsten
Am 31.01.2011 19:17, schrieb Desilets, Alain:
> Another question...
>
> Say I am on a page P that is in a given workspace W, and I create a page P' from there. Will page P' automatically be created in workspace W, or do I have to manually specify that.
>
> Note that by "I create a page from there", I mean several possible things. For example, it could be that I create a new dangling link to P' on page P (which resides on W), and then click on that link to create the new page. Or, it could be that, while on P, I use the QuickCreate module displayed on the right, to create a new page P'.
>
> Alain
>

> AFAICT if you are in a particular perspective / category when you create a new page it creates it in
> that category thereby linking it to the perspective. This has been the case with my setup
> both with a question mark (non existant page) and with the quick create module; you remain
> within the perspective/category. You can check this with the category tab at any time, you
> can also add pages created elsewhere to the category so they "join" the perspective.
Excellent! Thx.

On 31/01/2011 1:17 PM, Desilets, Alain wrote:
> Another question...
>
> Say I am on a page P that is in a given workspace W, and I create a
> page P' from there. Will page P' automatically be created in
> workspace W, or do I have to manually specify that.
>
> Note that by "I create a page from there", I mean several possible
> things. For example, it could be that I create a new dangling link to
> P' on page P (which resides on W), and then click on that link to
> create the new page. Or, it could be that, while on P, I use the
> QuickCreate module displayed on the right, to create a new page P'.
>
AFAICT if you are in a particular perspective / category when you
create a new page it creates it in that category thereby linking it to
the perspective. This has been the case with my setup both with a
question mark (non existant page) and with the quick create module; you
remain within the perspective/category. You can check this with the
category tab at any time, you can also add pages created elsewhere to
the category so they "join" the perspective.

Another question...
Say I am on a page P that is in a given workspace W, and I create a page P' from there. Will page P' automatically be created in workspace W, or do I have to manually specify that.
Note that by "I create a page from there", I mean several possible things. For example, it could be that I create a new dangling link to P' on page P (which resides on W), and then click on that link to create the new page. Or, it could be that, while on P, I use the QuickCreate module displayed on the right, to create a new page P'.
Alain

>> Just be aware that permissions are not checked at the category level but at the global level
>> so this part is a hit or miss. According to LPH: "When category permissions are ignored,
>> object permissions are ignored too. It's really just that the code checks the global
>> permissions."
> I don't really understand this. One of my main reasons for wanting to create a workspace, is to have different sections on a same site that are editable by different groups of people. In the past, I have dealt with that situation by creating completely separate instances of Tiki, but it quickly becomes a nightmare to upgrade all of those sites separately.
>
> Is there no way to achieve the same goal with workspaces?
Yes I think you can, this is what I am doing it is essentially using the
perspective + category+groups to create a "Jail". The permission issue
will have to be resolved I think (LPH ?) but we can still use
"workspaces" to channel the experience. I came across the problem of
the permissions when I tried to apply comments to one perspective only.
I added comments to the perspective (search & drag) then gave
permissions via category to the appropriate groups, it didn't work. So
I had to apply the permissions globally to the appropriate group. I
hope this is clear.
I think the essential idea is good but it may be still in shakedown:
workspace: perspective in a category jail, groups assigned to the
category, permissions assigned to the groups in the category.

Thx Patricia,
This is very helpful.
> Just be aware that permissions are not checked at the category level but at the global level
> so this part is a hit or miss. According to LPH: "When category permissions are ignored,
> object permissions are ignored too. It's really just that the code checks the global
> permissions."
I don't really understand this. One of my main reasons for wanting to create a workspace, is to have different sections on a same site that are editable by different groups of people. In the past, I have dealt with that situation by creating completely separate instances of Tiki, but it quickly becomes a nightmare to upgrade all of those sites separately.
Is there no way to achieve the same goal with workspaces?
Alain

I recently tried this myself, I did not post a tutorial as it is not
totally clear to me yet. It is a variation on the hand made
instructions. Just be aware that permissions are not checked at the
category level but at the global level so this part is a hit or miss.
According to LPH: "When category permissions are ignored, object
permissions are ignored too. It's really just that the code checks the
global permissions." This is what I did
1. Enable Features: Category, Perspectives
2. Create category: test
3. Create groups to represent the various roles for the category
* testeditors, member tricia
* testviewers, member trixie
4. Assign permissions to category for groups: admin(all),
testeditors, testviewers
5. Create Perspective: test
1. in the search box type Category Jail & hit the search button
2. in Category Jail box type: test (you need the category number)
3. drag category jail to config box
4. in the search box type theme & hit the search button
5. drag theme to the config box
6. set theme
7. save
6. any pages for your "perspective" assign to the correct category
The preceding sets up a basic workspace with a theme different to the
main so that you can see it when you toggle. It is also a good idea to
enable the perspectives module to toggle perspectives via the menu.
hth
Tricia
On 31/01/2011 10:57 AM, Desilets, Alain wrote:
>
> I need to setup a separate workspace on wiki-translation.com. Looking
> at this page:
>
> http://doc.tiki.org/Workspace
>
> It seems like a very involved process, and I'm not sure that even I
> could pull it off. There are many concepts mentioned in that page that
> I am not familiar with (ex: data channels, roles, perspectives).
>
> Is there are more task-oriented tutorial that describes a list of
> steps in a typical scenario? I looked on Tiki for Smarties and
> couldn't find one.
>
> If such a tutorial does not exist, I am willing to write one (I have
> to do this anyway so I can remember how to do it again), but I may
> need some help figuring out how to actually do it the first time.
>
> Thx.
>
> Alain Désilets
>
> Agent de recherche | Research Officer
>
> Institut de technologie de l'information | Institute for Information
> Technology
>
> Conseil national de recherches du Canada | National Research Council
> of Canada
>
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
>
>
> _______________________________________________
> TikiWiki-devel mailing list
> TikiWiki-devel@...
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel

If you only need to create one, the "Hand made workspaces" is what you need.
It does not involve data channels or anything like that. As for roles and
perspectives, roles are simply groups and perspectives are a central
component to workspaces.
--
LP
On Mon, Jan 31, 2011 at 10:57 AM, Desilets, Alain <
Alain.Desilets@...> wrote:
> I need to setup a separate workspace on wiki-translation.com. Looking at
> this page:
>
>
>
> http://doc.tiki.org/Workspace
>
>
>
> It seems like a very involved process, and I’m not sure that even I could
> pull it off. There are many concepts mentioned in that page that I am not
> familiar with (ex: data channels, roles, perspectives).
>
>
>
> Is there are more task-oriented tutorial that describes a list of steps in
> a typical scenario? I looked on Tiki for Smarties and couldn’t find one.
>
>
>
> If such a tutorial does not exist, I am willing to write one (I have to do
> this anyway so I can remember how to do it again), but I may need some help
> figuring out how to actually do it the first time.
>
>
>
> Thx.
>
>
>
>
>
> Alain Désilets
>
> Agent de recherche | Research Officer
>
> Institut de technologie de l'information | Institute for Information
> Technology
>
> Conseil national de recherches du Canada | National Research Council of
> Canada
>
>
>
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better
> price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> TikiWiki-devel mailing list
> TikiWiki-devel@...
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
>
>

I need to setup a separate workspace on wiki-translation.com. Looking at this page:
http://doc.tiki.org/Workspace
It seems like a very involved process, and I'm not sure that even I could pull it off. There are many concepts mentioned in that page that I am not familiar with (ex: data channels, roles, perspectives).
Is there are more task-oriented tutorial that describes a list of steps in a typical scenario? I looked on Tiki for Smarties and couldn't find one.
If such a tutorial does not exist, I am willing to write one (I have to do this anyway so I can remember how to do it again), but I may need some help figuring out how to actually do it the first time.
Thx.
Alain Désilets
Agent de recherche | Research Officer
Institut de technologie de l'information | Institute for Information Technology
Conseil national de recherches du Canada | National Research Council of Canada

Hi all,
I made a lot of translations via i18n.iki.org lately and noticed, that some strings are untranslatable. So I had a look into the language.php file and it seems, that the whole section "untranslated words" does not show up in the translation interface (I did only some spot testing). Any chance, that this section can be shown to translate on i18n?
Otherwise it would be necessary to translate directly the language.php file. And if I have to do so, where should I commit (yes, I read this http://dev.tiki.org/Where+to+commit and this http://tiki.org/Translation+branching+strategy , too)? I just want to avoid double work ;)
Btw: a lot of translations in the language.php show up in the section "unused words" allthough they are still used (e.g. post, cancel, delete, perms ....). Is there a way to fix this automatically?
cheers
Gregor
___________________________________________________________
WEB.DE DSL Doppel-Flat ab 19,99 &euro;/mtl.! Jetzt mit
gratis Handy-Flat! http://produkte.web.de/go/DSL_Doppel_Flatrate/2

Yes, the IE cacheing issue was reported several weeks ago:
https://sourceforge.net/mailarchive/message.php?msg_id=26679900
-R
On Sat, 29 Jan 2011 22:57:02 -0500, Marc Laporte <marc@...>
wrote:
> I have seen the cached version issue on *.tiki.org sites as well...
>
> On 2011-01-29 7:45 PM, "lindon" <lindon@...> wrote:
>
> Anyone else have these issues in 6.1:
>
> - IE8 - formatting is messed up when first coming onto a page that is
> cached
> and displaying the refresh icon. Clicking the refresh icon fixes it
> (because
> the icon goes away i think) and the print icon, which was on the left
with
> the refresh icon, jumps over to the right to its normal position. I saw
> this
> on the tiki sites.
>

Michael,
I agree with you, it can and should be easier - thought profiles is
probably the best way to make it so. I wonder how hard it would be to
have a tracker and tracker plugin that included all fields for a
tracker by default. The current necessity to lookup and ID every field
you want to place is avoidable i would think.
In the long run, though, would you agree that "navigation determined
by feature" should fall by the wayside in favor of a more natural
"navigation determined by content"
Thats my long run perspective anyway that each page in the website has
a user determined title, and the content of that page can consist of
any of the features.
MLP
On Sun, Jan 30, 2011 at 8:19 AM, Michael Risch <risch@...> wrote:
> " The "old school" use of the tracker as a stand-alone feature can go away, IMO. :)I think it's still fine for small use cases and administrative purposes."
>
> That's a -1 (maybe a -10) from me until there is something that works as well and as easily, including linked fields between trackers, etc. Pretty plugins are nice, but they are a pain to set up and they aren't automatic. I'm all for wikifying the tracker display and input, but why would you get rid of a relatively settled and robust field editing system? Also, I have no desire to manually set up every input form and display table. I use the Tiki Tracker precisely because it takes zero time to set up my input and table forms - requiring me to do it for each one - even drag and drop - would be a huge step backward.
>
> Regards,
> MR
>
>
> -----Original Message-----
>
> Message: 5
> Date: Sun, 30 Jan 2011 00:19:35 +0000
> From: Gergely minger0 <mr.user1@...>
> Subject: Re: [Tiki-devel] Yet another roadmap: Trackers
> To: <tikiwiki-devel@...>
> Message-ID: <BAY140-W990348E8C9CEFB2B64594DEE30@...>
> Content-Type: text/plain; charset="iso-8859-1"
>
>
>
> Hi Tiki-devel,
>
>
> 2. "The trackerlist and trackerfilter plugins should be considered
>
> deprecated. As they act mostly on the database directly, they should
>
> remain functional for a transition period, but moving to alternatives
>
> must be the recommended option."
>
>
>
> I agree a ground-up reworking is desirable, not sure what you are
>
> envisioning as a replacement. I would say that the concept of the
>
> "pretty tracker in the wiki" is the future, implying that a user could
>
> effectively drag, drop and configure structured data as a plugin into
>
> any page/url while editing.
>
> UI is
> not my strong point. But already the unified search allows you to use
> wiki syntax for data layouts through the list plugin. You can use tables
> with customizable columns as well or simply templates on disk. Right
> now, those are view only, but adding form fields shouldn't be that hard.
> Talking about deprecating the plugins is too early for tiki7 or even tiki8. These plugins have a lot of knowledge. They were polished for a long time. It would definitely take some time to get a functionally equivalent replacement in the same quality.
> I assume the direct db access refers to the lack of caching. The mentioned plugins do not inherently use the database directly. These just call the trackerlib, primarily, which could be improved, of course. Starting there sounds safer to me.
>
>
>
> The "old school" use of the tracker as a stand-alone feature can go
>
> away, IMO. :)I think it's still fine for small use cases and administrative purposes.
>
> Joining LPH (I also think it's still fine for small use cases and administrative purposes.).
>
>
>
>
> 3. Name of the feature needs to be changed. Totally agree. how about
>
> "Forms", "Data Engine" or "Structured Data"?Fully open to discussion.
>
> Let me suggest creating the new data engine feature next to the trackers instead of giving it a new name.
>
> Alternatively, step by step improvements could be taken on basis what is already there.
>
> My favorite tracker issue is https://dev.tiki.org/tiki-view_tracker_item.php?itemId=3603 at the moment.
>
>
>
>
>
> MLP
>
>
>
>
>
> LPH
>
>
>
>
>
>
>
>
>
> Gergely,
> tracker fan
>
>
> Date: Fri, 28 Jan 2011 14:44:10 -0500
> From: lphuberdeau@...
> To: tikiwiki-devel@...
> Subject: Re: [Tiki-devel] Yet another roadmap: Trackers
>
>
>
> On Fri, Jan 28, 2011 at 2:14 PM, Michael Pilling <mlpilling@...> wrote:
>
> HI LP,.
>
> Hello Michael,
>
>
> Nice Work, I'll reply to the list on a couple of the points you raised . . .
>
> Trying my best.
>
>
>
> 1. Storage: what kind of storage are you thinking of?
>
> from the "ordinary power user" approach, having trackers as a separate
>
> database or tables in the database has a lot of appeal, and it would
>
> open up manipulation and maintenance via simple SQL commands. Trackers
>
> as flat files is also end user friendly.
>
> As a first phase, I really don't intend on changing the data structure, but yes, real tables are an option. Other databases that are better at unstructured data (which is what trackers are, even though we consider them structured when compared with wiki) like CouchDB or MongoDB would be alternatives as well. It depends on many factors.
>
>
>
>
>
> 2. "The trackerlist and trackerfilter plugins should be considered
>
> deprecated. As they act mostly on the database directly, they should
>
> remain functional for a transition period, but moving to alternatives
>
> must be the recommended option."
>
>
>
> I agree a ground-up reworking is desirable, not sure what you are
>
> envisioning as a replacement. I would say that the concept of the
>
> "pretty tracker in the wiki" is the future, implying that a user could
>
> effectively drag, drop and configure structured data as a plugin into
>
> any page/url while editing.
>
> UI is not my strong point. But already the unified search allows you to use wiki syntax for data layouts through the list plugin. You can use tables with customizable columns as well or simply templates on disk. Right now, those are view only, but adding form fields shouldn't be that hard.
>
>
>
> The "old school" use of the tracker as a stand-alone feature can go
>
> away, IMO. :)
>
> I think it's still fine for small use cases and administrative purposes.
>
>
>
> 3. Name of the feature needs to be changed. Totally agree. how about
>
> "Forms", "Data Engine" or "Structured Data"?
>
> Fully open to discussion.
>
>
>
> MLP
>
>
>
>
>
> On Fri, Jan 28, 2011 at 12:36 PM, Louis-Philippe Huberdeau
>
> <lphuberdeau@...> wrote:
>
>> Hello,
>
>> As Boston is coming up quickly, Marc asked me to write up my ideas for the
>
>> work on trackers. Here is the initial draft.
>
>> http://dev.tiki.org/Tracker+Roadmap
>
>> Feedback is welcome. Nothing is set in stone just yet.
>
>> --
>
>> LP
>
>> ------------------------------------------------------------------------------
>
>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
>
>> Finally, a world-class log management solution at an even better price-free!
>
>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
>
>> February 28th, so secure your free ArcSight Logger TODAY!
>
>> http://p.sf.net/sfu/arcsight-sfd2d
>
>> _______________________________________________
>
>> TikiWiki-devel mailing list
>
>> TikiWiki-devel@...
>
>> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
>
>>
>
>>
>
>
>
>
>
>
>
> --
>
> Michael Pilling
>
> HighProductivity.ca
>
> Office: 807 285 5567
>
> Mobile: 807 777 0886
>
> Toll free: 1 888 882 2887
>
>
>
> ------------------------------------------------------------------------------
>
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
>
> Finally, a world-class log management solution at an even better price-free!
>
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
>
> February 28th, so secure your free ArcSight Logger TODAY!
>
> http://p.sf.net/sfu/arcsight-sfd2d
>
> _______________________________________________
>
> TikiWiki-devel mailing list
>
> TikiWiki-devel@...
>
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
>
>
>
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> TikiWiki-devel mailing list
> TikiWiki-devel@...
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
>
> ------------------------------
>
> _______________________________________________
> TikiWiki-devel mailing list
> TikiWiki-devel@...
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
>
>
> End of TikiWiki-devel Digest, Vol 56, Issue 74
> **********************************************
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> TikiWiki-devel mailing list
> TikiWiki-devel@...
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
>
--
Michael Pilling
HighProductivity.ca
Office: 807 285 5567
Mobile: 807 777 0886
Toll free: 1 888 882 2887

" The "old school" use of the tracker as a stand-alone feature can go away, IMO. :)I think it's still fine for small use cases and administrative purposes."
That's a -1 (maybe a -10) from me until there is something that works as well and as easily, including linked fields between trackers, etc. Pretty plugins are nice, but they are a pain to set up and they aren't automatic. I'm all for wikifying the tracker display and input, but why would you get rid of a relatively settled and robust field editing system? Also, I have no desire to manually set up every input form and display table. I use the Tiki Tracker precisely because it takes zero time to set up my input and table forms - requiring me to do it for each one - even drag and drop - would be a huge step backward.
Regards,
MR
-----Original Message-----
Message: 5
Date: Sun, 30 Jan 2011 00:19:35 +0000
From: Gergely minger0 <mr.user1@...>
Subject: Re: [Tiki-devel] Yet another roadmap: Trackers
To: <tikiwiki-devel@...>
Message-ID: <BAY140-W990348E8C9CEFB2B64594DEE30@...>
Content-Type: text/plain; charset="iso-8859-1"
Hi Tiki-devel,
2. "The trackerlist and trackerfilter plugins should be considered
deprecated. As they act mostly on the database directly, they should
remain functional for a transition period, but moving to alternatives
must be the recommended option."
I agree a ground-up reworking is desirable, not sure what you are
envisioning as a replacement. I would say that the concept of the
"pretty tracker in the wiki" is the future, implying that a user could
effectively drag, drop and configure structured data as a plugin into
any page/url while editing.
UI is
not my strong point. But already the unified search allows you to use
wiki syntax for data layouts through the list plugin. You can use tables
with customizable columns as well or simply templates on disk. Right
now, those are view only, but adding form fields shouldn't be that hard.
Talking about deprecating the plugins is too early for tiki7 or even tiki8. These plugins have a lot of knowledge. They were polished for a long time. It would definitely take some time to get a functionally equivalent replacement in the same quality.
I assume the direct db access refers to the lack of caching. The mentioned plugins do not inherently use the database directly. These just call the trackerlib, primarily, which could be improved, of course. Starting there sounds safer to me.
The "old school" use of the tracker as a stand-alone feature can go
away, IMO. :)I think it's still fine for small use cases and administrative purposes.
Joining LPH (I also think it's still fine for small use cases and administrative purposes.).
3. Name of the feature needs to be changed. Totally agree. how about
"Forms", "Data Engine" or "Structured Data"?Fully open to discussion.
Let me suggest creating the new data engine feature next to the trackers instead of giving it a new name.
Alternatively, step by step improvements could be taken on basis what is already there.
My favorite tracker issue is https://dev.tiki.org/tiki-view_tracker_item.php?itemId=3603 at the moment.
MLP
LPH
Gergely,
tracker fan
Date: Fri, 28 Jan 2011 14:44:10 -0500
From: lphuberdeau@...
To: tikiwiki-devel@...
Subject: Re: [Tiki-devel] Yet another roadmap: Trackers
On Fri, Jan 28, 2011 at 2:14 PM, Michael Pilling <mlpilling@...> wrote:
HI LP,.
Hello Michael,
Nice Work, I'll reply to the list on a couple of the points you raised . . .
Trying my best.
1. Storage: what kind of storage are you thinking of?
from the "ordinary power user" approach, having trackers as a separate
database or tables in the database has a lot of appeal, and it would
open up manipulation and maintenance via simple SQL commands. Trackers
as flat files is also end user friendly.
As a first phase, I really don't intend on changing the data structure, but yes, real tables are an option. Other databases that are better at unstructured data (which is what trackers are, even though we consider them structured when compared with wiki) like CouchDB or MongoDB would be alternatives as well. It depends on many factors.
2. "The trackerlist and trackerfilter plugins should be considered
deprecated. As they act mostly on the database directly, they should
remain functional for a transition period, but moving to alternatives
must be the recommended option."
I agree a ground-up reworking is desirable, not sure what you are
envisioning as a replacement. I would say that the concept of the
"pretty tracker in the wiki" is the future, implying that a user could
effectively drag, drop and configure structured data as a plugin into
any page/url while editing.
UI is not my strong point. But already the unified search allows you to use wiki syntax for data layouts through the list plugin. You can use tables with customizable columns as well or simply templates on disk. Right now, those are view only, but adding form fields shouldn't be that hard.
The "old school" use of the tracker as a stand-alone feature can go
away, IMO. :)
I think it's still fine for small use cases and administrative purposes.
3. Name of the feature needs to be changed. Totally agree. how about
"Forms", "Data Engine" or "Structured Data"?
Fully open to discussion.
MLP
On Fri, Jan 28, 2011 at 12:36 PM, Louis-Philippe Huberdeau
<lphuberdeau@...> wrote:
> Hello,
> As Boston is coming up quickly, Marc asked me to write up my ideas for the
> work on trackers. Here is the initial draft.
> http://dev.tiki.org/Tracker+Roadmap
> Feedback is welcome. Nothing is set in stone just yet.
> --
> LP
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> TikiWiki-devel mailing list
> TikiWiki-devel@...
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
>
>
--
Michael Pilling
HighProductivity.ca
Office: 807 285 5567
Mobile: 807 777 0886
Toll free: 1 888 882 2887
------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
TikiWiki-devel mailing list
TikiWiki-devel@...
https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
TikiWiki-devel mailing list
TikiWiki-devel@...
https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
------------------------------
_______________________________________________
TikiWiki-devel mailing list
TikiWiki-devel@...
https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
End of TikiWiki-devel Digest, Vol 56, Issue 74
**********************************************

That fixed it - thanks chealer!
lindon
On Sat, Jan 29, 2011 at 9:58 PM, Filipus Klutiero <chealer@...> wrote:
> On 2011-01-29 19:45, lindon wrote:
> > Anyone else have these issues in 6.1:
> > - IE8 - formatting is messed up when first coming onto a page that is
> > cached and displaying the refresh icon. Clicking the refresh icon
> > fixes it (because the icon goes away i think) and the print icon,
> > which was on the left with the refresh icon, jumps over to the
> > right to its normal position. I saw this on the tiki sites.
> I didn't see the problem on IE8, but this must be fixed by r32143 for 6.2.
>
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better
> price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> TikiWiki-devel mailing list
> TikiWiki-devel@...
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
>

I have seen the cached version issue on *.tiki.org sites as well...
On 2011-01-29 7:45 PM, "lindon" <lindon@...> wrote:
Anyone else have these issues in 6.1:
- IE8 - formatting is messed up when first coming onto a page that is cached
and displaying the refresh icon. Clicking the refresh icon fixes it (because
the icon goes away i think) and the print icon, which was on the left with
the refresh icon, jumps over to the right to its normal position. I saw this
on the tiki sites.
- IE7 - infinite carousel doesn't work. Didn't see any fixes on the infinite
carousel site or elsehwere.
Thanks,
lindon
------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
TikiWiki-devel mailing list
TikiWiki-devel@...
https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel

On 2011-01-29 19:45, lindon wrote:
> Anyone else have these issues in 6.1:
> - IE8 - formatting is messed up when first coming onto a page that is
> cached and displaying the refresh icon. Clicking the refresh icon
> fixes it (because the icon goes away i think) and the print icon,
> which was on the left with the refresh icon, jumps over to the
> right to its normal position. I saw this on the tiki sites.
I didn't see the problem on IE8, but this must be fixed by r32143 for 6.2.

Infinite carousel works for me with IE8 running in IE7 mode (I don't have a native IE7 installation).
-R
---
Greetings from Sanford, NC, USA!
----- Original Message -----
From: lindon
To: Tikiwiki developers
Sent: Saturday, January 29, 2011 7:45 PM
Subject: [Tiki-devel] Couple of IE Issues
Anyone else have these issues in 6.1:
- IE8 - formatting is messed up when first coming onto a page that is cached and displaying the refresh icon. Clicking the refresh icon fixes it (because the icon goes away i think) and the print icon, which was on the left with the refresh icon, jumps over to the right to its normal position. I saw this on the tiki sites.
- IE7 - infinite carousel doesn't work. Didn't see any fixes on the infinite carousel site or elsehwere.
Thanks,
lindon
------------------------------------------------------------------------------
------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
------------------------------------------------------------------------------
_______________________________________________
TikiWiki-devel mailing list
TikiWiki-devel@...
https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel