یه سوال در مورد تغییرات نسخه ی 4.1.14.1

[PersianEngineer.Com 27]

سلام

کسی هست که بتونه قسمتی که در تغییرات نسخه ی 4.1.14.1 برای کاربران عادی غیرقابل دیدن شده رو قرار بده؟ یعنی این:

اینم لینکش:

https://invisionpower.com/release-notes/41141-r49/

 

[MReza 407]

پستی که دسترسی اون برای گروه‌های کاربری عادی محدود شده:

مخفی کننده

4.1.14 introduces some changes to the \IPS\Http\Url class.

We are making these changes primarily to resolve a number of bugs with encoding and decoding parts of URLs, especially where non-ASCII characters are used where symbols and non-latin characters could cause unexpected behaviour and errors in some browsers. The changes also make the class easier to understand and work with.

We have tried to make these changes as backwards compatible as possible, and most applications or plugins will not be affected, but these changes make the class more strict, and therefore if your application or plugin is providing the class with invalid URLs, it may now throw an exception where it would have previously allowed the invalid URL. You should review the information below carefully and thoroughly test your applications and plugins with these changes. An alpha, which includes these changes, is already available.

 

Summary of changes

Rather than a single \IPS\Http\Url class, there are now 3 classes, each of which extends the previous:

• \IPS\Http\Url, objects of which are external URLs
• \IPS\Http\Url\Internal, objects of which are internal URLs
• \IPS\Http\Url\Friendly, objects of which are front-end friendly URLs

You still create objects in the same way (so backwards compatibility is maintained) using ::internal(), ::external(), etc. or there is a new ::createFromString() method to just take a string.

Each has properties appropriate to it. So \IPS\Http\Url\Internal has a $base property for "front" or "admin" and \IPS\Http\Url\Friendly has properties for $seoTemplate (a key from the the FURL definition), $hiddenQueryString (the properties which are part of the query string), $seoTitles, and $friendlyUrlComponent (which contains the "/topic/1-foo" bit, automatically figuring out if that's in the query string or path depending if rewriting is enabled). So you no longer have to do things like ->getFurlQuery(), ->getFriendlyUrlData(), etc. all that is accessible from properties.

Within the properties, it is clear what is encoded and what isn't. The $url property is appropriately encoded, while $data is all decoded. The class adheres to RFC 3986 for what should be encoded and what is allowed.

So for example, here's a printout of a topic's URL:

IPS\Http\Url\Friendly Object
(
    [base] => front
    [seoTemplate] => forums_topic
    [hiddenQueryString] => Array
        (
            [app] => forums
            [module] => forums
            [controller] => topic
            [id] => 129
        )

    [seoTitles] => Array
        (
            [0] => this-is-a-test-topic-with-an-emoji-in-it-?
        )

    [friendlyUrlComponent] => topic/129-this-is-a-test-topic-with-an-emoji-in-it-?
    [isInternal] => 1
    [isFriendly] => 1
    [url:protected] => http://localhost:8888/ips4/topic/129-this-is-a-test-topic-with-an-emoji-in-it-%F0%9F%98%80
    [data] => Array
        (
            [scheme] => http
            [host] => localhost
            [port] => 8888
            [user] => 
            [pass] => 
            [path] => ips4/topic/129-this-is-a-test-topic-with-an-emoji-in-it-?
            [query] => 
            [fragment] => 
        )

    [queryString] => Array
        (
        )

)

You can see that:

• $hiddenQueryString contains the properties which are "disguised" by the friendly URL, and there are also properties for $seoTemplate and $seoTitles. I don't need to call a method to get any of that.
• $url has the full URL encoded as appropriate (depending on your browser, the percent encoded characters may render the Emoji properly - Safari does this - or you may actually see them - IE does this) while $data has it all decoded. I don't need to urlencode() or urldecode() anywhere. All properties are present in $data so I don't have to do isset() checks everywhere.
• $isInternal and $isFriendly are set for backwards compatibility

There are new simple methods for things like getting the "correct" URL. So all the code we had before in the dispatcher to verify and redirect is simplified to just:

$correctUrl = $url->correctFriendlyUrl();
if ( $correctUrl )
{
	\IPS\Output::i()->redirect( $correctUrl, NULL, 301 );
}

There are also methods for setting data - setScheme(), setHost(), setPath(), etc.

 

Backwards incompatible changes

• You can no longer call new \IPS\Http\Url() directly to figure out if a URL is internal and should only call this constructor directly if you know the URL is not internal. Call \IPS\Http\Url::createFromString() to ensure you get an object of the correct class back.
• \IPS\Http\Url::reconstruct(), setUrl() have been removed (but they were protected anyway)
• Passing the $verify property to \IPS\Http\Url::getFriendlyUrlData() is removed.
• \IPS\Http\Url::makeFriendly() has been removed.
• \IPS\Http\Url::examineFurl() has been removed
• \IPS\Http\Url::utf8ParseUrl() has been removed

Deprecations - no code changes necessary now, but you should consider making changes soon

• \IPS\Http\Url::furlDefintion() and seoTitle() have been moved to \IPS\Http\Url\Friendly, currently an alias to maintain backwards compatibility but it’s use is deprecated.
• \IPS\Http\Url::csrf() and acpQueryString() have been moved to \IPS\Http\Url\Internal. Currently an alias to maintain backwards compatibility but it’s use is deprecated and you should only call this method on objects of \IPS\Http\Url\Internal.
• \IPS\Http\Url::stripArguments() is deprecated. Use stripQueryString().
• \IPS\Http\Url::createFromArray() is deprecated. Use createFromComponents()
• \IPS\Http\Url::rfc3986() is deprecated. Casting to string now always returns an RFC 3986 conforming URL.
• \IPS\Http\Url::getFriendlyUrlData() is deprecated (and passing the $verify property is removed).

 

[sIiiS 13]

آقا دستت درد نکنه

امکان داره این لینک رو هم بیاری ببینیم چیه

https://invisionpower.com/forums/topic/431182-4114-alpha/

 

[MReza 407]

تاپیک طولانی هست. با ۱۳ پست.

Posted July 13

مخفی کننده

4.1.14 Alpha

Alpha installs will report as an alpha build. You can upgrade from the previous release but you cannot upgrade as we release alpha updates - you will have to re-upgrade again.

 

Download

Alpha releases cannot be upgraded to beta or final releases. Do not use on a live site. Technical support is not available.

Download: https://www.invisionpower.com/clientarea/index.php?app=nexus&module=clients&section=prerelease&branch=alpha

Developer tools: https://remoteservices.invisionpower.com/devtools/alpha

Please post any issues you have in the Alpha and Beta category of the bug tracker. We may ask you to submit a ticket if we need access to your install.

We will reply in this topic when the alpha is updated. Feel free to start other topics in this alpha area as you wish. Anyone can use and test these alpha builds but, by their technical nature, they are more designed for advanced users.

Developers can download the dev tools here: https://remoteservices.invisionpower.com/devtools/alpha

 

This first alpha has a long areas to test list. Future alpha builds we hope to do more frequently to keep the list more manageable. This list contains all areas that were touched (bug fixes, changes, feature additions, etc.) since the last full release.

Areas to test

• Using multimod tools in forums/topics/etc
• Registration chart in ACP dashboard
• Rebuilding Gallery thumbnails
• Logging in on a community which has been converted
• Deleting content
• Rebuilding attachment thumbnails queue task
• Upgrading Calendar from before 3.2
• Editing custom field values for purchases - on purchase, in client area, and in ACP
• Custom editor buttons, especially using the option value
• Building core app
• Pagination on gallery images and downloads files, including when both comments and/or reviews are enabled/disabled
• In the editor, double-click on an image and edit (or do not edit) its size
• Logging in on a community which has been converted from Vanilla 2
• Unhiding topics, especially one which had been moved in 3.x.
• Members can view/download attachments that either they uploaded or they have permission to access the content it is attached to
• Report center, especially notifications sent to moderators about reports
• Multi-Redirect routines, including in the installer and upgrader !! Test thoroughly !!
• Matrixes - both embedded in a form (e.g. when editing permissions for a group, meta tags, thresholds for prices in shipping rates, tax rates) or not (e.g. editing notification defaults, currencies) - especially that the options to add/remove rows work correctly where appropriate !! Test thoroughly !!
• Submitting status updates
• Redis 
• Search terms including operators !! Test thoroughly, including across multiple MySQL versions !!
• Bulk mailer, especially that emails get sent to all desired members !! Test thoroughly !!
• See code - no specific area to test, but significant change which testers should be aware of
• IP address tools in ACP / ModCP
• Creating calendar event on mobile
• Upgrader, especially from pre-4.0 where manual queries have to be ran
• Todays birthdays widget
• Half-star ratings, especially in database records
• Generating invoices in ACP, especially when adding products whose prices are adjusted by their custom field options
• Latest file info on categories in Downloads
• Significant code change to be aware of generally, but especially test that incorrect friendly URLs redirect correctly, and Pages URLs are working - especially with unusual configurations such as the gateway file !! Test thoroughly !!
• Any operation which would cause a folder in /uploads to be deleted - for example, deleting a theme - check the folder is deleted correctly
• Searching specific blogs
• New installs - JS is working
• Requirements checker on new installs, upgrades, and in ACP with mbstring.func_overload php.ini configuration enabled or disabled
• Pagination on the content section of progile
• Downloading plugin in developer mode
• Downloading applications in developer mode and installing apps generated on this version
• iCal imports, especially single day events
• Upgrading from 3.x with Pages installed
• Resending failed emails from the mail error log, test against PHP, SMTP and SparkPost
• Refunding PayPal transactions
• RSS export / import
• Searching PMs
• Autolink in editor, especially that it does not autolink URLs after you have specifically removed the link
• Hover cards on members
• Dropdown to select a prefix, especially where the prefix contains special HTML characters (<, >, etc)
• Reverting templates in ACP template editor
• Editor behavior after submitting a new comment or editing an existing comment. Particularly that no JS errors are thrown and subsequent comments can be submitted without issue !! Test thoroughly !!
• Following a topic/etc after paginating within it
• Database checker !! Test thoroughly !!
• Notifications spawned from @mentions - including that they are not sent if the mention is in a quote
• Adding links in the editor, especially on mobile devices
• Basic BBCode tags
• Member import - especially that birthdays in the incorrect format are not imported
• Paginating on the results from the “advanced search” on any ACP table, but particularly where the search criteria was a member such as in Administrator Logs
• Amazon S3, especially when using a region that is not us-standard/us-east-1
• Uploading files to any area - test that the upload can go through, especially as part of a multi step upload process (like uploading gallery images), but also that if you abandon the process half-way that the file is removed from disk after the cleanupfiles task runs one day later !! Test thoroughly !!
• Checking out with PayPal Billing Agreements
• Searching by number of comments / reviews / views
• Viewing transactions / invoices / shipping orders in ACP if Google Maps integration is disabled
• Selecting quoting (when you highlight post content to quote), especially on iPad and mobile devices
• Pages blocks external embed (i.e. click “External embed” from the dropdown actions for a block in the ACP), especially with multiple blocks per page
• Test no JS errors are logged when using private browsing / in cognito mode when typing into the editor
• Inserting emoticons and autolink embeds into the editor
• Custom permission error messages in Gallery categories
• Setting particular payment methods for a product, but that it also defaults to all
• Purchasing products as part of the registration process, especially that an error is shown correctly if the user does not have permission to purchase the chosen product.
• The link to go to the first unread post (i.e. the blue dot) takes you to the correct post
• Purchasing products as part of the registration process, especially if you abandon the purchase and go back to the registration form
• Number input fields (for example, setting a price on a product) when using a locale that uses commas for decimal points and periods for thousand separators 
• Performance of “Content I posted in” activity streams across different MySQL versions
• Custom slugs for pages articles, especially when using the same slug in different categories
• Topic feed widgets, especially after a new topic/post is added
• Search result ordering
• Digests
• Searching by particular dates (for example members joined after date) in ACP member list, especially with non-US locale
• Downloading files stored in AWS which have special characters in the filename
• Sorting database records, especially on fields which cannot be filtered such as text fields
• Quick Translating, especially translating phrases which are links (e.g. breadcrumbs, default activity stream link, etc) !! Test thoroughly !!
• Modal dialogs, especially that dragging the mouse does not incorrectly dismiss the modal
• Correct results (ensuring nothing the user doesn’t have permission to view) are returned when a search includes both a term and tags, and the search is set to show results for either match
• Moving between images in the details pane when uploading multiple images to Gallery
• Thumbnails use throughout Gallery link correctly to image page
• Buying downloads files when the site has multiple currencies set up
• Anti-Fraud rules based on a particular MaxMind score
• Syncing comments on Pages articles with forum topics. Test against multiple PHP versions, especially submitting new articles
• Gravatar - especially that the default photo shows when enabled if the site is being served over https
• "Image proxy is used correctly on RSS imports, especially if the srcset attribute is used on an image in the RSS content
• Includes general changes to the parser which testers should be aware of"
• Multimod tools on Gallery images, especially on Android devices or when resizing the browser window between selecting images and submitting the form
• Signature limits, especially with secondary groups
• Start typing a mention and then use backspace to remove the @. Test across multiple browsers. !! Test thoroughly !!
• Uploading many images to Gallery - should have a limit of 100 images, and uploading to other areas are not affected by this change
• Attempting to upload a file which is above the allowed file size
• Flags in language selector on a Windows server
• Checking out as a guest works on all gateways
• Titles display correctly, especially on older (pre 2012) Android devices and old versions (4 or older) of Safari
• Incoming emails, especially with attachments
• Removing shipping charges when generating an invoice manually in the ACP
• Inserting images into the editor using the dropdown menu at the bottom of the editor, especially that the inserted image conforms to the ACP-defined maximum image sizes
• File titles display correctly in the Downloads reviews widget
• Instant notifications
• Events that span or repeat are created correctly showing the correct dates after creation, and events which span a long time and/or repeat frequently do not produce an error
• Single day events in Calendars how on the correct day
• Using custom fields with options (i.e. radio and/or select, including multiselect) where the options are numerical. Especially fields on purchases in Commerce.
• Viewing invoice in ACP - especially that it is appropriately responsive
• The titles of widget feeds (e.g. topic feed) continue to display correctly after upgrade, but can subsequently be translated on multilingual sites
• Importing XML files (such as uploading themes and languages) and RSS imports
• Share links for comments on database records
• Setting up Google Maps integration in Community Enhancements
• Restricting products to certain groups - especially guests

 

Posted July 14

مخفی کننده

New build available. Areas to test:

• PHP 7 support

• Using the run anyway for SQL queries on upgrader - ensure that the queries actually run and you’re not stuck in a loop. Same with the manual option - ensure you are not in a loop.

• Check for issues in upgrade routines related to redirecting to the next step and displaying errors along with the retry/continue option.

• Upgrading with MySQL strict mode.

• Filtering by Pages fields when you select no field (should show all results)

• Voting on a poll a second time results in a second vote being stored

• URLs in editor (posting, editing, etc.)

• FURL customizations

Posted July 15

مخفی کننده

New build available. Areas to test:

• PayPal subscription payments fail if the gateway has been deleted
• Pages database imports
• Third party plugins/apps and the database checker playing nice together
• Editing Pages database categories
• Resized images in editor showing correctly on mobile
• Using S3 file storage with spaces in filenames
• Recurring calendar events showing on proper dates
• URL formatting throughout the suite
• Issue with PayPal billing agreements if the agreement is cancelled before Commerce syncs

 

Posted July 18

مخفی کننده

New build available.

• When an application is uninstalled all member reputation will now recount
• Update buzz.js (HTML5 audio javascript) and change settings to allow for audio support on more devices
• Fixes an issue where you are taken to the last post in a topic instead of the beginning of the topic if you haven't read it
• SEO adjustments to reviews and breadcrumbs

(Note that with each build there are many other smaller fixes that I do not include in these lists because they are fairly small.)

 

Posted July 20

مخفی کننده

New build available.

• Gallery digest daily email
• Upload and then re-uploading profile photos
• Google ads in iPad landscape mode
• Emoticons menu in editor
• PHP 7 support
• Recurring calendar events both in calendar and in widgets
• Using @ mentions in Chrome
• Editing a page losing database relationship
• Large profile images imported from remote URLs properly resized

Thank you to everyone who is helping test our alpha builds. Special thanks to @Adlago and @Martin A. who have been reporting quite a bit to the bug tracker.

New build available.

• Firefox not properly truncating embedded content when inside of a spoiler
• Clear all REDIS cache improvement
• Importing a Pages database can duplicate fields, categories and/or templates
• Fixed issue with Firefox breaking out of quotes in editor

This build also includes large changes to the search index and Activity Streams to increase performance particularly in "content I posted in" Streams. You should see a search index rebuild task start on upgrade. If you have a large database and use content I posted in streams you should see improvements.

 

Posted July 21

مخفی کننده

New build available.

• Clicking mentions taking you to the correct comment
• Last post data in forums where you cannot view other member topics
• Editing codeblock
• Added a basic PREV | NEXT pagination option for larger member tables when member searching
• Queued posts in archived topics
• Selective “Quote this” quoting
• ModCP hidden content tab
• Changing default application

We plan on upgrading our site next week and will follow on that with public beta releases. We really appreciate everyone testing these alpha builds. It should make 4.1.14 very stable.

 

Posted July 22

مخفی کننده

I did a second new build for today to address a couple recurring issues people were seeing in this morning's alpha.

• Editing a post with embeds
• Long usernames and display oddities
• Database checker and support tool
• Merging topics in Question and Answer forum
• Meta titles in database categories
• Item titles may show vertical on mobile devices when using Android or other out of date browsers
• YouTube embeds

Please keep in mind you cannot upgrade between alpha builds. You have to install or upgrade from scratch.

 

New build available.

• Removed hyphen CSS class since Firefox likes to over-hyphen
• Fix for topic open/close text breaking in forum view
• Fixed strange editor behavior in Firefox after removing formatting from paste (Firefox is the new IE)
• Added support for defining definite articles for content types
• <ABBR> tag fixes
• Added a canonical tag for default Pages pages to avoid any claims of duplicate content when accessing page via “site.com/folder/“
• Facebook video embeds

 

Posted July 25

مخفی کننده

New build available.

• Fixes an issue where non-latin characters in username restrictions don't work
• Repositioning profile photo
• Embeds
• Review counts in embeds
• Attempt to make old Android tablets display things better
• Quick translating in AdminCP
• Reordering categories in the AdminCP via drag and drop
• Charts and graphs in the AdminCP
• Uploading themes
• Date format on Windows
• CC and BCC support for Sparkpost emails

As always, even if I do not mention them here all bugs marked fixed in 4.1.14 in the bug tracker are included in each build.

 

Posted July 26

مخفی کننده

New build available. We are getting closer to beta stage now. Anyone who follows our bug tracker will note how quickly we are moving through fixes now.

• Editing customer notes in Commerce
• Facebook/Gfycat honoring max video width setting
• Fix for back button not doing anything if on the first page of a topic
• Mass-actions on members in AdminCP
• Google Maps API keys
• Items showing the same rating system-wide
• Notification counts

And, as always, dozens of other small and less interesting changes.

 

Posted July 29

مخفی کننده

New build available. Tomorrow we will have one more alpha build for testing over the weekend. On Monday our site here will be upgraded to 4.1.14 and the first public beta will follow soon after.

• Plugins with many language strings timeout
• "Notify of replies" under reply editor not updated when toggling Follow button
• Lost password email
• Login with Google
• Facebook embeds
• Pages database Yes/No field filter
• Fixes an issue where downlods changelogs and file descriptions may inadvertently claim attachments from each other
• Fixed using ' " < > in linked URLs
• Images in incoming emails to Commerce
• Fixes issue where changing database permissions doesn’t update all categories
• Making it clearer that only admins/mods can see email addresses on front end. Lots of confusion about this.

As of this post, we have zero open bugs in our alpha/beta bug tracker category. We sincerely thank those of you testing these alpha releases.

Public beta releases will start next week. Here is a preview of how we will be handling beta releases:

نقل قول

We consider beta releases safe to use on a live site but keep in mind these are beta releases so will probably have issues. Please consider that before upgrading your live site.

Beta releases are semi-supported through this process:

• You must maintain a backup of your site, know how to restore a backup if needed, and be comfortable with the fact that betas will have issues. If a beta causes major problems we cannot guarantee a fast resolution so it will be on you to restore a backup if this happens.
   
• You cannot submit tickets for beta releases. If you have any bugs in the beta they must be submitted to the beta releases bug tracker.
   
• If our staff needs more information on a bug report from you in private, they will reply to the bug report and ask you to submit a ticket referencing the report. This is the only time you can submit a ticket about a beta release. Any other tickets about beta releases will be closed.
   
• Any issues on your community during the beta stage may not be fixed until a future release. We will usually not specifically address any individual issues on your community. This means you will have to wait (sometimes several days) for a new release to get fixes. Normal support SLAs and services will not apply.

In short: we will fix issues that come up but it may take longer than normal and will usually not be private support. Do not use a beta if you cannot handle waiting a few days between releases for fixes or if private support via tickets is important to you.

We encourage you to report bugs in the beta release category of the bug tracker and thank you for doing so. Note that we may not fix all reported bugs in the beta series as our goal is to fix major issues between beta and final. Minor bugs will wait until the next version.

 

 

Posted August 2

مخفی کننده

The 4.1.14 alpha series has ended. The beta is now available.