Lobster01

Since I don’t really have an issue anymore, I set this one as resolved.

Thanks for the update.
What I mean with the R box is the input box R of the RGB color code.

But I will wait for the update and till than I’m gonna do it the old fashion way, filling in color codes myself ??

Is your problem solved yet? I had the same problem and after some fiddling around I somehow got all my accounts.
What I did was:
1. I searched at GA for differences between the accounts who were visible and invisible. In my case the property of the new account had not set a default view in property configuration. Don’t know if that’s it though.

2. I cleared the authorization and the cache inside the plugin in WP. I re-authorized with the access key and now everything is visible.

Maybe this helps. Good luck.

No problem. I’m glad to be able to help. Is it possible that, if you find some other reason for the disappearing desktop, you post it here? Cause I like the plugin and if the float property is needed, I like to put it back ??

Thanks

Maybe there was something wrong with the configuration. I had the same problem as dichternebel.
Using a multisite setup, activated this plugin ms-wide for smilies in bbpress and there was no menu-item in all the sites I had. So tried to activate the plugin on one site, the main site, and it showed the menu-item.
I activated it on a second site in the MS-setup but there’s no menu-item for this plugin. Hmm, weird.

I also got the notice that the option to convert emoticons like ?? and :-p in the settings->writing section should be turned off. Did that on both sites. On the main site in the wp-monalisa settings I enabled the option for bbpress and now there are smilies on the second site as well.

I had no need to alter the function.php and that’s nice. Maybe for future development a better ms-compatible setup would be great.

Ok, so I deleted the CSS property float in your CSS file and re-uploaded it. The issue is now gone.

It appears that the mentioned line is also further up in the css file. On line 185 according to Dreamweaver. While I was inspecting the element through Firefox it told me that the property was on line 93, sorry for that.

This issue is indeed caused by your plugin, sorry for that. It’s not so much a conflict, it’s just a CSS thing.

I have the same problem. When I’m activating your plugin, the dashboard widgets in the admin panel disappear. There not gone!! Not at all, they just moved out of the screen ??

You have a CSS file in your plugin called wafi-style.css. According to the file I have (and I did not change anything yet) this is on line 93

div.updated {
    float: left;
    width: 98%;
}

If you have a message on your dashboard thats saying that you need to do something for a plugin, like I have, for example:

There are no language files installed. You can manually install some language files or you could use a plugin to download these files automatically.

Those messages are in a DIV with the class UPDATED. In your CSS file, as you can see, you added some property’s to the updated class. which is causing the dashboard div to hide the widgets.

As far as I could find, those property’s are not needed.

Maybe you can change that in your CSS file so that people are able to use the plugin, which is great, and also use there dashboard (which is important ghehe).

Hope this helps

Seems similar indeed. Sorry, if I checked the debug.log I would have found this.

Anyway, I followed it and it’s fixed. Since I deactivated and uninstalled the plugin, I had to reinstall it again, configured it and now the problem is fixed.

Don’t know if I configured it completely the last time. The reinstall before just now I didn’t.

Thanks for the help ?? It’s a great plugin and like I said, I’m going to use it a lot in the future.

Hi Dennis,

Thank you for the quick reply. I did put the debug on (did not think about that before haha) and here’s what I got:

[24-Nov-2014 13:02:34 UTC] PHP Fatal error: Call to a member function get_language() on a non-object in /home/****/public_html/****/wp-content/plugins/multisite-language-switcher/includes/MslsMain.php on line 94

**** = hidden directory, did this myself ??

This was the only line in the debug.log

Cheers, Robert

I see that the bold option doesn’t work in the code section ghehe. Sorry for that. Should have known that.

Anyway, I found this in the console while checking for js errors:
POST https://devrught.com/devrught/wp-admin/admin-ajax.php
TypeError: l is undefined

The error occurred when I left the R box empty, so think that’s normal.

This is what i get if I click on the post message:

Aanvraag-URL: https://devrught.com/devrught/wp-admin/admin-ajax.php
Aanvraagmethode: POST
Statuscode: HTTP/1.1 200 OK
Aanvraagheaders 12:15:56.000
X-Requested-With: XMLHttpRequest
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0
Referer: https://devrught.com/devrught/wp-admin/post-new.php?post_type=page
Pragma: no-cache
Host: devrught.com
DNT: 1
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
Content-Length: 126
Connection: keep-alive
Cache-Control: no-cache
Accept-Language: nl,en-US;q=0.7,en;q=0.3
Accept-Encoding: gzip, deflate
Accept: application/json, text/javascript, */*; q=0.01
Verzonden cookie
wpfront-notification-bar-landingpage: 1
wp-settings-time-14: 1415810762
wp-settings-time-1: 1415820780
wp-settings-1: wplink=1&libraryContent=browse&imgsize=medium&mfold=o&align=right&urlbutton=none&editor=tinymce&ed_size=598&hidetb=1&advImgDetails=hide
wordpress_logged_in_ea422dda07ba07a2dcd2696de330afc8: beheerderlobster|1417020845|BzBjLC4nHHLFmG8F3HOHvRB8GHMN96GVOsT4NLkQg0D|7de208f38e750e5873f1091835ef3509c84231bc3feabde0002908196479f20b
wordpress_ea422dda07ba07a2dcd2696de330afc8: beheerderlobster|1417020845|BzBjLC4nHHLFmG8F3HOHvRB8GHMN96GVOsT4NLkQg0D|d7b36cbd77c7e355d0745d93cdd96b69cfb724742ae28e8f24e20a4f3d7666f8
wfvt_2973349588: 5469d8d9b7884
viewed_cookie_policy: yes
TPBmenuScrollTop: 0
PHPSESSID: 6578a5d6787afb533f5e636a3f7f1743
bp-activity-oldestpage: 1
_ga: GA1.2.2031134947.1412672205
Antwoordheaders Δ1335ms
X-Robots-Tag: noindex
X-Powered-By: PHP/5.4.32
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Server: Apache/2.2.29 (Unix) mod_ssl/2.2.29 OpenSSL/1.0.1e-fips mod_bwlimited/1.4
Pragma: no-cache
Keep-Alive: timeout=5, max=100
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Date: Mon, 17 Nov 2014 11:15:55 GMT
Content-Type: application/json; charset=UTF-8
Connection: Keep-Alive
Cache-Control: no-cache, must-revalidate, max-age=0

Thanks for the reply.

I don’t use that plugin, only the built in color picker. I will check for the JS errors. I’m not familiar with JS tho haha.

2 I was already checking the plugins, not completely done yet. Thought the same thing about the overwritten css property. But I couldn’t find a problem, except that all the position property’s are overwritten or disabled. Not clear if that’s normal or that it is another plugin.

This is what I found on the CSS position property’s:
(bold text had a line through it)
Dropdown box (paragraph) id: MCEU_72 ->
<div id="mceu_72" class="mce-container mce-panel mce-floatpanel mce-menu mce-menu-align" role="application" tabindex="-1" hidefocus="1" style="border-with: 1px; z-index: 100100; left: 410px; top: 1252px; width: 225px;">

.mce-menu {
    position: absolute;
    <strong>left: 0px;
    top: 0px;</strong>
    padding: 5px 0px;
    margin: 2px 0px 0px;
    min-width: 160px;
    <strong>background: none repeat scroll 0% 0% #FFF;
    border: 1px solid rgba(0, 0, 0, 0.2);
    z-index: 1002;
    border-radius: 6px;
    box-shadow: 0px 5px 10px rgba(0, 0, 0, 0.2);</strong>
    max-height: 400px;
    overflow-y: auto;
    overflow-x: hidden;
}
.mce-floatpanel {
    <strong>position: absolute;
    box-shadow: 0px 5px 10px rgba(0, 0, 0, 0.2);</strong>
}
.mce-container, .mce-container *, .mce-widget, .mce-widget *, .mce-reset {
    <strong>margin: 0px;
    padding: 0px;
    border: 0px none;</strong>
    outline: 0px none;
    vertical-align: top;
    <strong>background: none repeat scroll 0% 0% transparent;</strong>
    text-decoration: none;
    <strong>color: #333;
    font-family: "Helvetica Neue",Helvetica,Arial,sans-serif;</strong>
    font-size: 14px;
    text-shadow: none;
    float: none;
    <strong>position: static;
    width: auto;</strong>
    height: auto;
    white-space: nowrap;
    cursor: inherit;
    line-height: normal;
    font-weight: normal;
    text-align: left;
    box-sizing: content-box;
    direction: ltr;
    max-width: none;
}

Well that’s just it. Clearly you do not read all support questions on this forum. I did send a request before with an explanation of the problem. No answer.

Now, I looked at the first two pages of this support forum and found these:
Topic 1 – not addressed by you but similar problem.
Topic 2 – while this is not a request about the problem, it tells us that the problem does exist.
Topc 3 – Not addressed by you but an unable to login issue as well. This person has given little information but could be asked to give some more information about the issue. I think you would here something like: You must log in to access the admin area, or, error 404, or, it locked me out!
Topic 4 – not addressed by you, the topic I send a request through for the same problem.
Topic 5 – a request which is answered by you with a question if the problem is caused by another plugin. That’s the first thing you ask for. To bad there are no responses in this one.
Topic 6 – not yet addressed by you but a same topic as this one. Same problem! With a third person who joined that topic with clearly stating that he is locked out after 2 days using this plugin! You can not say you did not hear about this issue.

And about other plugins, I’m not a beginner with wordpress of webdesign. The first thing I checked was if another plugin could be the problem. I checked even the themes. Since this problem was still there I decided to have a clean install, completely vanilla. The only plugin I installed was your plugin. The next day I was locked out again! On the clean install.
This issue is within this plugin and needs to be checked and resolved. And since I posted a request before, checked the forum regular for solutions or answers, I found that there was no support for issues about been locked out or getting the message that you need to log in to access the admin area.
I started to search for other way’s to get the same results and found a perfect security plugin which, until now, did not lock me out of my own website.

And even if you’re develop this plugin in your free time. You should find more time to answer the support questions. Even if it is to let people know that you’re working on it. You have the ability to let people know that you have less time than normal or that support will be picked up at another time. People expect good support from the developer or, if there, the team. Some people who are working every day on their website or the website of there clients need to have quick answers. If not in an existing support issue with solution or in an posted support issue which is waiting for a response. I waited like a month in that other support topic and no answer. In this topic, I had to wait for 6 days and since I posted a somewhat negative reaction, you have the time to respond.

Well to bad, I really hope you will continue this plugin. Cause in some cases it is easier to add an extra security plugin as simple, but crucial, as this one. But work on a better support management.
Like I said, I found another great plugin which offers the same and much much more! I will stick to that one from now on.

Since this issue is not picked up by the dev team. I decided to set aside this constantly failing plugin. Now I use iThemes Security (formerly known as Better WP Security).
It offers the same security plus a whole lot of extra security options I needed.

For me this rename plugin and the support in this issue is a big let-down. Even if the dev team is busy solving this issue, they should let people know they are working on it. Not responding at all gives a bad reputation.

Good luck with your plugin, I really hope you will solve this issue in the future. But I will never use this plugin again!

You’re welcome pmcphail.

I have somewhat the same problem.
I don’t use the maintenance mode but I use this rename plugin.
Every time I visit the website and try to login, the plugin does not allow me to login. It redirects me to a 404 page and when I click on the home button to go to my front page, I need to log in again. The plugin blocks all login attempts.

The only thing I can do is the following: (maybe this helps for you to)

Login through FTP
Go to wp-content/plugins
Find the rename-wp-login folder
Rename the folder (i.e. rename-wp-loginnnn)
login to your website

After this the plugin does not work anymore, at least until you give the folder the right name again.