joelworsham

This is a conflict with older versions of PHP. This is a feature that was implemented in 5.4 https://php.net/manual/en/migration54.new-features.php.

I will modify this in the near future to be compatible down to 5.3 though, and release a patch for it.

Sorry for any inconvenience.

That’s because the editor doesn’t have the needed capabilities to view those pages. They would need the activate_plugins capability or the switch_themes and edit_theme_options capabilities.

Client Dash does not currently offer support for modifying role capabilities, but there are ways to accomplish this through custom programming or other plugins.

I’m actually confused as to how you added those pages to the editor’s menu. Client Dash is currently configured to only allow you to add pages for a user only if the user can access them. So this could be a bug?

Can you tell me what version of Client Dash you’re running, and also what version of WordPress?

And how did you add the pages to the editor? As in, did you use a custom link? Or were they from a different accordion box on the left?

This problem has been addressed and will be released in a patch in the near future.

Sorry for any inconvenience.

Translations is something that, unfortunately, Client Dash does not yet implement. We plan on integrating translation capability in the near future, and we’ll look into getting some translators to help with German.

For now, I’m sorry to say there is no such capability.

Alright, well it’s definitely livable, just was curios. Thanks for the replies.

Thanks for the info, though this plugin I found (Rename wp-login.php) only seems to rename the login url, and not the entire wp-admin url.

Is it possible to set-up the htaccess to apply some url rules to the entire backend to shorten the url to the normal “/wp-admin”? Or this is simply not possible?

I see now my issue… I thought the min weight was the minimum weight for the fee to apply, but I see now that the options won’t show unless the min weight is met.

Ah yes. I see what the issue is. It’s a strange, edge-case programmatical issue.

I will safeguard any instances of the issue you’re encountering in the next patch. There’s a few other small issues that need to be cleaned up as well.

The patch will be issued in the near future (hopefully today).

Sorry for the inconvenience! We’ll get this fixed soon.

Hmmm interesting. I will definitely look into this.

Could you explain a little further what you mean by “it makes a mess”?

Also, the not showing the Links item is a bug in Client Dash and will be fixed on the next patch / release.

Hmmm, that is a very interesting idea. It is certainly possible, though not currently integrated.

I will be sure to put that in the next release though ??

I apologize for this and for the delayed response.

I will look into this very soon and get back to you.

Great! Glad to help! I’ll be around if anything should come up.

I can absolutely understand your concern.

Client Dash keeps all of it’s settings within the default options table. So after you delete the plugin, these settings will indeed remain.

BUT, these settings only pertain to Client Dash itself, not to anything else.

So, in other words, if you activate Client Dash, tweak everything and move stuff around, and then later decide it’s not for you, simply deactivate and / or delete it. Your site will be back EXACTLY to as it was before, as if Client Dash was never even there. Your options table will just have a few extra entries sitting around.

However, if you REALLY want to clean those few minor database entries up, you can hop over to the “Tools” tab in Settings and use the “Reset All Settings” button. This will remove all Client Dash settings entirely. Please note, this is not necessary, but I can understand it making you feel a little more at ease ??

None specifically on the site, but it is running on a WP Engine install, which I believe uses some page and object caching.

We have found the error. The error is caused because of some syntax used in the plugin that is only supported in php 5.4 and up. We will be changing this today and releasing a patch with some other minor fixes as well.

Expect it by the end of the day.

Thank you for your patience as we resolve this situation!