Unable to install on WAMP
Mon, 17/05/2010 - 17:00
WindowsXP Pro
WAMP server 2
Apache 2.2.11
PHP 5.2.11
MySQL 5.1.36
Php MyAdmin
I will start by saying that I have 3 databases already running with Drupal, and it is very easy to add new ones.
I just create the database with Php MyAdmin, change the settings.php file to reflect the database, type in the localhost URL followed by install.php and drupal site is set up.
I have tried the same with Prose Point, but I get these errors
Notice: Undefined index: q in C:\wamp\www\news\includes\path.inc on line 164
Fatal error: Maximum execution time of 30 seconds exceeded in C:\wamp\www\news\includes\file.inc on line 907
I have seen on previous posts about setting the max_execution time to 600 secs but it still times out at 30 (Ordinary Drupal is instant) there are 4 php.ini files and I changed them all as not sure which one I am supposed to be changing, but it didn't make any difference.
I tried to install using PHP 5.3.0 but had deprecated errors although it did install, but not properly
Any thoughts please.
After several hours of playing around with the settings I finally got it to install but the error
Notice: Undefined index: q in C:\wamp\www\news\includes\path.inc on line 164 still exists and when I got to the part of choosing which ProsePoint variant I also got this error
Fatal error: Call to undefined function date_format_save() in C:\wamp\www\news\profiles\prosepoint\prosepoint.profile on line 68
I note there are no content types, is this normal or a corrupted database?
Tue, 18/05/2010 - 19:33
#2
Even though I have left the
Even though I have left the php settings the same I am back to it timing out. It was a complete new installation and new databasse, even given different names.
I cannot run IIS as I am already running WAMP, you can't to my knowledge run the two together, and I have no need for IIS if I'm running WAMP.
So at the moment what looks to be a good idea isn't going to work for me.
Done a complete new reinstall, wiped databases, history etc. First time it loaded and I had 90 items on the database but only got as far as Chose ProsePoint Variant and I just get an error of Problem loading page, connection was reset etc, local server so nothing to do with internet.
Tried again and only get 81 items on the database and still only get to Chose variant and then nothing.
Tue, 18/05/2010 - 21:20
#3
Also tried to load on host
This went OK until I got to the Chose variant again and I get this error
Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 84 bytes) in /home/********/public_html/news/profiles/prosepoint/modules/views/plugins/views_plugin_display.inc on line 234
Have emailed the host asking to increase the memory_limit to 64Mb
Wed, 19/05/2010 - 08:46
#4
...
Hi,
> I cannot run IIS as I am already running WAMP
Oops, I didn't mean to suggest that you try IIS. Some PHP issues or misconfigurations are common to Windows, regardless of whether it's IIS or Apache.
In any case, it looks like you're trying to load it onto a proper server now. After getting your memory_limit increased, please clear out the database and reinstall from scratch.
Once you get the site going on the webhost server, one thing you could try is to then copy/move the site onto your local desktop computer.
Wed, 19/05/2010 - 23:49
#5
I've not heard from the host,
I've not heard from the host, but reading on Drupal, HostPapa wont increase the memory limit so I followed some instructions to add ini_set('memory_limit', '64M'); to the bottom of the settings.php and that worked and it all uploaded.
I exported the database OK and imported OK but still can't get it to run on WAMP
Thu, 20/05/2010 - 09:22
#6
...
You might want to confirm the memory_limit by visiting ...admin/reports/status/php on your site just in case your host doesn't allow ini_set() calls from user files to take effect.
Also, after the higher limit, I hope you installed from scratch rather than continue on from the botched installation (when memory was 32Mb)?
Hi,
> I note there are no content types, is this normal or a corrupted database?
You definitely shouldn't be getting that error message. Something went wrong with installation and you have a corrupted database which you should clean out and reinstall over.
As to how to fix the date_format_save error message in the first place ... I don't know. There have been a couple of reports of this, and I've made suggestion to people to try diagnosing it, but as yet, no one has followed up nor informed me of the details.
You could try looking at IIS/Windows and try some of the things there.
One thing to definitely try is to set your php error_reporting value to E_ALL & ~E_NOTICE