Carike

@skus

Thanks a bunch. That was very kind of you. I just did not have the time / energy to chase that one down.
The simpler solution is to comment out line 47 in the DraftOrders.php file.

One could possibly write a small plugin, or place the code in your theme’s functions.php file to remove_action(). That would avoid the need to edit the plugin files directly. I don’t need to do this permanently though, so haven’t written and/or tested that.

To plugin support:

This is very poor UI/UX. Changing the status to draft is available from /wp-admin/, but there is zero warning that some of your orders are just going to be permanently deleted (not even moved to trash).

Thankfully I had a suitable backup, but as soon as I restored it, it would delete the drafts again, before I even had a chance to change their status back to on hold.

I would respectfully suggest not asking for reviews based on this thread, as neither of you provided a suitable solution in this case.

If anyone has a similar question, I exported the whole DB from the hosting control panel in various formats. Found the Snitch post values by looking through the CSV format.

I think I have figured out what happened.

The e-mails are set up (correctly) under the global settings, but for some reason e-mails were turned off under the individual group settings. This does not seem like the sane default to me, personally. There was also no way to know that I had to change the settings on an entirely different page to inform a group manager that action was required when a new member wants to sign up.

I highly recommend making a mention of the individual group setting (with a link) on the global settings page to make it easier for users of the plugin. This seems to be a UI / documentation issue. Improving either or both can go a long way towards avoiding frustration and misunderstandings. The plugin has a really high learning curve / barrier to entry, even for people who are familiar with WordPress. It must be really tough for newbies.

Have a great day.

Marking this as resolved for now. Will create a new thread as other issues pop up.

Hallos. Thanks for the response.

I will open a support thread to provide more details for you, since the group is closed and I only used the “defining recipients manually” feature as a workaround for the group manager notifications not working. I would really like to see this plugin improve.

Updated and tested. The ProfileGrid login form works. Just wanted to say thanks.

Thanks for the response.

I applied the patch, but it did not work initially. (It caused a critical error on front-end pages.)

It seems that it messes up the character formatting in the plugin editor if the code is copied directly from the .org website.
So, if you are looking for a solution to the same problem before the new version, manually remove the extra lines in the plugin editor, or comment them out if you have to.
I normally have the plugin editor disabled, choosing to upload from an offline text editor to the control panel if I absolutely have to make a change to a plugin, so it did not initially occur to me that it would be a thing.

• This reply was modified 2 years, 6 months ago by Carike. Reason: See post

I’ve had completely conflicting advice on this…where can one get a definitive one?

From a good lawyer.
And if they are telling you that you can remove copyright info, then get a better one who understands copyright and open source broadly and the GPL in particular.

You can modify the code to your liking. That is what the GPL is for. It is one of the Four Freedoms.
You cannot remove copyright information with regards to the work of others that you kept. That is not what the GPL is for.

:wave:

Core prioritizes strings submitted by www.ads-software.com contributors above po and mo files.
You can submit your translations here, while signed into your www.ads-software.com account (the one you used for this post): https://translate.www.ads-software.com/projects/wp-plugins/wp-user-avatar/stable/tr/default/

You can then submit a PTE (Project Translation Editor) request here: https://make.www.ads-software.com/polyglots/
You can aso join the Turkish Slack: https://make.www.ads-software.com/polyglots/handbook/translating/teams/local-slacks/

Because volunteer-time is limited, pretty much all locales prioritize editor requests over checking waiting strings.
Once some of your strings have been checked (to see if they comply with the style guide and glossary), your strings will be approved automatically.
You will also be able to go back and approve your own strings from before becoming a PTE.

Welcome to contributing!
If you have any questions, you are very welcome to join the Polyglots channel on the Make www.ads-software.com Slack.
You can find instructions here: https://make.www.ads-software.com/chat/

A login system is not the first plugin you want to write as a self-taught developer ??
But neither is modifying your wp-login file, if I am being completely honest.
Login, rights management (CAPS) and DB queries are places where things can go VERY WRONG.
Just because they work, does not mean that there are not unintended consequences.

Simply renaming your login file won’t work, no.
Depending on your hosting plan, you may be able to install more than one installation. I actually recommend breaking a test installation on purpose at least once. ?? To see what it does and to understand why it happens.
In short, if you rename the file, you are going to have difficulty logging out and chances are a number of your plugins will stop working.
I have to add here that making other changes to the file, in addition to renaming it, would solve some of these issues and there are tutorials around the web on how to do that, but it isn’t a good idea.
And, as you have found out, those changes will be over-written the moment you update.

Which leaves you with the option to turn off auto-updates and update manually (copying in the modified file again as soon as the update is done), but that isn’t recommended.
There are ways to get an MU plugin to do the “update” for you, but again, that isn’t recommended either.
All of those options interfere with the intended working of the software.

It *is* possible to add your game as a custom page template to a theme, although generally you want to keep content and appearance separate, so that should not be your first option.
The “safest” way is most likely to look for a reputable code snippet plugin and add your game to a page that way.
Although, that does have risks too and you should make sure that you understand data validation and sanitation.
You could also consider a Custom Post Type.
You can then restrict access to the page through any reputable membership plugin that offers the functionality.

Basically, even though we can have some discussion here about considerations you may want to keep in mind for different approaches, it really depends on what you are trying to do and why – and none of us can see that here. Even if we could, it is beyond the scope of the help that is intended for the forums.
There are a number of resources out there. Perhaps you may also want to consider the WordPress Stack Overflow. The thing is that you need to be willing to post your code in order to receive specific answers there, or here for that matter.

You should always keep backups, but much more so if you have highly customized code.
I’m really sorry. You must have had a pretty bad day.

The reason why you should not be editing Core code is because those files will be over-written every time that WordPress updates.
If themes or plugins update, the files in those folders will be over-written too.
Which means that you either have to place files that you don’t want to be over-written outside of the normal WordPress file structure (not recommended), or you have to save the code as an MU (Must Use) plugin. That can’t be uploaded or deleted from within /wp-admin/.

The thing with the WordPress login page is hard-coded in a number of places, often in plugins, even though it should not be. So, you may find yourself locked out of your site, or a myriad of other unintended behaviour can happen if you try to change that URL (particularly on log out).

You really should consider Steve’s advice to use an existing login plugin as a model for your own code.

Alternatively, you may want to consider whether WordPress is the right platform for your game, now and into the future.
While it makes the web accessible to anyone, it really isn’t suited for every application, nor can it be.

Best of luck!

Hallo there.

www.ads-software.com is the site that creates, distributes and supports WordPress Core.
The WordPress software is installed on your own site and no one at www.ads-software.com has access to your website.
The tables you are referring to, are created by a plugin, not by WordPress Core.
www.ads-software.com distributes plugins and themes for the convenience of website owners, but plugins are created by third parties – and www.ads-software.com does not control those either.

The plugin that creates those tables was closed quite some time ago.
Yui’s advice is really the best thing to do here – try to find an actively maintained plugin from the www.ads-software.com repository that does the same thing.

All the best of luck!

Sites go into maintenance mode during updates to help prevent sites from crashing ??

It usually does not lead to significant downtime, but your site seems to be doing more frequent updates than most ??

How many plugins do you have?
Do you have a record somewhere of the dates and times that your site went into maintenance mode?
If you keep a list of all of your plugins and their versions, you should be able to cross-check if these times coincide with new theme / plugin versions being released.

You *could* disable auto-updates for all of your themes and plugins, if you would like to schedule when your site will be in maintenance mode.
That having been said, having auto-updates enabled is the “official” recommendation.

You may also want to reinstall WordPress Core.
While that should take care of possible unauthorized changes or extra files, you still need to find the source of the problem.
If, just for example, a plugin installed a backdoor, it could be used to make the same changes again.

Do you use a firewall plugin?
If not, you may want to look at one that blocks bad (or here malicious) queries.