Updated Information:
To attempt to fix the problem, we've migrated to a new host provider with servers running MySQL 5.0.27, reinstalled Sugar4.1.2 on the new server, copied the MySQL data from our old server to the new server, then upgraded Sugar to 4.5.1b on the new server. I can't believe that we still cannot export certain Contacts to a csv file. This is a critical problem for us. We can see the records, and edit them, but they will not export.
Lastly, we decided to take another look at the raw records using phpmyadmin. We've browsed the records in the contacts table and have noted something that we find very odd. Most all of the records have a value of "1" in the deleted column, including our real data and the sample data. A record that we can't export has a value of "0" (we only looked for this one record). When we changed that record in phpmyadmin to "1" we can't see the record any longer in Sugar, which is logical but leads to this question. Why do most all of the records have "1" for deleted, yet can be seen and exported, and one record has "0" for deleted, can be seen but not exported, and if we change it to "1" can't be seen therefore can't be exported?
We could really use some help here.
Tom
Original Post:
Running version 4.2.1b on Linux (shared host 1and1)
Apache 1.3.33
mysql 4.0.25
PHP 4.4.4
I've noticed that when I export a list of Contacts, not all contacts displayed will export to the csv file. When I specifically tag the "missing" records in question and export just those records, I create a csv file with only a header line, no records. Looking at several records that fail to export, I can find no pattern to suggest why they are not exporting. The records display correctly, I can edit them, but I can't export them.
I couldn't find any record of this problem in the forums, so any assistance would be appreciated.
Tom


LinkBack URL
About LinkBacks



Reply With Quote
Bookmarks