On a fresh install of Drupal 8, Beta 4, when I tried to create a Basic Page I got the following PHP fatal error.
Maximum function nesting level of '100' reached, aborting
In my case, it was apparently hitting a limit that is set by xDebug. To fix this on my system, which is running Linux Mint 17 with Apache 2.4.7,
1) Added the following line to /etc/php5/mods-available/xdebug.ini
xdebug.max_nesting_level=200
2) Restarted Apache.
# service apache2 restart
Sources:
Error on install Maximum function nesting level of '100' reached, aborting!
https://www.drupal.org/node/1663314
Maximum function nesting level reached error in Drupal
http://stackoverflow.com/questions/5103182/maximum-function-nesting-level-reached-error-in-drupal
Wednesday, January 28, 2015
Thursday, January 22, 2015
Setting up a local dev instance
Here are a few tips about setting up my local dev environment for working on PlayPoi. Linux Mint 17, Apache 2.4.7.
This is not a complete set of steps but just a few key points and things to remember to do.
Installing Drupal 8 beta 4.
(a) I already had a copy of the D8 beta 4 directory available locally, so I made a copy of it under /var/www/html and renamed it to playpoi.
(b) Changed the owner of the entire site instance to the user that Apache runs under.
# cd /var/www/html
# chown -R www-data:www-data playpoi
(c) Edited /etc/apache2/apache2.conf to insert the following directive so that the .htaccess file of the site is used.
<Directory /var/www/html/playpoi>
AllowOverride All
</Directory>
(d) I've also started using virtual hosts. So I created one for this site following the directions in this blog post:
http://optimizely-to-drupal-8.blogspot.com/2015/01/setting-up-virtual-hosts-for-multiple.html
Setting up for our custom theming and modules.
Dee and I are using a GitHub repo as a collaborative space for managing our code and its issues.
At the same time, Drupal 8 is still in beta and continuing to evolve. The D8 convention is to put custom themes and contrib/custom modules into the top-level site directories themes and modules, respectively.
In order to provide loose coupling between our custom work for PlayPoi on the one hand, and the updates to Drupal 8 core on the other, on our local systems we are replacing those two top-level directories with symbolic links that point into where the local GitHub repo is placed.
In other words, the code we are working on is actually located outside of the site tree.
On my local system,
$ cd /home/earl
$ git clone git@github.com:DeeZone/playpoi.git
which cloned the repo into /home/earl/playpoi.
# cd /var/www/html/playpoi
# rm -r themes
# ln -s /home/earl/playpoi/themes themes
# rm -r modules
# ln -s /home/earl/playpoi/modules modules
In the event that the entire D8 tree might get replaced, it would only be necessary to re-create the symbolic links.
Another benefit is that by having the GitHub repo separately placed in my own file space with me as the owner, I can work on it while logged in as myself without needing to be part of any special group or to have elevated privileges.
Also, the repo gets included in the back-up of my home directory, which is already set up.
This is not a complete set of steps but just a few key points and things to remember to do.
Installing Drupal 8 beta 4.
(a) I already had a copy of the D8 beta 4 directory available locally, so I made a copy of it under /var/www/html and renamed it to playpoi.
(b) Changed the owner of the entire site instance to the user that Apache runs under.
# cd /var/www/html
# chown -R www-data:www-data playpoi
(c) Edited /etc/apache2/apache2.conf to insert the following directive so that the .htaccess file of the site is used.
<Directory /var/www/html/playpoi>
AllowOverride All
</Directory>
(d) I've also started using virtual hosts. So I created one for this site following the directions in this blog post:
http://optimizely-to-drupal-8.blogspot.com/2015/01/setting-up-virtual-hosts-for-multiple.html
Setting up for our custom theming and modules.
Dee and I are using a GitHub repo as a collaborative space for managing our code and its issues.
At the same time, Drupal 8 is still in beta and continuing to evolve. The D8 convention is to put custom themes and contrib/custom modules into the top-level site directories themes and modules, respectively.
In order to provide loose coupling between our custom work for PlayPoi on the one hand, and the updates to Drupal 8 core on the other, on our local systems we are replacing those two top-level directories with symbolic links that point into where the local GitHub repo is placed.
In other words, the code we are working on is actually located outside of the site tree.
On my local system,
$ cd /home/earl
$ git clone git@github.com:DeeZone/playpoi.git
which cloned the repo into /home/earl/playpoi.
# cd /var/www/html/playpoi
# rm -r themes
# ln -s /home/earl/playpoi/themes themes
# rm -r modules
# ln -s /home/earl/playpoi/modules modules
In the event that the entire D8 tree might get replaced, it would only be necessary to re-create the symbolic links.
Another benefit is that by having the GitHub repo separately placed in my own file space with me as the owner, I can work on it while logged in as myself without needing to be part of any special group or to have elevated privileges.
Also, the repo gets included in the back-up of my home directory, which is already set up.
Monday, November 10, 2014
How we are doing this
Doing this migration is a part-time gig for both Dee and myself. Even though we are both in the New York City area, it's hard to work together at the same time, even remotely.
So we thought we'd try a different kind of collaborative approach, especially because the purpose of this project is not only the end result, but also very much as an exercise for learning Drupal 8.
What we're going to do is set up tasks that both of us will tackle independently. Then from time to time we will get together to compare notes and decide on which result to use in order to continue. I expect that often it will be some kind of amalgamation.
This blog will document the technical stuff that each of us learns. It may also log how this kind of collaboration turns out for us, which is another reason why I'm interested in doing it.
So we thought we'd try a different kind of collaborative approach, especially because the purpose of this project is not only the end result, but also very much as an exercise for learning Drupal 8.
What we're going to do is set up tasks that both of us will tackle independently. Then from time to time we will get together to compare notes and decide on which result to use in order to continue. I expect that often it will be some kind of amalgamation.
This blog will document the technical stuff that each of us learns. It may also log how this kind of collaboration turns out for us, which is another reason why I'm interested in doing it.
Saturday, November 8, 2014
In the beginning... Earl (Drupal user: tz_earl) and I (Drupal user: DeeZone) started the process of moving the PlayPoi.com site from Drupal 6 to Drupal 8. This blog is a running account of the trial and tribulations of our journey.
Our first task is to get the latest release of Drupal 8 running in our local development environments. Expect posts from both of us detailing any challenges we encountered in the process.
Our first task is to get the latest release of Drupal 8 running in our local development environments. Expect posts from both of us detailing any challenges we encountered in the process.
Subscribe to:
Comments (Atom)