Skip to content

UPDATE : Development to Master #2683

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 65 commits into from
Apr 5, 2018
Merged

UPDATE : Development to Master #2683

merged 65 commits into from
Apr 5, 2018

Conversation

TheSerapher
Copy link
Contributor

@TheSerapher TheSerapher commented Mar 3, 2018

Thanks everyone contributing! This project may not be actively maintained anymore but at least we have some community support to keep it alive 👍 If you are on the list of contributors make sure to keep an eye on the issue tracker after release. There may be issues coming in with a feature you worked on, would be great to have someone assist in debugging any found issues then.

1.0.9 (April 5th 2018)

Fixed Issues

  • Fixed issue on graphs page (Thanks @tperalta82 !)
  • Show error message when trying to send mail to users (Thanks @mecab !)
  • Removed some name validation on contact forms (Thanks @mecab !)
  • Calculate the efficiency correctly in API (Thanks @smiba !)
  • Expend CSRF token expiry (Thanks @smiba !)
  • Improve est. diff for constantly changing coins (Thanks @smiba !)
  • Fixed mobile display issue of wallet status (Thanks @TopoX84 )
  • Fixed mobile display issue of peer info (Thanks @TopoX84 )

Features

  • MySQL Master/Slave switching based on SQL queries (Thanks @tperalta82 !)
  • Added a switch to ignore cron errors (Thanks @mecab !) - USE AT YOUR OWN RISK
  • Adjusted block overview percentage colors to be less "dangerous" ;-) (Thanks @smiba !)
  • Added 'start' parameter to ´getusertransactions´ api page (Thanks @desaerun !)
  • Replaced recaptcha-v1 with recaptcha-v2 (Thanks @AmazingDreams !)
  • Added more APIs for the price checker (Thanks @bziemek !) See Wiki for details.

tperalta82 and others added 30 commits December 3, 2017 03:10
Implement Read/Write Split directly on PHP / Fixed statistics->graphs page
.gitignore composer.lock, and remove composer.lock from repo
…d of returning false it was returning the this->sqlError.... which by then was returning the return false, the problem was the log in the cron that was misleading, took 2 days figuring this one out
Had to rewrite all the mysqli->error/errno to mysqli->lastused because of the read/write splitting, shoud be working now
Reverted notifications code back to previous version
Added  the lastused property to mysqlms, so that when calling the error/errno we know what was the lsat connection used, same for insert_id
Possibly fixed all the MySQL errors from my previous pull request
Fix INSERTS with Selects inside
Subtracting numbers from datetime causes wrong value, or raises error depending on MySQL version/configurations
Non-alphanumeric character causes some problems if used in the mail header (i.e., sender name or subject), but the filled info is just used in the mail body so removing the validation is safe at this time.
Fix SQL in cleaning up old notifications
Remove unnessesary validation in sending contact form
Fix errors while sending mail is not displayed in contact form.
Add -t option to ignore too old cronjob active flag
Small change I overlooked
Fix: Calculate the efficiency correctly in API
Often my pool is at 101% because thats just luck, however bright red makes users often think something is wrong

I'd say up to 115% make it orange, its less worrying.
Together with #83efd60
Do not show in x amount of blocks, if the coin’s difficulty changes on
every block
Change it to 15 minutes, 2 minutes is not enough.
@AmazingDreams
Copy link
Contributor

I'd like to say that Recaptcha v1 will stop working March 31st: https://developers.google.com/recaptcha/docs/faq#what-happens-to-recaptcha-v1

Any calls to the v1 API will not work after March 31, 2018.

So perhaps it would be a good idea to make a hotfix for the recaptcha thing - if there is no entire release possible.

@TheSerapher
Copy link
Contributor Author

If in a hassle people can always just switch to the development branch in the time being. As this is officially unsupported, no expectations should be made by users to the project to fix things "on-time".

Bit I think we can do it before the 31st, even though some things may have to wait for a later date.

@TheSerapher TheSerapher merged commit 8fa8d6c into master Apr 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants