Hi @paullydca
Does the issue happen without other plugins active?
Do you know how to check the browser’s Javascript console?
The WPRUS admin page relies on Javascript, and if there is an error coming from other plugins, it could prevent it from working.
Please feel free to investigate further so that I can help you ; I presently cannot replicate your issue.
I have tried with deactivating all other plugins and it still occurs. I tried theme as well, and it still happens.
I am familar with console yes
It could be something server related maybe. I’ve tried the connection on other sites I have and it works flawlessly. But sites on that server not so good.
- Got the credentials, went in scottsdale website, added unbranded, saved => issue: after page reload, the unbranded sites settings wouldn’t appear, as described.
-
I went to plugins, deactivated them all except WPRUS, went back to WPRUS, added unbranded, saved => issue: 2 unbranded sites appeared.
-
I went in and activated the previously disabled plugins.
-
I deleted the duplicated unbranded site settings, then activated the user actions and tested them, saved => success
-
I added a test website of mine to the settings, saved => success
-
I deleted the test site from the settings, saved => success
-
I logged out of both sites, logged in to unbranded, got logged in automatically on scottsdale => success, sync works.
It seems to me something was happening with the interface due to another plugin. I haven’t investigated more, however it seems WPRUS settings themselves do not have any issue.
It should get you going though, but if in any event you are able to narrow down which plugin is responsible for the conflict, feel free to let me know and I’d be glad to provide a fix (unless the issue is on the other plugin’s side, in which case I’d be happy to advise you on how to provide feedback for them to fix it).
I’ll close this issue for now – don’t hesitate to open another one with as many relevant details as possible should other problems arise ;).
@frogerme While I know you have the best of intentions, it’s forum policy that you not ask users for admin or server access. Users on the forums aren’t your customers, they’re your open source collaborators, and requesting that kind of access can put you and them at high risk.
If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.
Thankfully are other ways to get information you need:
You get the idea.
We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It’s actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it’s difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.
When you help users here and in public, you also help the next person with the same problem. They’ll be able to read the debugging and solution and educate themselves. That’s how we get the next generation of developers.
You’ve been placed on “modwatch” until we’re convinced such postings have stopped. Your account has *not* been banned, we just want to check things for a while before they’re public. If you wish to take issue with this, contact moderators via the #forums channel on slack (https://make.ww.wp.xz.cn/slack) However, continuing to ask for admin access to user sites may result in escalating this to the plugins team.
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
@frogerme I’ve archived your reply. To put it mildly, it indicates you’re not getting it.
This isn’t hard and if you need it explained to you in ways that you’ll understand feel free to contact the plugins team via email. You have their email.
If the forum restrictions are too burdensome for you then consider asking the plugins team to close your plugins on this site. That way you won’t have support topics that may tempt to to ignore the forum guidelines again.
No one is forced to host their plugins here on this site. But if you do, you need to comply with those guidelines or risk having your plugins closed.
I really appreciated @frogerme help. Certainty would not have shared details with him if i was not comfortable. It’s not often you find a plugin author of such a useful free plugin so willing to offer extensive help to ensure their product works for them.
Whether you’re comfortable or not, it sets a level of expectation that asking for or offering credentials is OK here. It’s not. Please don’t offer to send or post logon credentials on these forums: https://ww.wp.xz.cn/support/guidelines#the-bad-stuff
You can contact the author on their own site and, once there, the discussion is between the two of you. However, it is not OK to enter or send site credentials on these forums. We don’t want to encourage others (who are less reputable) to do similar things. It’s a fine line, but one that we need to enforce. Thanks for your cooperation.
understood thanks for clarification.
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
Certainty would not have shared details with him if i was not comfortable.
Please do not. It’s not a matter of comfort; the plugin author risks having their plugin removed from this site when that happens. It really is that serious. It’s not just to protect users, it also is to protect volunteer developers like this plugin author.
If something goes wrong after you’ve provided those credentials then they author is possibly liable and that’s not a scenario that should be here at all.
Everyone here is a volunteer like yourself. That includes the plugin author.
