Drupal 7 had the Tracking Code module that did the following:
A module that allows admins to create tracking code snippets and control their visibility similar to the core Drupal block module. It can be used to inject arbitrary code into the <head>, and at the beginning and end of the <body> tag, the most common placement for tracking code.
This module allows you to name your various tracking code snippets and organize them by weight and region. Configuration of a single snippet provides visibility settings similar to the core Drupal block module: white/black list by Drupal path, content type, and user role.
Currently there are three possible regions to inject your tracking code snippets:
- Inside <HEAD> - Code is added using drupal_add_html_head()
- After <BODY> - Code is added to $page['page_top'] using hook_page_alter()
- Before </BODY> - Code is added to $page['content_bottom'] using hook_page_alter()
We're thinking of porting this module. But, I am wondering if there is a better way to accomplish the same thing that does not require porting another module?
Recent comments
Thank you for all your help. In the meantime I just edited the export db-file and removed the top line with the sandbox comment. --> Still the same issue. I exported also with the...
Problem with utf8mb4 Format when importing database
Another possibility: The RRSB module has a forward option. If you don't want all the social-media sharing links, you can uncheck them all, then enable RRSB on the node types of your choice.
Forward/email this page ?
One person said: I use bee in mamp - but not sure what i can offer. I did a basic setup and it just works...
Problem with utf8mb4 Format when importing database
It is possible to remove that line manually from the SQL file and it should then import to MySQL fine.
Problem with utf8mb4 Format when importing database
I think people have used bee in MAMP. I've posted in our chat channel to see if anyone can jump in here and help: #Backdrop > Bee @ 💬
Problem with utf8mb4 Format when importing database