headers
sandaili | 1 Sep 2009 03:27

Re: New Category problem - doesn't show up and becomes unassigned


I have been trying to figure this out all weekend and failed miserably. If
anyone can at least let me know if this is a feature that works on theirs so
I stop wasting my time trying to fix it, I would appreciate it :)
-- 
View this message in context: http://www.nabble.com/New-Category-problem---doesn%27t-show-up-and-becomes-unassigned-tp25183337p25233019.html
Sent from the Horde - Turba mailing list archive at Nabble.com.

--

-- 
Turba mailing list - Join the hunt: http://horde.org/bounties/#turba
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: turba-unsubscribe <at> lists.horde.org
Permalink | Reply | 0 comments |
headers
gimili | 1 Sep 2009 13:59
Picon

Re: New Category problem - doesn't show up and becomes unassigned

sandaili wrote:
> When creating a contact, or task, I can press "new category" but nothing pops
> up. I am not sure if somethign is supposed to pop up or not. So I fill out
> the rest of the fields, and submit. 
>
> The task or contact is created, and the category is unassigned.
>
> I have been searching Nabble and looking in my setup but I can't figure out
> what to fix.
>   
When I select "new category" in turba or anywhere else in horde and then 
hit save (using the newest firefox on win xp) it pops up with a window 
saying "Please type the new category name:".  I can also go to "Global 
Options", in the side bar, then select "Categories and Labels" and in 
there I can also create new categories.  It is possible but 
unfortunately more difficult to make global categories.  If you are 
having problems perhaps try a different browser.  What versions and what 
browser are you currently using on what os?  **Note:  when you select 
"New Category" you have to hit the save button before to get the prompt 
to pop up.**

-- 
gimili

--

-- 
Turba mailing list - Join the hunt: http://horde.org/bounties/#turba
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: turba-unsubscribe <at> lists.horde.org
(Continue reading)

Permalink | Reply | 1 comment |
headers
sandaili | 1 Sep 2009 14:55

Re: New Category problem - doesn't show up and becomes unassigned


Thanks! I tried after I updated Firefox, and it works. I use Opera as my main
browser and apparently Horde and Opera are not compatible. Popups are
allowed in it. I don't get an error in Opera, I just hit save and it never
asks anything. Hmmm!

Thanks so much and now I know I'm not crazy.

gimili wrote:
> 
> sandaili wrote:
>> When creating a contact, or task, I can press "new category" but nothing
>> pops
>> up. I am not sure if somethign is supposed to pop up or not. So I fill
>> out
>> the rest of the fields, and submit. 
>>
>> The task or contact is created, and the category is unassigned.
>>
> 
> When I select "new category" in turba or anywhere else in horde and then 
> hit save (using the newest firefox on win xp) it pops up with a window 
> saying "Please type the new category name:".  I can also go to "Global 
> Options", in the side bar, then select "Categories and Labels" and in 
> there I can also create new categories.  It is possible but 
> unfortunately more difficult to make global categories.  If you are 
> having problems perhaps try a different browser.  What versions and what 
> browser are you currently using on what os?  **Note:  when you select 
> "New Category" you have to hit the save button before to get the prompt 
> to pop up.**
(Continue reading)

Permalink | Reply | 0 comments |
headers
Robert P. J. Day | 1 Sep 2009 16:58
Picon
Gravatar

Re: how to simplify my turba upgrade process

On Mon, 31 Aug 2009, Michael Rubinsky wrote:

> Can you point me to where in the docs referring to turba_objects is
> misleading you?

  ok, it's possible i was confusing myself between two of the upgrade
scripts.  i think we can both agree that, if there was an upgrade
script somewhere in turba/scripts/upgrades whose invocation upgraded
*only* the "turba_objects" table with no option to upgrade *other*
tables that represented addressbooks, and the accompanying
documentation *also* didn't make it clear that you should run that
script on all of your other addressbook tables, that would be somewhat
misleading.  but i can't find such an example, so i'm thinking i
misread something.  sorry.

rday

p.s.  oh, wait, here's an example but it might be so old, it's not
relevant.  ugpgrading to turba 2.0, the UPGRADING doc reads:

=====

Four new fields have been added to the default SQL table layout, one
being mandatory.  The new ``object_uid`` field provides a global
unique ID to objects.

Execute the provided SQL script to update your data to the new Turba
version::

   mysql --user=root --password=<MySQL-root-password> <db name> <
(Continue reading)

Permalink | Reply | 2 comments |
headers
Robert P. J. Day | 1 Sep 2009 18:01
Picon
Gravatar

Re: how to simplify my turba upgrade process


  ok, i think i see where i misunderstood the fundamental process of
upgrading turba -- that the basic schema of the addressbook is
user-definable.  so let me ask a much simpler question that might make
short work of my confusion.

  to recap, i'm upgrading a horde install on a debian system from an
old 3.0.5 to the latest.  to do that, i started from scratch and
installed horde -- just the infrastructure.  and that worked fine, no
apps, just the infrastructure.

  now, one at a time, i'm adding back in the formerly-installed horde
(and non-horde) apps, un-tarring each app's current tarball following
each app's UPGRADING instructions and possibly upgrading that app's
data schema in the process.

  i've already re-installed the (kronolith) calendar just that way,
and it appears to work just fine, so now i'm working on the turba
addressbooks data.  and before i get detailed, will this basic recipe
get me my addressbooks back?

  1) note the current set of addressbook tables in the horde database
     (currently four of them)

  2) following what i read in UPGRADING, run the appropriate scripts
     to upgrade their schemas

  3) to start from scratch, delete *every* trace of turba from the
     new horde install -- that is, the share tables, the install
     directory ... *everything* except the addressbook tables
(Continue reading)

Permalink | Reply | 8 comments |
headers
Michael Rubinsky | 1 Sep 2009 18:11
Favicon
Gravatar

Re: how to simplify my turba upgrade process


Quoting "Robert P. J. Day" <rpjday <at> crashcourse.ca>:

> On Mon, 31 Aug 2009, Michael Rubinsky wrote:
>
>> Can you point me to where in the docs referring to turba_objects is
>> misleading you?
>
>   ok, it's possible i was confusing myself between two of the upgrade
> scripts.  i think we can both agree that, if there was an upgrade
> script somewhere in turba/scripts/upgrades whose invocation upgraded
> *only* the "turba_objects" table with no option to upgrade *other*
> tables that represented addressbooks, and the accompanying
> documentation *also* didn't make it clear that you should run that
> script on all of your other addressbook tables, that would be somewhat
> misleading.

No. You're still not understanding what I'm saying.  The reason the  
scripts refer to the table by name is because that table is the only  
table created by Turba. It's an example, or even a suggested schema,  
not a required schema. If the admin creates his own custom tables,  
then there is no reason to even run these scripts.

Thanks,
mike

--
The Horde Project (www.horde.org)
mrubinsk <at> horde.org
(Continue reading)

Permalink | Reply | 1 comment |
headers
Robert P. J. Day | 1 Sep 2009 18:17
Picon
Gravatar

Re: how to simplify my turba upgrade process

On Tue, 1 Sep 2009, Michael Rubinsky wrote:

>
> Quoting "Robert P. J. Day" <rpjday <at> crashcourse.ca>:
>
> > On Mon, 31 Aug 2009, Michael Rubinsky wrote:
> >
> > > Can you point me to where in the docs referring to turba_objects
> > > is misleading you?
> >
> >  ok, it's possible i was confusing myself between two of the
> > upgrade scripts.  i think we can both agree that, if there was an
> > upgrade script somewhere in turba/scripts/upgrades whose
> > invocation upgraded *only* the "turba_objects" table with no
> > option to upgrade *other* tables that represented addressbooks,
> > and the accompanying documentation *also* didn't make it clear
> > that you should run that script on all of your other addressbook
> > tables, that would be somewhat misleading.
>
> No. You're still not understanding what I'm saying.  The reason the
> scripts refer to the table by name is because that table is the only
> table created by Turba. It's an example, or even a suggested schema,
> not a required schema. If the admin creates his own custom tables,
> then there is no reason to even run these scripts.

  actually, yes, i get what you're saying and i see why i got so
confused in the beginning.  from my initial reading and from perusing
the scripts, i got the impression that there was something magical
about that "turba_objects" table, and all my further misunderstanding
followed from that.  i didn't realize that it was just the arbitrary
(Continue reading)

Permalink | Reply | 0 comments |
headers
Michael Rubinsky | 1 Sep 2009 18:18
Favicon
Gravatar

Re: how to simplify my turba upgrade process


Quoting "Robert P. J. Day" <rpjday <at> crashcourse.ca>:

>
>   ok, i think i see where i misunderstood the fundamental process of
> upgrading turba -- that the basic schema of the addressbook is
> user-definable.  so let me ask a much simpler question that might make
> short work of my confusion.
>
>   to recap, i'm upgrading a horde install on a debian system from an
> old 3.0.5 to the latest.  to do that, i started from scratch and
> installed horde -- just the infrastructure.  and that worked fine, no
> apps, just the infrastructure.
>
>   now, one at a time, i'm adding back in the formerly-installed horde
> (and non-horde) apps, un-tarring each app's current tarball following
> each app's UPGRADING instructions and possibly upgrading that app's
> data schema in the process.
>
>   i've already re-installed the (kronolith) calendar just that way,
> and it appears to work just fine, so now i'm working on the turba
> addressbooks data.  and before i get detailed, will this basic recipe
> get me my addressbooks back?
>
>   1) note the current set of addressbook tables in the horde database
>      (currently four of them)
>
>   2) following what i read in UPGRADING, run the appropriate scripts
>      to upgrade their schemas
(Continue reading)

Permalink | Reply | 7 comments |
headers
Robert P. J. Day | 1 Sep 2009 18:44
Picon
Gravatar

Re: how to simplify my turba upgrade process

On Tue, 1 Sep 2009, Michael Rubinsky wrote:

> Quoting "Robert P. J. Day" <rpjday <at> crashcourse.ca>:
>
> > 1) note the current set of addressbook tables in the horde
> > database (currently four of them)
> >
> > 2) following what i read in UPGRADING, run the appropriate scripts
> > to upgrade their schemas
>
> Only if they need to be updated. i.e if you are updating the
> sources.php file from the new *.dist version and plan to use the
> 'localsql' configuration. Otherwise, you just need to make sure you
> have appropriate maps in the entries.

  technically, i'm sure i don't *need* to nuke all that stuff, but i
don't know what kind of mess i've made of the turba install thus far
so, for the sake of cleanliness, i'd just like to simulate as if i was
starting from scratch, and was handed some old addressbooks from an
old turba install.  as in, i'd like to test what it would take if
someone told me, "here, here's some old addressbooks from a 2.0.5
install -- add turba 2.3.1 to our horde install and add those books
back in."

  in short, i want to install the latest turba, and bring the
addressbooks up to date to be compatible with the default, rather than
go the other way.  (and since i think i've already done those schema
upgrades, this would only make sense.)

> > 3) to start from scratch, delete *every* trace of turba from the
(Continue reading)

Permalink | Reply | 6 comments |
headers
Michael Rubinsky | 1 Sep 2009 19:15
Favicon
Gravatar

Re: how to simplify my turba upgrade process

Quoting "Robert P. J. Day" <rpjday <at> crashcourse.ca>:

> On Tue, 1 Sep 2009, Michael Rubinsky wrote:
>
>> Quoting "Robert P. J. Day" <rpjday <at> crashcourse.ca>:
>>
>> > 1) note the current set of addressbook tables in the horde
>> > database (currently four of them)
>> >
>> > 2) following what i read in UPGRADING, run the appropriate scripts
>> > to upgrade their schemas
>>
>> Only if they need to be updated. i.e if you are updating the
>> sources.php file from the new *.dist version and plan to use the
>> 'localsql' configuration. Otherwise, you just need to make sure you
>> have appropriate maps in the entries.
>
>   technically, i'm sure i don't *need* to nuke all that stuff, but i
> don't know what kind of mess i've made of the turba install thus far
> so, for the sake of cleanliness, i'd just like to simulate as if i was
> starting from scratch, and was handed some old addressbooks from an
> old turba install.  as in, i'd like to test what it would take if
> someone told me, "here, here's some old addressbooks from a 2.0.5
> install -- add turba 2.3.1 to our horde install and add those books
> back in."
>
>   in short, i want to install the latest turba, and bring the
> addressbooks up to date to be compatible with the default, rather than
> go the other way.  (and since i think i've already done those schema
> upgrades, this would only make sense.)
(Continue reading)

Permalink | Reply | 5 comments |

Gmane