dm4n

Hi @jeroenpeters1986,

Thanks for your prompt replies.

I think you’re right and the theme is doing something nasty. I created a new page with Name Directory shortcode and it’s working fine.

Will test further and report back if nay issues.

Thankyou ??

Hi,

the tweaks going well – using the pointers from your Plugin FAQ.

There’s a problem with the Index – the letter links aren’t leading to the entries.

Msg returned on click is “There are no names in this directory at the moment”

https://bit.ly/2OgxAAd

I wonder if it’s an issue with the theme.

Cheers

• This reply was modified 6 years, 7 months ago by dm4n.

Hi,

That worked, thanks! I put the code in the Appearance > Custom CSS section of WP.

I’ve got a few more tweaks to attempt – font size and colour of the directory entries and will write a glowing review after that.

Cheers ??

Hi avee,

Sorry – no website yet, I’m running WordPress on my localhost.

Screenshot of Front Page here.

Thanks

Problem was at the Google Analytics end in my case – had to generate a new UA code and Property on Google’s system and then the MonsterInsights plugin picked everything up.

Thanks.

Yep, same problem here too, on fresh install of the plugin ??

Perfect!

Many thankyous ??

Thanks very much!

That did the trick.

Except the url in the Footer is in format https://’sitename.com’

How to change it to just ? ‘www.sitename.com’ ?

The problem is my Footer says ?’site-title’

and I want it to say ?’site url’

Or even redirect to a Thankyou Page?

Answer: deactiviating Kirki Toolkit Plugin fixed the problem.

All works now. thanks

Thanks for your help. I was just reading the specificity page when your reply came through.

I think the problem is a specificity issue- the selectors displayed in Inspect element are:

a {
color: #F30;
text-decoration: none;
}

And the parent’s style.css is
a {
color: #F30;
*/ text-decoration:none; */
}

Is the comment syntax incorrect? And doesn’t the child’s style.css override the parent’s?

I think that’s right – the error occurred if WP Super Cache needed to write to the .htaccess file and I wiped the caches before allowing the plugin to write.

Also, I’m not using Bulletproof plugin at the moment.

Since figuring that out – the error hasn’t reoccurred.

Thanks.

That’s useful info about Permission settings.

There is definitely redundancy in using both- maybe this can be changed via respective configuration settings.

Thanks for the generous help ??

Cheers.