IIS/Windows
Thu, 15/04/2010 - 17:07
Have tried installing Prosepoint with IIS7 on a Windows 7 machine, using the Microsoft URL rewrite module.
It almost works, but for the install script failing after selecting 'demo system' type with the following error:
Notice: Undefined index: q in
C:\inetpub\wwwroot\Prosepoint\includes\path.inc on line 164
Fatal error: Call to undefined function date_format_save() in C:\inetpub\wwwroot\Prosepoint\profiles\prosepoint\prosepoint.profile on line
68
PHP Notice: Undefined index: q in
C:\inetpub\wwwroot\Prosepoint\includes\path.inc on line 164 PHP Fatal error:
Call to undefined function date_format_save() in C:\inetpub\wwwroot\Prosepoint\profiles\prosepoint\prosepoint.profile on line
68
Subsequently, having manually set the theme to tma2 and enabled all the modules, it seems to work.
Any ideas how to fix this?
It works fine under Apache on Windows XP - anyone tried with Apache on Windows 7?
Sat, 17/04/2010 - 04:00
#2
Hi Ben
>and see around line
Hi Ben
>and see around line 1883 whether there is a line starting with function date_format_save in it?
Yes, that function is present.
> visit the url .../admin/build/modules on your site and see whether the module Date API is enabled?
No, the Date API module is not enabled. In fact no modules except Color, Comment, Help, Menu and Update status are enabled.
That state is as-is immediately after the install script has failed.
Sat, 17/04/2010 - 15:20
#3
...
Hi,
Now that is odd.
So the error message 'Call to undefined function date_format_save() ...' is because the module date_api.module is not enabled.
But why would those 5 ish modules (Color, Comment, Help, Menu, Update) be enabled but not others (like Taxonomy and Path)? That's puzzling.
I'll have to think about this, and maybe do some Googling as well.
Certainly your site isn't installed properly so I wouldn't recommend you use it for anything serious.
Here's a suggestion to try:
Can you raise your PHP memory_limit to something large (ie. maybe 256M) and max_execution_time to something large (ie. maybe 600 seconds), clear out your database, and then try a full reinstall?
In the meantime, I'll see what else I can find.
Thank you.
Sun, 18/04/2010 - 01:10
#4
Fixed it.(Reading the
Fixed it.
(Reading the documentation - even as a last resort, often pays dividends!)
It appears that the problem was caused by the php error reporting setting, which needs to be:
E_ALL & ~E_NOTICE
according to the Drupal install requirements, and it isn't by default.
I also had to stretch the maximum script execution time value quite a lot to get through the final part of the install script without error.
As a result, I can now at least confirm that it is possible to run the Prosepoint install process without any major errors running under IIS7 on Windows 7, using Microsoft's url rewrite module. Furthermore, the site appears to work ok, but I haven't done much testing yet. Setting up the url rewrite module was quite easy - it can generate it's own config settings by reading the .htaccess file supplied with Prosepoint, and these end up sitting in a web.config file in the application root directory.
Getting MySQL to run on Windows 7 was another battle, and there are lots of notes about this on the web. My hints/suggestions would be: don't use the msi installer, don't install it in 'Program Files' and edit the windows/system32/drivers/etc/hosts file to remove the IPV6 ::1 localhost entry.
Thanks for your help Ben.
Sun, 18/04/2010 - 10:52
#5
...
Hi,
Are you sure changing error_reporting to E_ALL & ~E_NOTICE is sufficient to fix this issue? Did you go through with a full re-installation?
Strange ... because the error_reporting setting should only affect the 'Notice: Undefined index: q in ...' messages which are just warning message. It shouldn't have affected the 'Fatal error: Call to undefined function date_format_save() ...' mesages which are fatal error messages. Perhaps you also did something else which was the true fix (ie. like increasing the PHP resources, perhaps?).
> Setting up the url rewrite module was quite easy - it can generate
> it's own config settings by reading the .htaccess file
Good to know. I presume everytime you change .htaccess, this web.config file needs to be regenerated?
(At one point, was going to point you to this post:
Local installations of Drupal on Windows Vista load slowly or fail
http://drupal.org/node/222808
since it looked like it contained some potentially useful information, but maybe it's not needed anymore)
Well, thank you for reporting back. If you do encounter any other issues or bugs, do please let me know.
Mon, 19/04/2010 - 04:18
#6
As it happens, I did also
As it happens, I did also increase the php memory allocation but that alone didn't seem to help at the time. I can't be sure now though whether I cleared the database after that step, before changing the error setting. Having now seen the install work (again) though, it was noticeable that when it didn't work, the ajax status page which lists the modules being installed either didn't appear, or flashed by very quickly.
As for the .htaccess file - yes you would need to re-import the MS url rewriter settings after changing it, but I'd guess that given sufficient understanding of how the htaccess settings work, editing the web.config file shouldn't be too difficult as the relevant section is quite similar. The web.config file can contain much more stuff relevant to other (MS .net) applications though so it may look complex to the uninitiated, and its contents can be inherited from parent directories.
Interestingly (?) the link you gave refers to a page describing problems caused by IPV6 stuff in Vista - an issue I encountered earlier while trying to get MySQL to work on Windows 7.
Another suggestion I was working up to (while I'm here - it's not relevant to the rest of the thread, sorry!) is to perhaps consider beefing up the video player facilities in Prosepoint, please? I realise this can be done outside of Prosepoint, and I have experimentally hacked the pp_media.module slightly myself to use a different player which includes control buttons etc. (in IE anyway) - but having this there by default with support for a wider range of file types could be handy.
Hi,
The warning messages 'Notice: Undefined index: q in ...' can be safely ignored.
The error message 'Call to undefined function date_format_save() ...' is the one causing your problem and it's puzzling why PHP can't find the function definition for date_format_save(). This has been reported before by other people, but I never got any meaningful feedback on how it was fixed (if at all).
If you have the patience, it would be great if you could dig around in your server for me ...
Can you use a text editor (ie. wordpad or some other editor) and load the file (presuming I guess the paths and backslashes correctly) ...
C:\inetpub\wwwroot\Prosepoint\profiles\prosepoint\modules\date\date_api.module
and see around line 1883 whether there is a line starting with function date_format_save in it?
Also, on your current site, can you please visit the url .../admin/build/modules on your site and see whether the module Date API is enabled?
If you could report back these two points, that would be very helpful.
Unfortunately, although it seems like your site has been installed and is working, that's not really the case. The fatal error would have prevented a lot of the ProsePoint site configuration from executing, so you will likely to encounter many small bugs or misconfigurations.
I'd suggest (after we clear up this issue) that you clear out your database and reinstall again from scratch.