ProsePoint

Prosepoint says updates available but can't update

Asked by sanjay

I have very recently installed ProsePoint (0.10) on a local test server. [I have used Drupal for some time and so I am aware of the way modules and themes are updated etc for drupal].

In the status report ProsePoint tells me that "there are updates available for one or more of your modules or themes". I click on the 'Out of date' link which takes me to the available updates.
It shows that there are updates available for Date 6.x-2.0-rc4 (Recommended version: 6.x-2.0-rc6).
I download that tar.gz, untar it and place it into "/sites/all/modules" and hope that ProsePoint will pick up the update but it doesn't. I even try creating a new directory modules in "/sites/default" and repeat the process there but no ProsePoint doesn't find it.

Surely I am missing something but don't know what.

Many thanks in advance.

Sanjay

Question information

Language:
English Edit question
Status:
Solved
For:
ProsePoint Edit question
Assignee:
No assignee Edit question
Solved by:
sanjay
Solved:
Last query:
Last reply:
Revision history for this message
bengtan (bengtan) said : 		#1

Hi,

Your date module should go into .../sites/default (or equivalent) in order to override the ProsePoint version. After unpackaging, there should be a directory .../sites/default/modules/date. Is that what you have? Or have you misspelt a directory?

Revision history for this message
sanjay (san-jaykumar) said : 		#2

The spellings are right, the path is correct. I was wondering about permissions: I also changed the owner and group to www. No difference. I might try reinstalling.

The difference that I noticed between my drupal and prosepoint installations was that the modules directory in '../sites/default' was not created automatically for prosepoint I had to create it manually. Was it because the fatal error I had got "..Max. execution time of 30 secs. exceeeded...". But apart from this update thing the site is working perfectly fine and I must it is a great piece of software. Thanks.

Sanjay

Revision history for this message
bengtan (bengtan) said : 		#3

> Was it because the fatal error I had got "..Max. execution time of 30 secs. exceeeded...".

If you got this error during installation, then the entire database is suspect and possibly corrupt.

However, if you got this error after a successful installation, then it shouldn't be the cause of this problem.

As a test, can I suggest you install some other Drupal module (that isn't included with ProsePoint) into .../sites/default/modules and see if that appears in the modules listing? That will (hopefully) indicate whether there is a fault with the file system, or with ProsePoint code/database.

Also, you are using .../sites/default, yes? And not some special directory like .../sites/my_site_dir ?

Revision history for this message
sanjay (san-jaykumar) said : 		#4

I have reinstalled ProsePoint.

I tried to change the settings in php.ini for max_exec to 300 but then I got error 302 (Safari could be taking the blame here), reset php.ini to what it was before; deleted everything and reinstalled prosepoint. Got the fatal error once again but the site got built nonetheless. Checked the permissions on the prosepoint modules dir (755 1000 1000) and applied the same to sites/default/modules and everything is working now. Even the update has been accepted. I am very pleased.

I am not planning to rebuild the site any time soon but what is the best way to avoid the fatal error.

Thanks

Sanjay