So I installed Trends 3.0 by copying over the existing directory in the pepper folder, as instructed by the read-me and then reloading Mint in the browser. No go. Instead, it asked me if I wanted to uninstall a part of Trends. So I did. Then I relaunched the browser and went to Mint preferences to reinstall Trends. It doesn’t show up as available for reinstall and it’s not showing as an active pane. I blow away the directory for Trends in the pepper folder and recopy it over. Trends still does not show up in Preferences. The permissions seem okay with other pepper. What gives? Further, why does it seem like every day since I installed Mint 2.0 I lose another pepper? Fresh View, Sparks, Session Tracker, Trends, and now, seemingly as a result of whatever mischief Trends 3.0 is up to, the map is not displaying in GeoMint.
Trends 3.0 problem
Just curious, you mentioned your having issues with other Peppers. Are they doing the same exact thing that Trends did?
I seem to be having a similar problem (but only with Trends, not other peppers) — it didn’t show up at first, I changed some 644 permissions, it showed up once, but it’s gone again.
Andrew
I’ve now updated to Mint 2.02 (which I had no idea was available) and changed the permissions on Trends 3.0 and all seems to be working. The problem seems to be that the new SFTP client I am using did not give the files the proper execution permission.
I’ve had a problem upgrading Trends as well (using Mint 2.02). I followed the instructions and now when I view the Preferences page, only half loads. To be as clear as possible… the Mint and Pane Order columns appear, but with no background image, and the Pepper column doesn’t appear at all (most likely creating the background image problem for the other columns).
Viewing Mint itself doesn’t show “errors” per say, but Trends Internal reports:
Hits Comparing 0 Minutes to Previous 0 Minutes % +/- There are no pages which meet this requirement.
And Trends External shows stats revolving around the past 0 minutes.
I assume these flaws are as a result of something going wrong, I’m just not sure where to start hunting it down.
I apologize for the people who are having trouble getting Trends to install. The last couple of versions I’ve released had permissions set wrong due to a bug in my ZIP program. It seems to really have borked up some people’s installations.
The people who are candidates to experiencing it are on Unix based systems like OS X. Unfortunately the only way to remedy it is to remove all traces of Trends. Browse to your mint/pepper folder and completely delete the brettdewoody folder. Then, redownload the latest Trends from the Peppermill. Be sure to extract it somewhere other than where your previous version was extract. Then reupload to the mint/pepper directory.
All should be well now. If not, make sure the folders and files of Trends are CHMODed to 755. If you followed all of these steps and Trends still is not working, please contact me.
That seemed to fix the issue I was having, Ronald. I did have to change the permissions before uploading. Thanks
Er, I think it’s still not right. The permissions didn’t come out as 755 in my install. They came out -rwx———
A
Ron, as I mentioned elsewhere, I double-checked the permissions on the pepper install yesterday and everything was set to 755 (directory, subdirectory and files). But, just to be sure, I went through the process one more time this morning.
Unzipped locally (with BOMArchiveHelper), the directories were properly set to 755, but the files were set to 700. So, I changed them to 755, uploaded everything to the server one more time and…
…it works perfectly.
Again, I swear I checked the permissions yesterday, so there are really only two possible explanations:
- Idiotic user error.
- Mysterious UNIX filesystem permissions anomalies that were, at some point during the night, fixed by the ext3 elves.
My money is on #2…
I’ve contacted the developer of my ZIP program. Maybe he didn’t completely fix the bug.
Let me stress that it was my own idiotic user error, not yours. (I’m not sure I was clear on that point.) I’m sure the permissions problems were there yesterday, but I missed it somehow.
So, I apologize for making you spend more time on a problem that you’d already resolved.
You must be logged in to reply. Login above or create an account