Problem installing Content Field extension
This is an open discussion with 8 replies, filed under Extensions.
Search
Is the extension directory called exactly content_field
?
Yes the directory is exactly 'content_field' and I am using Symphony 2.3. As far as I can tell the problem seems to be an issue with the file paths when installed on a MAMP setup. No problems so far with a vanilla Apache install on OSX.
My guess is that your MAMP dev environment is running PHP5.2. The __DIR__
constant was added in PHP 5.3. Updating MAMP to a recent version should solve the issue
I bet that is it! I dont have that dev machine with me right now but will check it later. Thanks for answering -- MAMP can be both a blessing and a curse...
Answer confirmed.
I just switched the require directories to relative ref, seemed to work fine.
require_once 'libs/message-stack.php'; require_once 'libs/content-type.php'; require_once 'libs/text-content-type.php';
Any reason this might be an issue? I guess using an absolute path is better practice, but I can't see an actual problem with adapting it this way.
Sadly I don't have the capacity to update my stack, stupid shared hosting. Moving to VPS as soon as I can convince my client it's worth the outlay.
Orrrr.. not, 5.2 doesn't support anonymous functions. Ok scrap that idea.
The idea was good while it lasted :)
Create an account or sign in to comment.
I have been experimenting with Rowan Lewis' Content field extension:
Content field extension
This would be perfect for setting up user controlled HTML5 section elements!
Works fine on default Apache (OSX) but I can't get it working on a MAMP dev machine. Enable/install returns a white screen and the error log says:
I have worked through all the obvious things to a front-end guy - can anyone help?