You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
(2) |
Apr
(2) |
May
(24) |
Jun
(1) |
Jul
(6) |
Aug
(1) |
Sep
(3) |
Oct
(2) |
Nov
|
Dec
(1) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Sandy S. <ss...@fo...> - 2003-05-14 14:42:59
|
The SQL to directly update a password for the admin user (substitute 'admin' with any user ID for other users): UPDATE records SET password = ENCRYPT('newpass') WHERE idnum = 'admin' AND datatype = 1; Also, your "organisationtypes" bug may come from the fact that the "type" field gets automagically mapped to the {objectname}types table, where {objectname} is the name of the currently-selected object. If you still have "type" selected for your Organisation object, you will get this error if you do not have an organisationtypes table. -- Sandy Smith, Senior Programmer Forum One Communications, Inc. ss...@fo... tel. 703-548-1855 x28 http://www.forumone.com/ |
From: Sandy S. <ss...@fo...> - 2003-05-14 14:38:02
|
Hi Adrian and Ian-- I would suggest re-updating from CVS all your packages and see if that does not solve your problem. I have been bugfixing for the past week and there may be incompatibilities in your packages as we ramp up to the 0.0.5 release. If that doesn't work, let us know. It should NOT be necessary to delete and reinstall everything. -- Sandy Smith, Senior Programmer Forum One Communications, Inc. ss...@fo... tel. 703-548-1855 x28 http://www.forumone.com/ |
From: Adrian C. <ad...@da...> - 2003-05-14 10:24:09
|
Hi Nyk, Sandy, core, Thanks very much for getting back to me. Re our problem with deleted datatypes reappearing: I've looked through our data objects and our db fields and there's no mention of the offending datatype that I could find. Re our problem with the relationships dropdown not appearing when it should in dbasis: We have updated from CVS in the past few days and have also checked the typesfield table and it uses 'is_unique' not just 'unique'. Re our problem with Context login not working: Context has also been updated from CVS. Can you suggest other ways we can try to isolate and correct these problems other than deleting and reinstalling it all again? Regards, Adrian Regards, Adrian ----- Original Message ----- From: "Nyk Cowham" <nc...@fo...> To: "Adrian Columb" <ed...@da...> Cc: "Randum Ian" <ia...@ra...>; "Websyntax-Core@Lists. Sourceforge. Net" <web...@li...> Sent: Wednesday, 14 May 2003 8:39 Subject: RE: [Websyntax-core] Syntax Datatypes, Relationships dropdown and Context problems > > > > Firstly, when I log in to dbasis, then go to 'data', then select > > > > 'organisation' from > > > > the dropdown menu, then click 'add record' I get the following error: > > > > > > > > Fatal error: mysql error: [1146: Table 'pxdb.organisationtypes' doesn't > > > > exist] in EXECUTE("SHOW COLUMNS FROM organisationtypes") in > > > > /home/danceportal/www/dbasis/includes/errorhandler.inc.php on line 77 > > > > > > > > That error reffers to the 'organisationtypes' datatype that I had > > > > previously created in the datatypes section of dbasis, and then > > subsequently > > > > deleted when I realised it wasn't needed. Should allow us to delete > > > > datatypes without it getting messed up like that? How can we fix it when > > it > > > > does? > > > > > > Normatively it should delete all references to a table that has been > > deleted, but positively it probably isn't doing that currently. > > > Anyhoo, you need to remove any reference to the deleted table from your > > datatype definition (you probably have a field defined that > > > is using that table - or maybe it is a field defined in dbfields. > > > > As we don't fully understand fully how the database works we'd rather not > > mess with it on that level. Can that be fixed so it deletes the correclty? > > It is wise not to try modify the database directly. It is not a big priority for me to fix usability issues with DBasis simply > because it is planned for a complete rewrite as a desktop client app. In the meantime, it is incumbent on the developer to make sure > that objects do not contain links to pick tables that have been deleted. > > > > > Secondly, when I go to the 'objects' section and try to create a field > > in a > > > > datatype in that is a relationship, the relationships dropdown menu > > doesn't > > > > display the list of relationship types (which are defined in the > > > > Relationships section of dbasis) However, when I try to edit one of the > > > > fileds that is predefined as a relationship the dropdown list of > > > > Relationships shows up just fine. > > > > > > This seems to be a new bug that has formed. Probably something to do with > > session persistance. I will put it in the bug tracker. > > > > Cool - can you tell me roughly when do you think that wll be fixed? > > Actually I spoke too soon - it turns out it isn't a bug at all. I replicated the problem on a site I had recently upgraded, but I > realized that I hadn't upgraded DBasis from the CVS too. This problem should go away if you update DBasis from CVS. This is due to a > change in the database schema (renaming the typesfields.unique attribute to typesfields.is_unique). PxDB, DBasis and Context should > all be updated from CVS to be compatible with each other. > > thanks to Sandy for helping to clarify this! > > > > > Thirdly, we can't log in to context with the default username/password > > > > details even though we haven't changed the details. > > > > > > Don't know why that should happen. Seems fine on the new instances that I > > have installed recently. > > > > It doesn't work for us, though it did work previously. > > Again, I think you need to update Context from CVS to be compatible with the new API files (PxDB). > > > Please keep me updated if you have any new info about these problems. > > > > Regards, > > > > Adrian > > > > > > > > Nyk Cowham, Systems Architect > > > Forum One Communications > > > http://www.forumone.com/ > > > Communicate Collaborate Change the world > > > > > > > > > > > > |
From: Randum I. <ia...@ra...> - 2003-05-14 08:01:22
|
> > > Firstly, when I log in to dbasis, then go to 'data', then select > > > 'organisation' from > > > the dropdown menu, then click 'add record' I get the following error: > > > > > > Fatal error: mysql error: [1146: Table 'pxdb.organisationtypes' doesn't > > > exist] in EXECUTE("SHOW COLUMNS FROM organisationtypes") in > > > /home/danceportal/www/dbasis/includes/errorhandler.inc.php on line 77 > > > > > > That error reffers to the 'organisationtypes' datatype that I had > > > previously created in the datatypes section of dbasis, and then > subsequently > > > deleted when I realised it wasn't needed. Should allow us to delete > > > datatypes without it getting messed up like that? How can we fix it when > it > > > does? > > > > Normatively it should delete all references to a table that has been > deleted, but positively it probably isn't doing that currently. > > Anyhoo, you need to remove any reference to the deleted table from your > datatype definition (you probably have a field defined that > > is using that table - or maybe it is a field defined in dbfields. > > As we don't fully understand fully how the database works we'd rather not > mess with it on that level. Can that be fixed so it deletes the correclty? It is wise not to try modify the database directly. It is not a big priority for me to fix usability issues with DBasis simply because it is planned for a complete rewrite as a desktop client app. In the meantime, it is incumbent on the developer to make sure that objects do not contain links to pick tables that have been deleted. > > > Secondly, when I go to the 'objects' section and try to create a field > in a > > > datatype in that is a relationship, the relationships dropdown menu > doesn't > > > display the list of relationship types (which are defined in the > > > Relationships section of dbasis) However, when I try to edit one of the > > > fileds that is predefined as a relationship the dropdown list of > > > Relationships shows up just fine. > > > > This seems to be a new bug that has formed. Probably something to do with > session persistance. I will put it in the bug tracker. > > Cool - can you tell me roughly when do you think that wll be fixed? Actually I spoke too soon - it turns out it isn't a bug at all. I replicated the problem on a site I had recently upgraded, but I realized that I hadn't upgraded DBasis from the CVS too. This problem should go away if you update DBasis from CVS. This is due to a change in the database schema (renaming the typesfields.unique attribute to typesfields.is_unique). PxDB, DBasis and Context should all be updated from CVS to be compatible with each other. thanks to Sandy for helping to clarify this! ---[snip]--- Hi guys, I don't think this is a problem as although I downloaded the latest version from CVS last week I didn't change the attribute of the db table. Is there a SQL command I can type in which will change this? Regards, Ian. |
From: Nyk C. <nc...@fo...> - 2003-05-13 22:39:35
|
> > > Firstly, when I log in to dbasis, then go to 'data', then select > > > 'organisation' from > > > the dropdown menu, then click 'add record' I get the following error: > > > > > > Fatal error: mysql error: [1146: Table 'pxdb.organisationtypes' doesn't > > > exist] in EXECUTE("SHOW COLUMNS FROM organisationtypes") in > > > /home/danceportal/www/dbasis/includes/errorhandler.inc.php on line 77 > > > > > > That error reffers to the 'organisationtypes' datatype that I had > > > previously created in the datatypes section of dbasis, and then > subsequently > > > deleted when I realised it wasn't needed. Should allow us to delete > > > datatypes without it getting messed up like that? How can we fix it when > it > > > does? > > > > Normatively it should delete all references to a table that has been > deleted, but positively it probably isn't doing that currently. > > Anyhoo, you need to remove any reference to the deleted table from your > datatype definition (you probably have a field defined that > > is using that table - or maybe it is a field defined in dbfields. > > As we don't fully understand fully how the database works we'd rather not > mess with it on that level. Can that be fixed so it deletes the correclty? It is wise not to try modify the database directly. It is not a big priority for me to fix usability issues with DBasis simply because it is planned for a complete rewrite as a desktop client app. In the meantime, it is incumbent on the developer to make sure that objects do not contain links to pick tables that have been deleted. > > > Secondly, when I go to the 'objects' section and try to create a field > in a > > > datatype in that is a relationship, the relationships dropdown menu > doesn't > > > display the list of relationship types (which are defined in the > > > Relationships section of dbasis) However, when I try to edit one of the > > > fileds that is predefined as a relationship the dropdown list of > > > Relationships shows up just fine. > > > > This seems to be a new bug that has formed. Probably something to do with > session persistance. I will put it in the bug tracker. > > Cool - can you tell me roughly when do you think that wll be fixed? Actually I spoke too soon - it turns out it isn't a bug at all. I replicated the problem on a site I had recently upgraded, but I realized that I hadn't upgraded DBasis from the CVS too. This problem should go away if you update DBasis from CVS. This is due to a change in the database schema (renaming the typesfields.unique attribute to typesfields.is_unique). PxDB, DBasis and Context should all be updated from CVS to be compatible with each other. thanks to Sandy for helping to clarify this! > > > Thirdly, we can't log in to context with the default username/password > > > details even though we haven't changed the details. > > > > Don't know why that should happen. Seems fine on the new instances that I > have installed recently. > > It doesn't work for us, though it did work previously. Again, I think you need to update Context from CVS to be compatible with the new API files (PxDB). > Please keep me updated if you have any new info about these problems. > > Regards, > > Adrian > > > > > Nyk Cowham, Systems Architect > > Forum One Communications > > http://www.forumone.com/ > > Communicate Collaborate Change the world > > > > > > |
From: Nyk C. <nc...@fo...> - 2003-05-13 21:51:25
|
> Firstly, when I log in to dbasis, then go to 'data', then select > 'organisation' from > the dropdown menu, then click 'add record' I get the following error: > > Fatal error: mysql error: [1146: Table 'pxdb.organisationtypes' doesn't > exist] in EXECUTE("SHOW COLUMNS FROM organisationtypes") in > /home/danceportal/www/dbasis/includes/errorhandler.inc.php on line 77 > > That error reffers to the 'organisationtypes' datatype that I had > previously created in the datatypes section of dbasis, and then subsequently > deleted when I realised it wasn't needed. Should allow us to delete > datatypes without it getting messed up like that? How can we fix it when it > does? Normatively it should delete all references to a table that has been deleted, but positively it probably isn't doing that currently. Anyhoo, you need to remove any reference to the deleted table from your datatype definition (you probably have a field defined that is using that table - or maybe it is a field defined in dbfields. > Secondly, when I go to the 'objects' section and try to create a field in a > datatype in that is a relationship, the relationships dropdown menu doesn't > display the list of relationship types (which are defined in the > Relationships section of dbasis) However, when I try to edit one of the > fileds that is predefined as a relationship the dropdown list of > Relationships shows up just fine. This seems to be a new bug that has formed. Probably something to do with session persistance. I will put it in the bug tracker. > Thirdly, we can't log in to context with the default username/password > details even though we haven't changed the details. Don't know why that should happen. Seems fine on the new instances that I have installed recently. Nyk Cowham, Systems Architect Forum One Communications http://www.forumone.com/ Communicate Collaborate Change the world |
From: Adrian C. <ad...@da...> - 2003-05-13 21:38:38
|
Hi Syntax Core team, We have updated out Syntax install from CVS but are still experiencing some problems. Firstly, when I log in to dbasis, then go to 'data', then select 'organisation' from the dropdown menu, then click 'add record' I get the following error: Fatal error: mysql error: [1146: Table 'pxdb.organisationtypes' doesn't exist] in EXECUTE("SHOW COLUMNS FROM organisationtypes") in /home/danceportal/www/dbasis/includes/errorhandler.inc.php on line 77 That error reffers to the 'organisationtypes' datatype that I had previously created in the datatypes section of dbasis, and then subsequently deleted when I realised it wasn't needed. Should allow us to delete datatypes without it getting messed up like that? How can we fix it when it does? Secondly, when I go to the 'objects' section and try to create a field in a datatype in that is a relationship, the relationships dropdown menu doesn't display the list of relationship types (which are defined in the Relationships section of dbasis) However, when I try to edit one of the fileds that is predefined as a relationship the dropdown list of Relationships shows up just fine. Thirdly, we can't log in to context with the default username/password details even though we haven't changed the details. Anything you can suggest to help us overcome these issues would be most appreciated. Sincerely, Adrian |
From: Nyk C. <nc...@fo...> - 2003-05-09 22:44:22
|
> That's great, I appreciate it. I have got it up and running finally. > > The only problem is when I go to edit some data in the data part of > Dbasis and it crops up with this error which I have forgotten how to > solve. Can anyone shed any light on this? > > ----------[snip]---------- > Warning: [PxDB] You have not set the pxdb_pref for datastore[path] or > datastore[url]. File uploads will not work. in > /home/danceportal/PxDB/classes/pxdb.class.php on line 151 > ----------[snip]---------- > > Cheers, Ian. This is a warning that DBasis gives to remind you to tell Syntax where to store uploaded files and what base URL to give them. Use DBasis and select the Preferences tab. You need to add two preferences: 1. pref_name=datastore, pref_key=path, pref_value=/path/to/upload/files 2. pref_name=datastore, pref_key=url, pref_value=http://www.danceportal/files Nyk > -----Original Message----- > From: Nyk Cowham [mailto:nc...@fo...] > Sent: 09 May 2003 20:36 > To: Randum Ian; web...@li... > Subject: RE: [Websyntax-core] More Database Woes!!! > > I have replicated this error: > > It only happens if you have the 0.0.4 package files and have applied the > changes to the database discussed a few days ago. If you > have the CVS version with those database changes applied everything is > peachy. > > Nyk Cowham, Systems Architect > Forum One Communications > http://www.forumone.com/ > Communicate Collaborate Change the world > > > -----Original Message----- > > From: web...@li... > > [mailto:web...@li...]On Behalf Of Randum > > Ian > > Sent: Wednesday, May 09, 2001 2:09 PM > > To: web...@li... > > Subject: [Websyntax-core] More Database Woes!!! > > > > > > Right, more woes lie ahead! > > > > I re-installed Syntax from the ground up, cleared the db out and put > the > > SQL file in and reinstalled all the various components. I specifically > > checked that the relationships table was correct which it was. I then > > went into Dbasis and tried to modify one of the Datatypes and I got > this > > error > > > > ----------[snip]---------- > > Fatal error: mysql error: [1054: Unknown column 'dt1' in 'where > clause'] > > in EXECUTE("SELECT id FROM relationships WHERE (dt1 = 1 OR dt2 = 1) > > ORDER BY weight") in > > /home/danceportal/www/dbasis/includes/errorhandler.inc.php on line 77 > > ----------[snip]---------- > > > > I then went back and checked the database and the relationships table > > had shrunk to just "id", "description" and "weight". > > > > Can anyone shed any light on what is happening? > > > > Regards, > > Randum Ian > > ia...@ra... > > DancePortalGlobal Webmaster > > http://www.danceportalglobal.com > > > > > > > > > > > > ------------------------------------------------------- > > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > > The only event dedicated to issues related to Linux enterprise > solutions > > www.enterpriselinuxforum.com > > > > _______________________________________________ > > Websyntax-core mailing list > > Web...@li... > > https://lists.sourceforge.net/lists/listinfo/websyntax-core > > > > > > > > > ------------------------------------------------------- > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > The only event dedicated to issues related to Linux enterprise solutions > www.enterpriselinuxforum.com > > _______________________________________________ > Websyntax-core mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/websyntax-core > > |
From: Randum I. <ia...@ra...> - 2003-05-09 22:07:23
|
That's great, I appreciate it. I have got it up and running finally. The only problem is when I go to edit some data in the data part of Dbasis and it crops up with this error which I have forgotten how to solve. Can anyone shed any light on this? ----------[snip]---------- Warning: [PxDB] You have not set the pxdb_pref for datastore[path] or datastore[url]. File uploads will not work. in /home/danceportal/PxDB/classes/pxdb.class.php on line 151 ----------[snip]---------- Cheers, Ian. -----Original Message----- From: Nyk Cowham [mailto:nc...@fo...] Sent: 09 May 2003 20:36 To: Randum Ian; web...@li... Subject: RE: [Websyntax-core] More Database Woes!!! I have replicated this error: It only happens if you have the 0.0.4 package files and have applied the changes to the database discussed a few days ago. If you have the CVS version with those database changes applied everything is peachy. Nyk Cowham, Systems Architect Forum One Communications http://www.forumone.com/ Communicate Collaborate Change the world > -----Original Message----- > From: web...@li... > [mailto:web...@li...]On Behalf Of Randum > Ian > Sent: Wednesday, May 09, 2001 2:09 PM > To: web...@li... > Subject: [Websyntax-core] More Database Woes!!! > > > Right, more woes lie ahead! > > I re-installed Syntax from the ground up, cleared the db out and put the > SQL file in and reinstalled all the various components. I specifically > checked that the relationships table was correct which it was. I then > went into Dbasis and tried to modify one of the Datatypes and I got this > error > > ----------[snip]---------- > Fatal error: mysql error: [1054: Unknown column 'dt1' in 'where clause'] > in EXECUTE("SELECT id FROM relationships WHERE (dt1 = 1 OR dt2 = 1) > ORDER BY weight") in > /home/danceportal/www/dbasis/includes/errorhandler.inc.php on line 77 > ----------[snip]---------- > > I then went back and checked the database and the relationships table > had shrunk to just "id", "description" and "weight". > > Can anyone shed any light on what is happening? > > Regards, > Randum Ian > ia...@ra... > DancePortalGlobal Webmaster > http://www.danceportalglobal.com > > > > > > ------------------------------------------------------- > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > The only event dedicated to issues related to Linux enterprise solutions > www.enterpriselinuxforum.com > > _______________________________________________ > Websyntax-core mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/websyntax-core > > |
From: Nyk C. <nc...@fo...> - 2003-05-09 19:36:04
|
I have replicated this error: It only happens if you have the 0.0.4 package files and have applied the changes to the database discussed a few days ago. If you have the CVS version with those database changes applied everything is peachy. Nyk Cowham, Systems Architect Forum One Communications http://www.forumone.com/ Communicate Collaborate Change the world > -----Original Message----- > From: web...@li... > [mailto:web...@li...]On Behalf Of Randum > Ian > Sent: Wednesday, May 09, 2001 2:09 PM > To: web...@li... > Subject: [Websyntax-core] More Database Woes!!! > > > Right, more woes lie ahead! > > I re-installed Syntax from the ground up, cleared the db out and put the > SQL file in and reinstalled all the various components. I specifically > checked that the relationships table was correct which it was. I then > went into Dbasis and tried to modify one of the Datatypes and I got this > error > > ----------[snip]---------- > Fatal error: mysql error: [1054: Unknown column 'dt1' in 'where clause'] > in EXECUTE("SELECT id FROM relationships WHERE (dt1 = 1 OR dt2 = 1) > ORDER BY weight") in > /home/danceportal/www/dbasis/includes/errorhandler.inc.php on line 77 > ----------[snip]---------- > > I then went back and checked the database and the relationships table > had shrunk to just "id", "description" and "weight". > > Can anyone shed any light on what is happening? > > Regards, > Randum Ian > ia...@ra... > DancePortalGlobal Webmaster > http://www.danceportalglobal.com > > > > > > ------------------------------------------------------- > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > The only event dedicated to issues related to Linux enterprise solutions > www.enterpriselinuxforum.com > > _______________________________________________ > Websyntax-core mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/websyntax-core > > |
From: Randum I. <ia...@ra...> - 2003-05-09 18:08:56
|
Right, more woes lie ahead! I re-installed Syntax from the ground up, cleared the db out and put the SQL file in and reinstalled all the various components. I specifically checked that the relationships table was correct which it was. I then went into Dbasis and tried to modify one of the Datatypes and I got this error ----------[snip]---------- Fatal error: mysql error: [1054: Unknown column 'dt1' in 'where clause'] in EXECUTE("SELECT id FROM relationships WHERE (dt1 = 1 OR dt2 = 1) ORDER BY weight") in /home/danceportal/www/dbasis/includes/errorhandler.inc.php on line 77 ----------[snip]---------- I then went back and checked the database and the relationships table had shrunk to just "id", "description" and "weight". Can anyone shed any light on what is happening? Regards, Randum Ian ia...@ra... DancePortalGlobal Webmaster http://www.danceportalglobal.com |
From: Sandy S. <ss...@fo...> - 2003-05-08 14:54:13
|
Yes, it should. As I noted elsewhere, we'll have to modify the script to changes can be incrementally upgraded so v0.0.3->0.0.4 changes aren't applied to an 0.0.4 installation. On Thursday, May 8, 2003, at 10:50 AM, Nyk Cowham wrote: > Sandy: > > I think we are due for another alpha release before our first beta > release. We can coordinate so installing 0.0.5 will also check > for the database version. This should make things easier, no? > > Nyk Cowham, Systems Architect > Forum One Communications > http://www.forumone.com/ > Communicate Collaborate Change the world > >> -----Original Message----- >> From: web...@li... >> [mailto:web...@li...]On Behalf Of Sandy >> Smith >> Sent: Tuesday, May 06, 2003 2:53 PM >> To: web...@li... >> Subject: [Websyntax-core] upgrade issues >> >> >> The fix to use 'is_unique' in typesfields I just checked in does break >> nastily when put on an older version. I've put in code in the >> mysql_upgrade script to update this, but short of a version change it >> won't trigger. (the upgrade change isn't in CVS yet because >> Sourceforge >> is having issues again) >> >> Should we put in instructions for what to do if you're using v.0.0.4? >> Or should we just force this check to happen any time run-once is >> executed? >> >> -- >> Sandy Smith, Senior Programmer >> Forum One Communications >> <ss...@fo...> >> http://www.forumone.com/ >> tel. (703) 548-1855 x28 >> >> >> >> ------------------------------------------------------- >> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara >> The only event dedicated to issues related to Linux enterprise >> solutions >> www.enterpriselinuxforum.com >> >> _______________________________________________ >> Websyntax-core mailing list >> Web...@li... >> https://lists.sourceforge.net/lists/listinfo/websyntax-core >> >> > > -- Sandy Smith, Senior Programmer Forum One Communications, Inc. ss...@fo... tel. 703-548-1855 x28 http://www.forumone.com/ |
From: Nyk C. <nc...@fo...> - 2003-05-08 14:49:59
|
Sandy: I think we are due for another alpha release before our first beta release. We can coordinate so installing 0.0.5 will also check for the database version. This should make things easier, no? Nyk Cowham, Systems Architect Forum One Communications http://www.forumone.com/ Communicate Collaborate Change the world > -----Original Message----- > From: web...@li... > [mailto:web...@li...]On Behalf Of Sandy > Smith > Sent: Tuesday, May 06, 2003 2:53 PM > To: web...@li... > Subject: [Websyntax-core] upgrade issues > > > The fix to use 'is_unique' in typesfields I just checked in does break > nastily when put on an older version. I've put in code in the > mysql_upgrade script to update this, but short of a version change it > won't trigger. (the upgrade change isn't in CVS yet because Sourceforge > is having issues again) > > Should we put in instructions for what to do if you're using v.0.0.4? > Or should we just force this check to happen any time run-once is > executed? > > -- > Sandy Smith, Senior Programmer > Forum One Communications > <ss...@fo...> > http://www.forumone.com/ > tel. (703) 548-1855 x28 > > > > ------------------------------------------------------- > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > The only event dedicated to issues related to Linux enterprise solutions > www.enterpriselinuxforum.com > > _______________________________________________ > Websyntax-core mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/websyntax-core > > |
From: Randum I. <ia...@ra...> - 2003-05-08 13:20:51
|
Hi Sandy, Thanks for getting back to me. I am lead to believe that the CVS copy hasn't overwritten the original as I previously thought. I will make sure that I download the latest CVS version tonight and rename the old one before copying it across I should have the updated version on there. 1 question I do have is when do I use the upgrade.php script you mention below? Everytime I download from CVS or major updates? Would this go some way to solving my error? Regards, Ian. > I assume this is in the relationships table. I'm not sure why the > fields dt1 and dt2 should be deleted, but they were never used by the > system--it was an experimental feature that was never completed, so I > took it out. It should be fine to leave them out of that table as they > don't do anything. > > Now, if this is causing you database errors, be sure of two things: > > a) that the CVS copies are really overwriting these files. The most > offensive ones are in PxDB/classes/metadata and in DBasis/datatypes. > > b) that you re-name the 'unique' field in typesfields to 'is_unique'. > That isn't caught by the upgrade script currently. > > I have that code working on three sites in-house. If you still get > errors, post the text of them here and I'll take a look at them. > > On Thursday, May 8, 2003, at 04:21 AM, Randum Ian wrote: > >> Morning guys, >> >> We are in the process of implementing Syntax on our server now and we >> have >> updated to the latest version on CVS as of Tuesday. We are having >> serious >> problems with fields not being found in our database when we try to >> add records with Dbasis namely dt1 and dt2. We add these fields back >> but they >> disappear just as fast. I noticed that this problem was noted and a >> fix was >> implemented so would it be best to just delete the db and apply the >> sql file and make a fresh instance of the tables. Would the errors go >> away are >> is it something else that we should be noting? >> >> Regards, >> Randum Ian >> ia...@ra... >> DancePortalGlobal Webmaster >> http://www.danceportalglobal.com >> >> >> >> ------------------------------------------------------- >> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara >> The only event dedicated to issues related to Linux enterprise >> solutions >> www.enterpriselinuxforum.com >> >> _______________________________________________ >> Websyntax-users mailing list >> Web...@li... >> https://lists.sourceforge.net/lists/listinfo/websyntax-users >> >> > -- > Sandy Smith, Senior Programmer > Forum One Communications > <ss...@fo...> > http://www.forumone.com/ > tel. (703) 548-1855 x28 Randum Ian ia...@ra... DancePortalGlobal Webmaster http://www.danceportalglobal.com |
From: Sandy S. <ss...@fo...> - 2003-05-08 13:16:38
|
I assume this is in the relationships table. I'm not sure why the fields dt1 and dt2 should be deleted, but they were never used by the system--it was an experimental feature that was never completed, so I took it out. It should be fine to leave them out of that table as they don't do anything. Now, if this is causing you database errors, be sure of two things: a) that the CVS copies are really overwriting these files. The most offensive ones are in PxDB/classes/metadata and in DBasis/datatypes. b) that you re-name the 'unique' field in typesfields to 'is_unique'. That isn't caught by the upgrade script currently. I have that code working on three sites in-house. If you still get errors, post the text of them here and I'll take a look at them. On Thursday, May 8, 2003, at 04:21 AM, Randum Ian wrote: > Morning guys, > > We are in the process of implementing Syntax on our server now and we > have > updated to the latest version on CVS as of Tuesday. We are having > serious > problems with fields not being found in our database when we try to add > records with Dbasis namely dt1 and dt2. We add these fields back but > they > disappear just as fast. I noticed that this problem was noted and a > fix was > implemented so would it be best to just delete the db and apply the sql > file and make a fresh instance of the tables. Would the errors go away > are > is it something else that we should be noting? > > Regards, > Randum Ian > ia...@ra... > DancePortalGlobal Webmaster > http://www.danceportalglobal.com > > > > ------------------------------------------------------- > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > The only event dedicated to issues related to Linux enterprise > solutions > www.enterpriselinuxforum.com > > _______________________________________________ > Websyntax-users mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/websyntax-users > > -- Sandy Smith, Senior Programmer Forum One Communications <ss...@fo...> http://www.forumone.com/ tel. (703) 548-1855 x28 |
From: Randum I. <ia...@ra...> - 2003-05-08 07:56:09
|
Morning guys, We are in the process of implementing Syntax on our server now and we have updated to the latest version on CVS as of Tuesday. We are having serious problems with fields not being found in our database when we try to add records with Dbasis namely dt1 and dt2. We add these fields back but they disappear just as fast. I noticed that this problem was noted and a fix was implemented so would it be best to just delete the db and apply the sql file and make a fresh instance of the tables. Would the errors go away are is it something else that we should be noting? Regards, Randum Ian ia...@ra... DancePortalGlobal Webmaster http://www.danceportalglobal.com |
From: Sandy S. <ss...@fo...> - 2003-05-06 18:52:44
|
The fix to use 'is_unique' in typesfields I just checked in does break nastily when put on an older version. I've put in code in the mysql_upgrade script to update this, but short of a version change it won't trigger. (the upgrade change isn't in CVS yet because Sourceforge is having issues again) Should we put in instructions for what to do if you're using v.0.0.4? Or should we just force this check to happen any time run-once is executed? -- Sandy Smith, Senior Programmer Forum One Communications <ss...@fo...> http://www.forumone.com/ tel. (703) 548-1855 x28 |
From: Nyk C. <nc...@fo...> - 2003-04-29 14:27:12
|
Hi Adrian: I think this is the same problem as the bug that has been reported in the bugtracker: http://sourceforge.net/tracker/index.php?func=detail&aid=693873&group_id=69167&atid=523627 Sandy reports that this seems to be fixed in the latest CVS version. Try updating DBasis from CVS and that should remove the problem. If you are still having issues let us know and we will take another look at it. Nyk Cowham, Systems Architect Forum One Communications http://www.forumone.com/ Communicate Collaborate Change the world > -----Original Message----- > From: web...@li... > [mailto:web...@li...]On Behalf Of Adrian > Columb > Sent: Sunday, April 27, 2003 9:51 AM > To: web...@li... > Subject: [Websyntax-core] Fw: Syntax datatype error! > > > Hi Syntax developers, > > We have a reoccurring problem with Syntax - somehow the dt1 column keeps > getting deleted. When I try to edit a datatype's name it comes back with an > error as follows: Fatal error: mysql error: [1054: Unknown column 'dt1' in > 'where clause'] in EXECUTE("SELECT id FROM relationships WHERE (dt1 = 1 OR > dt2 = 1) ORDER BY weight")in > /home/danceportal/www/dbasis/includes/errorhandler.inc.php on line 77 > > That's been there since we installed it and keeps reoccurring - when we > recreate the dt1 column in the database it just gets deleted again. Do you > know how we can fix this problem? > > Regards, > > Adrian > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Websyntax-core mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/websyntax-core > > |
From: Adrian C. <ad...@da...> - 2003-04-27 13:50:55
|
Hi Syntax developers, We have a reoccurring problem with Syntax - somehow the dt1 column keeps getting deleted. When I try to edit a datatype's name it comes back with an error as follows: Fatal error: mysql error: [1054: Unknown column 'dt1' in 'where clause'] in EXECUTE("SELECT id FROM relationships WHERE (dt1 = 1 OR dt2 = 1) ORDER BY weight")in /home/danceportal/www/dbasis/includes/errorhandler.inc.php on line 77 That's been there since we installed it and keeps reoccurring - when we recreate the dt1 column in the database it just gets deleted again. Do you know how we can fix this problem? Regards, Adrian |
From: Hans L. <ha...@ve...> - 2003-03-18 18:53:14
|
Hi Adrian, Sorry for the delay in response. Inicidentally, I am actually no longer the tech lead for the PHlexDB project [I need to update the phlexdb.org site] -- the project has evolved into the Syntax project and you can learn more from: http://syntax.forumone.com/ . There is some new documentation there -- and links to new, more up-to-date sourceforge project. I'm glad, however, to see that you're interested in using the suite of tools -- and I hope that it serves your purpose. Yes, Syntax currently does require register_globals to be on -- although I this is really only a requirement for the administration / db setup tools, and not the public site. register_globals in PHP means that variables sent to a script via GET or POST (or cookies) automatically become part of the global namespace. Take a look at http://www.zend.com/manual/security.registerglobals.php to understand the security implications of this. I am copying the websyntax-core list, so feel free to post to that list if you have other questions, etc. Good luck. Cheers, Hans Adrian Columb wrote: >Hi Hans, > >I'm very impressed by PhlexDB/Syntax from reading all about it on your site. >I am now considering installing it for managing content on my site >http://www.danceportalglobal.com/. I was wondering if you could explain to >me the security implications of having register globals = ON, as it is >mentioned as a known flaw of the software? Otherwise it sounds great. > >Best, > >Adrian > > > |
From: Jase R. <jro...@fo...> - 2003-03-07 18:38:30
|
who's on here so far? i see there are no mailman archives yet... |