Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Hey bud, I had this same issue and just fixed it. Also on Linode, running Ubuntu.

    It looks like its a DNS issue. I guess theLinode’s in-house DNS servers are having an issue? Its out of my depth, to be honest. You can get running again by using a public DNS instead (e.g., Google’s).

    You can confirm you have a DNS issue by running this test script:

    If indeed this is a DNS issue, you should get a similar error as you’re seeing from WordPress (curl error 6, can’t resolve hostname).

    To fix, login via SSH and edit /etc/resolv.conf:

    nano /etc/resolv.conf

    Comment out the existing nameserver lines (add a # to the front), and add in Google’s DNS servers instead.

    Here’s how my /etc/resolv.conf file looks now:


    There could be other lines in the file (there are in mine) – just leave them alone.

    Restart apache (or nginx) after making the change:

    service apache2 restart

    That should do it!

    I hope this helps you. We’ve been trying to figure this out all day.


    Plugin Author ghuger


    Hi Wendy!

    Although we are not usually able to monitor these forums for support questions, this is a great question and I suspect others will want to know. I’ve emailed you as well with the same information.

    Yes: the template files must have a specific name, and they need to be in the root folder of your theme.

    For example, if you wanted to customize the single-staff-member-content.php template, you would:

    1) Navigate to /wp-content/plugins/staff-directory-pro/templates/, and save a copy of single-staff-member-content.php

    2) Modify this copy of single-staff-member-content.php however you like

    3) Upload your modified copy of single-staff-member-content.php to the *root folder* of your theme. For example, with the twentyfifteen theme, your customized template file would live at /wp-content/themes/twentyfifteen/single-staff-member-content.php

    Its important that you place the modified template inside of the root folder of your theme – we will not be able to detect it from any other location. This could be confusing, because in our plugin the templates all live in the “templates” folder, whereas in your theme they need to be in the theme’s root folder.

    I hope that helps!

    All the best,

    Here is the code in question, Kenny:

    Please remove it.

Viewing 3 replies - 1 through 3 (of 3 total)