New version: Remove from main menu into Tools

Hi,

Also, the options menu is not very intuitive – it’s hard to tell if an option is selected or not, they are just buttons and for me nothing changes pressing either On or Off. So I can’t really tell what options are active.

Please make a screenshot of how the menu is displayed. All switches must be clear. Perhaps you have problems with the interface?

The main menu is a pain for many users. Now the plugin uses arbitrary post types and they are automatically added to the main menu. In the future I will try to solve this problem, I will also need to interview a few more users.

Best regards, Alex

• This reply was modified 6 years, 5 months ago by webcraftic.

Hello, thanks for the reply.

The menu looks like this, and also the settings page. As you can see, there is no way to tell what option is selected On or Off:
https://i.imgur.com/BWiwcwW.png

This is in Firefox.

I would like the PHP Snippets item moved into the Tools menu to avoid cluttering up the main menu.

And there needs to be a way to tell what option is On or Off.

Stian

Hi,
The settings page should look like this, it looks like you have some gaps with the interface.

On the setting page, simply open the developer panel in your browser. Take a screenshot of the panel on the “console” tab and attach a screenshot so I can understand what the problem is.

How to open the console of the developer? Look at this article:
https://kb.mailster.co/how-can-i-open-the-browsers-console/

As for the menu, I will try to solve this problem.

Best regards, Alex

Hello Alex,
thanks again for looking at this.

You posting that screenshot of how it should look was a good idea. It became apparent that something was very wrong, since I had the same look also when testing in Vivaldi.

I looked in the dev.console and found several resources giving a 403 forbidden.
For instance this file:

wp-content/plugins/insert-php/libs/factory/bootstrap/assets/cache/ef2b9fc6fe0b7396878b88eecd9810ff.min.js?ver=2.0.4

So I had a look at the permissions of the dir on server side, and apparently some permissions were set very wrong when the new version of the plugin was installed. The permission looked like this:

drwx-w--w- 2 user www 4096 Jun 15 15:59 cache

So, the www server had no read permission on the files in the cache dir. On my system only owner and www should have read/execute, no other. Having the cache dir writable to www and others, like it was, could be a security problem.

Since I usually don’t need to set manual permissions inside my wordpress installation, I think some setting in the plugin might be wrong, and creates the cache with wrong permissions.My host runs SuPHP and so files installed by WP are owned by me and only readable by www.

So maybe the problem lies in some obscure plugin setting for code that generates the cache with the minified bootstrap css?

Anyway for me at least, this problem is gone, at least until a new version of the plugin comes and messes it up again? ??

• This reply was modified 6 years, 5 months ago by Stian Lund.