lang pt_br #9
Open
lang pt_br #9
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Now fully compatible with pre-RE and RE Hercules `item_db*` tables. Added support for new `upper` values from HerculesWS/Hercules@1caae98 Closes #1
This is a modern and simple HTML5 theme. Based on Emphaino Theme for Wordpress (https://github.com/sriniguna/emphaino).
Minor fixes to Hello World addon.
Disabled TidyHTML by default because it's not working well with HTML5.
…ame in the chatlog
|
Just to clarify, this translation is done according to the flux of Xantara. It may be noted that the file is translated to 7 months in my github. https://github.com/Megasantos/Fluxcp/blob/master/lang/pt_br.php |
Correction
Properly escaped the userid in account view and the destination charname...
Fix #7 Add shadow item mask
Fixed incorrect usage of ; Special thanks to Viollently Happy who reported it.
Follow up a293953 Fixed incorrect usage of ";", should be ","
- Restored editing, duplication, and viewing for pre-re and re item modules. - Added default values for nullable entries in pre-re and re item modules. - Added setting for Max Base Level in config/servers.php. - Max Equip Level now defaults to Max Base Level. - Cleaned up some typos and comments.
Compatibilized item module.
- Corrected values of 'Small' and 'Medium' - Properly attributed Hercules on the error page - Replaced invalid copyright with appropriate attribution
The job wasn't identified so it doesn't appear on Online Characters or Server Information
- Merged security patch from Xantara's FluxCP.
- Since there (currently and in future) is no difference between the table structure for renewal and pre-renewal databases, it makes no sense to have extra code that makes a distinction between their names. A server will always use either one or the other, never both at the same time. - If you have a mob_db_re and/or item_db_re table, please rename it to mob_db and/or item_db_re, respectively. Signed-off-by: Haru <haru@dotalux.com>
players online does not count autotrade merchants, population is now the total count Signed-off-by: mleo <mleo1@hellokitty.com>
update to server status
- Closes #32 Signed-off-by: Haru <haru@dotalux.com>
* Fixed an exploit in the Item Shop. * Fixed exploit in the Registration and Password Recovery.
- The user-facing message mentioned that the password could not be longer than %d characters, while in fact it was checking whether the password contained more than %d non-alphanumerical characters. - It makes no sense at all to limit the number of non-alphanumerical characters. Why would anyone want to force people to use more letters and numbers and less symbols anyways? Signed-off-by: Haru <haru@dotalux.com>
- The setting is disabled by default, because, according to user
reports, it fails to accept some otherwise perfectly acceptable email
addresses, according to RFC 822 and its descendants (2822, 5322). See
the php manual page of 'filter_var' for more details.
- Examples of rejected email addresses, according to user tests:
* Any address with a not fully qualified hostname part (such as
user@localhost)
* Any IDN address (with non-ASCII symbols in the hostname or username)
* Any address with an username ending with a `.` (such as
user.@example.com)
* Any address with a quote-delimited string in the username part
(such as "hello world"@example.com or hello." ".world@example.com)
- Before this commit (and after a904a24),
the checks were unnecessarily stricter by default, only allowing
email addresses with alphanumeric hostnames and alphanumeric with a
small set of symbols usernames (rejecting addresses such as
user@host-name.com, user+foo@example.com or a@example.com).
- The default checker has been switched back to the
pre-a904a24a6f10e28b14f37f694cc09ed76da1e68d version (allowing
anything as long as it contains an `@`).
- Thanks to Strteusel for the filter_var suggestion.
Signed-off-by: Haru <haru@dotalux.com>
Was being able to see the log paypal two accounts with any user, without being administrator for txnview account be in the wrong array.
Checks if payment notify recieved from paypal servers. Prevent two critical bugs. Special request to paypal notify with bypass of paypal reciever email check. 1. Creates executable .php file in payments log folder via saveDetailsToFile() function. 2. Sending fake completed payment to get unlimited credits. Hack report example: https://gist.github.com/S-anasol/9c91d92686bd0e882ee672a394fa1567#file-gistfile1-txt-L45-L48 Highlighted lines is bug execution example. Bypass paypal email check(receiver_email) and create shell file(txt_id) with any code inserted into any request variable.
[super very critical] RCE and Unlimited Credits PayPal vulnerability.
Paypal doesn't handle 80 port connections. Switching to SSL. Also added host list to allow sanbox testing :)
Fixed constructors for PHP 7.0
Security fix
SSL Requirement and allow sandbox servers
* Updated recaptchalib.php to the latest version. * Updated Google reCaptcha V1 to Google reCaptcha V2
Update from original
Column 'view' for item_db became 'view_sprite', proper changes were made so as not to affect the themes folder for the item module
Item Module update for August 2017 changes
When md5 is active, the " trim($ password) == '' " condition is no longer valid, because even if the password is blank a 32 character code is generated.
Updated code that was using deprecated PHP functions: Array and string offset access using curly braces in lib/markdown/markdown.php $file_contents = file_get_contents($file_path, null); // Deprecated $file_contents = file_get_contents($file_path, false); // Updated and not deprecated in lib/Flux.php
Upgrade FLuxCP to php8.2:
extend birthdate
correct auth validation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://github.com/JulioCF/itens-gerais/blob/master/CPs/Flux/Fluxcp_br/lang/pt_br.php