Drupal custom module failing to install - module

I have created a module on a development server (xampp) all is fine and working. However when I have move the module to my production server it fails to install properly, WSOD. From db I can see that my fields are not being created.
Drupal version 7.27 on both, both clean installs with the same dependencies installed.
Nothing in apache error log.
Grateful for any tips.
Mathew

ok just incase this helps someone else further down the line - this was an issue with different versions on PHP on the two servers one had 5.3 the other 5.5. One supports short form arrays [] and one does not which was my problem.
Would i have been able to resolve this from PHP logs?

Related

Upgrading from Glassfish 2.1.1 to Glassfish 4.1

Can someone please enlighten me. I'm trying to upgrade my Glassfish 2.1.1 to Glassfish 4.1. I've decided to do a side by side install as indicated here: https://docs.oracle.com/cd/E26576_01/doc.312/e24942/upgrading-legacy-installation.htm#GSUPG00039
Question are:
(1) What is "as-install"? There's no such directory as-install\bin in my extracted glassfish4 so I assumed it is the installation directory? Is it glassfish4\bin or glassfish4\glassfish\bin?
(2) I can't see the asupgrade.bat file in my glassfish 4.1 so I'm not able to proceed with the steps on the above link. I'm not sure if the version is related since the document specifically says "upgrade to GlassFish Server 3.1". I can see a pkg directory, and there's also an updatetool.bat. I can't run the upgrade tool though since I'm in a closed environment (no internet).
(3) Is it okay to just delete the Sun folder (for Sun Glassfish Enterprise Server v2.1.1) and replace it with the glassfish4 folder (for Glassfish4.1)? Then I will just run my updated installer that supports the new server. Fresh install works, however we also want to try upgrade.
(4) Assuming #3 is not possible, are there any other way?
Sorry to ask this here since I'm not familiar to any Oracle/Sun community. Google search' top results doesn't specifically answer these questions.
UPDATE: Apparently, I found a similar unanswered thread here: Where is the Glassfish 4 upgrade tool . Same issue, upgradetool is no where to be found. Also, tried to connecting to internet and I still can't update it via updatetool.bat.
UPDATE2: Apparently, updatetool.bat doesn't work for Glassfish4.1. I tried running it/installing it so that the upgradetool might be visible but it seems it can't download the application packages.

Outdated version of Zend Engine API

I am hosting a website, using the Symfony framework, on a MAMP server on my Mac, and I'm trying to generate bundles automatically with the help of the terminal.
If it is relevant in any way, here is what I try to type into the terminal:
php -c /Applications/MAMP/bin/php/php5.4.10/conf/php.ini php
app/console generate:bundle
And here is the error I get:
XCache requires Zend Engine API version 220100525. The Zend Engine API
version 220090626 which is installed, is outdated.
Could not open input file: php
Do any of you have an idea of how I could update the Zend Engine API or otherwise fix my problem? That would be of HUGE help!
Edit:
Thanks to the help of whistlergreg I've gotten rid of one of the problems it seems, but I still get the following response:
Could not open input file: php
Edit:
I was told by someone that the second php in my command shouldn't be there. Instead I should write:
php -c /Applications/MAMP/bin/php/php5.4.10/conf/php.ini app/console
generate:bundle
It seems like the second error was caused by a noobish typo by me, and now everything is working.
Note: With Xcache 3.0, xcache.so is no longer a Zend Extension but a PHP extension
remove zend_extension = */xcache.so
load it using extension = xcache.so
This might be why the error is being thrown:
The main cause for the error is because of outdated build of XCache
(not related to its actual version though), that mostly happens when
user upgrades PHP version. When compiling and building XCache, it’s
been associated with the version of Zend Engine API that exists on the
system at the time.
When PHP is updated or upgraded, the Zend Engine API is updated too, causing XCache module to fail as the version no longer matched.
The solution for the Zend Engine API version is newer error is pretty
simple. Just download, compile and install XCache again will fix and
resolve the issue permanently (until new PHP major version update). 1
Switch MAMP to use APC from the MAMP preferences menu, that worked for me! Make sure you restart apache after making the change.

Trying to transfer older version of mediawiki to new server

So, in college I had a Debian server which used to host a wiki, with mediawiki version 1.9. This server stopped working, and all I have now is its HD. I want to transfer this wiki to a new server, which also runs Debian, but I can't do that with Debian's current stable version of mediawiki, 1.15, because it is not possible to transfer a wiki to another version of mediawii.
So, my idea is to install mediawiki 1.9 on the new server, and then move the wiki. But I am having problems with installing it.
When I go to http://my_hostname/config/index.php, to configure the new wiki, so that I can transfer the other one, I get the following message, and nothing happens:
Checking environment...
Please include all of the lines below when reporting installation problems.
PHP 5.3.3-7+squeeze8 installed"
I really don't have a clue on what is wrong. ANY help would be greatly appreciated!
Like you commented yourself, it would certainly be worth a try to using your existing configuration. The configuration is typically some site preferences and database configuration, so make sure dat your database is setup in the same way as before.
Regarding your configuration problems, maybe php filters away the errors. You can check this by searching for error_reporting in your php.ini.
Just follow the instructions at http://www.mediawiki.org/wiki/Manual:Upgrading. Probably no point in trying to install at MediaWiki 1.9.
You may want to do a clean install of MediaWiki 1.18.1 first just to make sure your system is ready, all dependencies met, etc.

Any luck with mod_libpq under Apache 2.2 and/or win32?

Has anyone had luck compiling mod_libpq for Apache 2? I know there were some fairly major changes so the source might have to be updated, but has it been done already by someone?
Also, has it been compiled for win32 (either version of Apache, or another web server altogether?)
I've written an updated version for Apache2.2 which can be downloaded from
http://asmith.id.au/source/mod_libpq2.c
However, it is my first attempt at writing a module for Apache2 and it is not debugged yet.
Previously I had no use for it as I was still using Apache1.3 but since I am now faced with retiring that old server I guess I'll have to finish off the new version.

Joomla Mootools file getting truncated

I am trying to run Joomla on my local machine. I have installed wamp 2.0 and everything installed ok with it and I managed to see it running. I have now come to install Joomla 1.5.18 but I am having a problem with the mootools file on the installation wizard.
When running through the installation process in FireFox with firebug turned on I get errors about the mootools file missing a }. When I view the file through windows explorer it is complete and everything is fine with it but when I click on the error in firebug to see the error the file is truncated which I assume is why it is not working and complaining about a missing }. To test the file I created a test page which pulls in the same mootools file and this works fine (running locally and not through Joomla ).
Does anyone know why this is happening and how to fix it? I think it must be a problem with wamp as like I said the file is fine and runs ok if I run it from the file system, however I know nothing about servers so this is a guess. Maybe a limit on the size of a file which can be returned as the mootools file is around 7000 characters long.
I have tried un-installing both Joomla and Wamp but none this has not worked and I still get the same error. Thanks
I'm just curious, have you tried installing a newer version of Joomla? 1.5.8 is a little bit old and you may have better luck using something a version or two newer. Alternately speaking, if you're not a big fan of installing WAMP and then manually installing Joomla, you can use a Bitnami Joomla stack. Basically, Bitnami installs Apache, mySQL, PHP, and Joomla all in one quick and easy install.
I hope that some of this helps!
I would suggest that your problem is not with the Mootools package but with your template or modules that are loaded in. Can you turn off all of your modules and reenable them one by one until you see the error again?