comments in pihole-ftl.conf
i have a lot of comments in my pihole-ftl.conf, mainly to identify undocumented settings or point to topics where the setting is introduced / explained

one of my comments triggered a php error on the settings page

## decrepated !!!

[[image]](https://b2discourse.pi-hole.net/original/3x/6/b/6b83604fa488b1e5e846cf42eda3c3f5a812cd3a.png "image")

pihole-ftl uses '#' as comment sign

php uses ';' as co…
actually, ftl does not care about #. instead, everything ftl cannot parse as valid config setting is ignored. so using ; everywhere is fine as well. prepending with ä would equally work, too, etc.

additional hint: pi-hole v6.0 will change the config file format to [toml](https://toml.io). the existing pihole-ftl.conf …
Errors and warnings usually appear in `....\logs\php_error.log` or `....\logs\apache_error.log` depending on your php.ini settings.


Also useful errors are often directed to the browser, but as they are not valid html they are not displayed.


So `"tail -f`" your log files and when you get a blank screen use IEs "view" -> "source" menu options to view the raw output. [image]

[how to enable error reporting in php](https://www.000webhost.com/forum/t/how-to-enable-error-reporting-in-php/43038) [tutorials](/forum/c/tutorials)

this tutorial is for those who get internal server error. so your website is not working and you are struggling to find out why. you see error 500 and do not know what to do next. if you try googling error 500 this wil… Hi BenzZz,



as far as I understand this is a HTML-problem. Try setting the initial value with



```
value=""
```

to an empty string.



Otherwise I can suggest:  

- Open your source code in your browser and see if you have any artifacts from your php parser  

- make sure you have your JavaScript deactivated



I hope that helps, Simon Hello,

 

 

We would like to inform you that decoding MCE errors is out of the scope of support for us. As a general recommendation based on the wording for the log, please check the memory modules installed and confirm if one of them has failed.
 
 
 
 
 
 
 
 
 

[View solution in original post](/t5/Server-Products/How-to-decode-MCE-errors/m-p/527769#M13599) > if( !@include( $path ) ) {
> 
> 


That part of the syntax is totally wrong. I don't think that an include is not meant to be in an if statement. Also replace the include with the require function which does the same thing but with error reporting. Also I would advice removing those @ symbols. So the above quote should be the following:



```
if(file_exists($path)) {
require( $path );
} else {
``` Hello, [@Trulines87](/c/user/viewprofilepage/user-id/733134).


Welcome to Shopify Community. My name is Olivia and I work here.


Thanks for posting your question, I can definitely help you out with this today. There are a couple of different ways we can tackle this, so let's dive right in to your options.


**A. Use your design time.**


Each store on a paid plan, using a Shopify developed theme, is allotted a full 60 minutes of design time for minor changes. While it's best to check with our [Support Team](https://bit.ly/2XDcBxK) on what changes we can, and can't accommodate, your request is definitely one we could look after. If you have a specific idea of what you would like your footer to look like let me know and I can connect you with our Theme team. Just be as detailed as possible with your request, maybe even including examples, to help us make the right changes. Make sure to check out our [design policy](https://bit.ly/31wVsHb) to read more about support for Shopify themes.


***OR***


**B. Add text to your footer code.**


If you're comfortable with making code changes you can save your design time for something else. It will be helpful to have basic knowledge of HTML and CSS to help you customize the style and layout of added text, but I can point you towards making these changes on your own. Head to **Shopify Admin > Online Store > Themes > Narrative > Actions > Edit Code** and scroll down to */sections* to find the file **footer.liquid**.


Narrow down this piece of code on line 32:


 



```
{% when 'menu' %}

```

 


Now, insert your text after that line. Make sure to add <p> before your text, and </p> at the end of your text to close the code. Here's an example:


 



```
            {% when 'menu' %}
            <p> Add your contact info </p>
              {%- assign link_list = block.settings.link_list -%}
```

 


This is how it would appear on your website:


![08-26-ndww6-2kmgo](/c/image/serverpage/image-id/57763i1C21A51AE550DEAA/image-size/large?v=1.0&px=999 "08-26-ndww6-2kmgo")


That's it! You can take it a step further and make it even easier for your customers to contact you by adding a direct email link. Simple code like this would work: 


 



```
<a href="mailto:yourmail@domain.com">Insert your business email address</a>
```

 


Same thing for a "click-able" phone number to help customers easily phone you:


 



```
<a href="tel:18001112233">1-800-111-2233</a>
```

 


And we're done! Don't forget to replace the email address and phone number in those codes with your own information.


That should work, but let me know if any other questions come up that I can help with.


Warm regards,



**Olivia | Social Care @ Shopify**  
 - Was my reply helpful? Click **Like** to let me know!   
 - Was your question answered? Mark it as an **Accepted Solution** - To learn more visit the [Shopify Help Center](https://help.shopify.com/) or the [Shopify Blog](https://www.shopify.ca/blog) What have you tried? Have you searched the php manual for sending email? > You might have missed a bracket somewhere... Only such a mistake causes so many insignificant errors.
> 
> 


And to find it, [format your code](http://www.gidnetwork.com/b-38.html) properly. It's your first debugging tool. hi sheeeng.  thank you for reporting this to us.  we looked into that file and verified that there is a false detection indeed.  we have fixed this already and the fix should go out soon on the next database releases.

 

thank you again for you report! 

 

 

f-secure labs > 
> When I'm on a discussion, it shows up!
> 
> 
> 


The discussion still based on the old code.



> 
> Or do any of you guys still have it available?
> 
> 
> 


It is still possible to use:


![](http://pix.academ.info/img/2017/11/18/3d272cacfc99d5afdf92f0374cf5c406.png)


You just need to turn off the new code:


* Go to any page of the forum (this page is good).
* Write `duo.old_web_url_whitelist=["^.+"];` in the browser console and press "Enter".
* Go to home, then to the lingot store, and take the test.
* Enjoy!