[ITEM]
How do the async features like author control work? Does Grid talk to an external service? Table already exists error when I want to activate Grid. Why? How do I use Grid landingpages? How do I get new box types? What about Grid an caching?
[/ITEM]
Grids 4.7.1 Download 5,8/10 1152 votes
Description
What is Grid?
- Grid allows Editors to easily create and maintain Landingpages
- Grid is build of a grid containing Containers and Boxes
- Grid is a CMS-neutral Library and this is the WordPress plugin that implements it
Types of Boxes
Static Boxes –
Free-HTML-Box
- Medialibrary-Box
Video-Box
List-Boxes –
Ordered and filtered Lists of Contents
Number of Items as well as criteria for sorting and filtering are configurable
Configuration Boxes –
Container configuration
Slot configuration
Content-Boxes –
Single Posts of any kind as Teasers
Reuseable Boxes – Mac media players.
All Boxes may be reused across several Landingpages
Easy extendable with new boxes. Have a look at doc.the-grid.ws (english is coming soon).
Arbitrary section
Learning jQuery Fourth Edition Karl Swedberg and Jonathan Chaffer jQuery in Action Bear Bibeault, Yehuda Katz, and Aurelio De Rosa jQuery Succinctly Cody Lindley.
There’s a documentation at doc.the-grid.ws (english is coming soon)
Installation
- Upload
grid-wordpress.zipto the/wp-content/plugins/directory - Extract the Plugin to a
gridFolder - Activate the plugin through the ‘Plugins’ menu in WordPress
- Build landing pages at
Landing Pages,Switch into the Gridand on next screensave changes - Look for more plugins on wordpress.org that can provide grid boxes
FAQ
Generally speaking, yes! But you can easily turn it off in grid settings. And there will be no talking to any external server anymore. Alternatively you can host your own grid async service on your own server. Note that our service will not use or save any personal data at any time. It only uses data to keep the function going.
This happens if grid was installed previously and could not be uninstalled correctly. You have to delete in the wp_options the option_name „grid“. Then try again to active Grid plugin.
Goto Settings->Grid and choose which post types should be able to use Grid. Than goto one of the activated post types and click on Switch into the Grid and on next screen save changes. Now you can drag and drop your landingpage.
Have a look at wordpress.org for plugins that provide new grid boxes or you can create your own plugin and use the grid_load_classes action to add new box classes. You can find a documentation at doc.the-grid.ws
Grid works fine with a varnish configuration and the comet cache plugin. If you use another caching that does not work with grid please contact us on github.com or wordpress.org.
Reviews
Tested a few grid plugins. This is nothing. Sorry!
-->If you are migrating from the .NET Framework 4.7 to 4.7.2, review the following topics for application compatibility issues that may affect your app:
Core
Allow Unicode in URIs that resemble UNC shares
| Details | In System.Uri, constructing a file URI containing both a UNC share name and Unicode characters will no longer result in a URI with invalid internal state. The behavior will change only when all of the following are true:
|
| Suggestion | Applications working with URIs consistently containing Unicode could have conceivably used this behavior to disallow references to UNC shares. Those applications should use IsUnc instead. |
| Scope | Edge |
| Version | 4.7.2 |
| Type | Runtime |
| Affected APIs |
Support special relative URI notation when Unicode is present
| Details | Uri will no longer throw a NullReferenceException when calling TryCreate on certain relative URIs containing Unicode. The simplest reproduction of the NullReferenceException is below, with the two statements being equivalent:To reproduce the NullReferenceException, the following items must be true:
|
| Suggestion | Users depending on this behavior to disallow relative URIs should instead specify UriKind.Absolute when creating a URI. |
| Scope | Edge |
| Version | 4.7.2 |
| Type | Runtime |
| Affected APIs |
JIT
Incorrect code generation when passing and comparing UInt16 values
| Details | Because of changes introduced in the .NET Framework 4.7, in some cases the code generated by the JIT compiler in applications running on the .NET Framework 4.7 incorrectly compares two T:System.UInt16 values. For more information, see Issue #11508: Silent bad codegen when passing and comparing ushort args on GitHub.com. |
| Suggestion | If you encounter issues in the comparison of 16-bit unsigned values in the .NET Framework 4.7, upgrade to the .NET Framework 4.7.1. |
| Scope | Edge |
| Version | 4.7 |
| Type | Runtime |
Runtime
Improved WCF chain trust certificate validation for Net.Tcp certificate authentication
| Details | .NET Framework 4.7.2 improves chain trust certificate validation when using certificate authentication with transport security with WCF. With this improvement, client certificates that are used to authenticate to a server must be configured for client authentication. Similarly server certificates that are for the authenticating a server must be configured for server authentication. With this change, if the root certificate is disabled, the certificate chain validation fails. The same change was also made to .NET Framework 3.5 and later versions via Windows security roll-up. You can find more information here.This change is on by default and can be turned off by a configuration setting. |
| Suggestion |
|
| Scope | Minor |
| Version | 4.7.2 |
| Type | Runtime |
Security
RSACng and DSACng are once again usable in Partial Trust scenarios
| Details | CngLightup (used in several higher-level crypto apis, such as System.Security.Cryptography.Xml.EncryptedXml) and System.Security.Cryptography.RSACng in some cases rely on full trust. These include P/Invokes without asserting SecurityPermissionFlag.UnmanagedCode permissions, and code paths where System.Security.Cryptography.CngKey has permission demands for SecurityPermissionFlag.UnmanagedCode. Starting with the .NET Framework 4.6.2, CngLightup was used to switch to System.Security.Cryptography.RSACng wherever possible. As a result, partial trust apps that successfully used System.Security.Cryptography.Xml.EncryptedXml began to fail and throw SecurityException exceptions.This change adds the required asserts so that all functions using CngLightup have the required permissions. |
| Suggestion | If this change in the .NET Framework 4.6.2 has negatively impacted your partial trust apps, upgrade to the .NET Framework 4.7.1. |
| Scope | Edge |
| Version | 4.6.2 |
| Type | Runtime |
| Affected APIs |
Web Applications
'dataAnnotations:dataTypeAttribute:disableRegEx' app setting is on by default in .NET Framework 4.7.2
| Details | In .NET Framework 4.6.1, an app setting ('dataAnnotations:dataTypeAttribute:disableRegEx') was introduced that allows users to disable the use of regular expressions in data type attributes (such as System.ComponentModel.DataAnnotations.EmailAddressAttribute, System.ComponentModel.DataAnnotations.UrlAttribute, and System.ComponentModel.DataAnnotations.PhoneAttribute). This helps to reduce security vulnerability such as avoiding the possibility of a Denial of Service attack using specific regular expressions.In .NET Framework 4.6.1, this app setting to disable RegEx usage was set to false by default. Starting with .NET Framework 4.7.2, this config switch is set to true by default to further reduce secure vulnerability for web applications that target .NET Framework 4.7.2 and above. |
| Suggestion | If you find that regular expressions in your web application do not work after upgrading to .NET Framework 4.7.2, you can update the value of the 'dataAnnotations:dataTypeAttribute:disableRegEx' setting to false to revert to the previous behavior. |
| Scope | Minor |
| Version | 4.7.2 |
| Type | Runtime |
Windows Communication Foundation (WCF)
WCF AddressHeaderCollection now throws an ArgumentException if an addressHeader element is null
| Details | Starting with the .NET Framework 4.7.1, the AddressHeaderCollection(IEnumerable<AddressHeader>) constructor throws an ArgumentException if one of the elements is null. In the .NET Framework 4.7 and earlier versions, no exception is thrown. |
| Suggestion | If you encounter compatibility issues with this change on the .NET Framework 4.7.1 or a later version, you can opt-out of it by adding the following line to the <runtime> section of the app.config file:: |
| Scope | Minor |
| Version | 4.7.1 |
| Type | Runtime |
| Affected APIs |
WCF MsmqSecureHashAlgorithm default value is now SHA256
| Details | Starting with the .NET Framework 4.7.1, the default message signing algorithm in WCF for Msmq messages is SHA256. In the .NET Framework 4.7 and earlier versions, the default message signing algorithm is SHA1. |
| Suggestion | If you run into compatibility issues with this change on the .NET Framework 4.7.1 or later, you can opt-out the change by adding the following line to the <runtime>section of your app.config file: |
| Scope | Minor |
| Version | 4.7.1 |
| Type | Runtime |
WCF PipeConnection.GetHashAlgorithm now uses SHA256
| Details | Starting with the .NET Framework 4.7.1, Windows Communication Foundation uses a SHA256 hash to generate random names for named pipes. In the .NET Framework 4.7 and earlier versions, it used a SHA1 hash. |
| Suggestion | If you run into compatibility issue with this change on the .NET Framework 4.7.1 or later, you can opt-out it by adding the following line to the <runtime> section of your app.config file: |
| Scope | Minor |
| Version | 4.7.1 |
| Type | Runtime |
Windows Presentation Foundation (WPF)
Chained Popups with StaysOpen=False
| Details | A Popup with StaysOpen=False is supposed to close when you click outside the Popup. When two or more such Popups are chained (i.e. one contains another), there were many problems, including:
|
| Scope | Edge |
| Version | 4.7.1 |
| Type | Runtime |
| Affected APIs |
Crash in Selector when removing an item from a custom INCC collection
| Details | An T:System.InvalidOperationException can occur in the following scenario:
|
| Suggestion | Upgrade to .NET Framework 4.7.1. |
| Scope | Minor |
| Version | 4.7 |
| Type | Runtime |
Keytips behavior improved in WPF
| Details | Keytips behavior has been modified to bring parity with behavior on Microsoft Word and Windows Explorer. By checking whether keytip state is enabled or not in the case of a SystemKey (in particular, Key or F11) being pressed, WPF handles keytip keys appropriately. Keytips now dismiss a menu even when it is opened by mouse. |
| Suggestion | N/A |
| Scope | Edge |
| Version | 4.7.2 |
| Type | Runtime |
Resizing a Grid can hang
| Details | An infinite loop can occur during layout of a T:System.Windows.Controls.Grid under the following circumstances:
|
| Suggestion | Upgrade to .NET Framework 4.7.1. Alternatively, if you don't need the 4.7 allocation algorithm you can use the following configuration setting: |
| Scope | Edge |
| Version | 4.7 |
| Type | Runtime |
- Author: admin
- Category: Category
Grids 4.7.1 Download 5,8/10 1152 votes
Description
What is Grid?
- Grid allows Editors to easily create and maintain Landingpages
- Grid is build of a grid containing Containers and Boxes
- Grid is a CMS-neutral Library and this is the WordPress plugin that implements it
Types of Boxes
Static Boxes –
Free-HTML-Box
- Medialibrary-Box
Video-Box
List-Boxes –
Ordered and filtered Lists of Contents
Number of Items as well as criteria for sorting and filtering are configurable
Configuration Boxes –
Container configuration
Slot configuration
Content-Boxes –
Single Posts of any kind as Teasers
Reuseable Boxes – Mac media players.
All Boxes may be reused across several Landingpages
Easy extendable with new boxes. Have a look at doc.the-grid.ws (english is coming soon).
Arbitrary section
Learning jQuery Fourth Edition Karl Swedberg and Jonathan Chaffer jQuery in Action Bear Bibeault, Yehuda Katz, and Aurelio De Rosa jQuery Succinctly Cody Lindley.
There’s a documentation at doc.the-grid.ws (english is coming soon)
Installation
- Upload
grid-wordpress.zipto the/wp-content/plugins/directory - Extract the Plugin to a
gridFolder - Activate the plugin through the ‘Plugins’ menu in WordPress
- Build landing pages at
Landing Pages,Switch into the Gridand on next screensave changes - Look for more plugins on wordpress.org that can provide grid boxes
FAQ
Generally speaking, yes! But you can easily turn it off in grid settings. And there will be no talking to any external server anymore. Alternatively you can host your own grid async service on your own server. Note that our service will not use or save any personal data at any time. It only uses data to keep the function going.
This happens if grid was installed previously and could not be uninstalled correctly. You have to delete in the wp_options the option_name „grid“. Then try again to active Grid plugin.
Goto Settings->Grid and choose which post types should be able to use Grid. Than goto one of the activated post types and click on Switch into the Grid and on next screen save changes. Now you can drag and drop your landingpage.
Have a look at wordpress.org for plugins that provide new grid boxes or you can create your own plugin and use the grid_load_classes action to add new box classes. You can find a documentation at doc.the-grid.ws
Grid works fine with a varnish configuration and the comet cache plugin. If you use another caching that does not work with grid please contact us on github.com or wordpress.org.
Reviews
Tested a few grid plugins. This is nothing. Sorry!
-->If you are migrating from the .NET Framework 4.7 to 4.7.2, review the following topics for application compatibility issues that may affect your app:
Core
Allow Unicode in URIs that resemble UNC shares
| Details | In System.Uri, constructing a file URI containing both a UNC share name and Unicode characters will no longer result in a URI with invalid internal state. The behavior will change only when all of the following are true:
|
| Suggestion | Applications working with URIs consistently containing Unicode could have conceivably used this behavior to disallow references to UNC shares. Those applications should use IsUnc instead. |
| Scope | Edge |
| Version | 4.7.2 |
| Type | Runtime |
| Affected APIs |
Support special relative URI notation when Unicode is present
| Details | Uri will no longer throw a NullReferenceException when calling TryCreate on certain relative URIs containing Unicode. The simplest reproduction of the NullReferenceException is below, with the two statements being equivalent:To reproduce the NullReferenceException, the following items must be true:
|
| Suggestion | Users depending on this behavior to disallow relative URIs should instead specify UriKind.Absolute when creating a URI. |
| Scope | Edge |
| Version | 4.7.2 |
| Type | Runtime |
| Affected APIs |
JIT
Incorrect code generation when passing and comparing UInt16 values
| Details | Because of changes introduced in the .NET Framework 4.7, in some cases the code generated by the JIT compiler in applications running on the .NET Framework 4.7 incorrectly compares two T:System.UInt16 values. For more information, see Issue #11508: Silent bad codegen when passing and comparing ushort args on GitHub.com. |
| Suggestion | If you encounter issues in the comparison of 16-bit unsigned values in the .NET Framework 4.7, upgrade to the .NET Framework 4.7.1. |
| Scope | Edge |
| Version | 4.7 |
| Type | Runtime |
Runtime
Improved WCF chain trust certificate validation for Net.Tcp certificate authentication
| Details | .NET Framework 4.7.2 improves chain trust certificate validation when using certificate authentication with transport security with WCF. With this improvement, client certificates that are used to authenticate to a server must be configured for client authentication. Similarly server certificates that are for the authenticating a server must be configured for server authentication. With this change, if the root certificate is disabled, the certificate chain validation fails. The same change was also made to .NET Framework 3.5 and later versions via Windows security roll-up. You can find more information here.This change is on by default and can be turned off by a configuration setting. |
| Suggestion |
|
| Scope | Minor |
| Version | 4.7.2 |
| Type | Runtime |
Security
RSACng and DSACng are once again usable in Partial Trust scenarios
| Details | CngLightup (used in several higher-level crypto apis, such as System.Security.Cryptography.Xml.EncryptedXml) and System.Security.Cryptography.RSACng in some cases rely on full trust. These include P/Invokes without asserting SecurityPermissionFlag.UnmanagedCode permissions, and code paths where System.Security.Cryptography.CngKey has permission demands for SecurityPermissionFlag.UnmanagedCode. Starting with the .NET Framework 4.6.2, CngLightup was used to switch to System.Security.Cryptography.RSACng wherever possible. As a result, partial trust apps that successfully used System.Security.Cryptography.Xml.EncryptedXml began to fail and throw SecurityException exceptions.This change adds the required asserts so that all functions using CngLightup have the required permissions. |
| Suggestion | If this change in the .NET Framework 4.6.2 has negatively impacted your partial trust apps, upgrade to the .NET Framework 4.7.1. |
| Scope | Edge |
| Version | 4.6.2 |
| Type | Runtime |
| Affected APIs |
Web Applications
'dataAnnotations:dataTypeAttribute:disableRegEx' app setting is on by default in .NET Framework 4.7.2
| Details | In .NET Framework 4.6.1, an app setting ('dataAnnotations:dataTypeAttribute:disableRegEx') was introduced that allows users to disable the use of regular expressions in data type attributes (such as System.ComponentModel.DataAnnotations.EmailAddressAttribute, System.ComponentModel.DataAnnotations.UrlAttribute, and System.ComponentModel.DataAnnotations.PhoneAttribute). This helps to reduce security vulnerability such as avoiding the possibility of a Denial of Service attack using specific regular expressions.In .NET Framework 4.6.1, this app setting to disable RegEx usage was set to false by default. Starting with .NET Framework 4.7.2, this config switch is set to true by default to further reduce secure vulnerability for web applications that target .NET Framework 4.7.2 and above. |
| Suggestion | If you find that regular expressions in your web application do not work after upgrading to .NET Framework 4.7.2, you can update the value of the 'dataAnnotations:dataTypeAttribute:disableRegEx' setting to false to revert to the previous behavior. |
| Scope | Minor |
| Version | 4.7.2 |
| Type | Runtime |
Windows Communication Foundation (WCF)
WCF AddressHeaderCollection now throws an ArgumentException if an addressHeader element is null
| Details | Starting with the .NET Framework 4.7.1, the AddressHeaderCollection(IEnumerable<AddressHeader>) constructor throws an ArgumentException if one of the elements is null. In the .NET Framework 4.7 and earlier versions, no exception is thrown. |
| Suggestion | If you encounter compatibility issues with this change on the .NET Framework 4.7.1 or a later version, you can opt-out of it by adding the following line to the <runtime> section of the app.config file:: |
| Scope | Minor |
| Version | 4.7.1 |
| Type | Runtime |
| Affected APIs |
WCF MsmqSecureHashAlgorithm default value is now SHA256
| Details | Starting with the .NET Framework 4.7.1, the default message signing algorithm in WCF for Msmq messages is SHA256. In the .NET Framework 4.7 and earlier versions, the default message signing algorithm is SHA1. |
| Suggestion | If you run into compatibility issues with this change on the .NET Framework 4.7.1 or later, you can opt-out the change by adding the following line to the <runtime>section of your app.config file: |
| Scope | Minor |
| Version | 4.7.1 |
| Type | Runtime |
WCF PipeConnection.GetHashAlgorithm now uses SHA256
| Details | Starting with the .NET Framework 4.7.1, Windows Communication Foundation uses a SHA256 hash to generate random names for named pipes. In the .NET Framework 4.7 and earlier versions, it used a SHA1 hash. |
| Suggestion | If you run into compatibility issue with this change on the .NET Framework 4.7.1 or later, you can opt-out it by adding the following line to the <runtime> section of your app.config file: |
| Scope | Minor |
| Version | 4.7.1 |
| Type | Runtime |
Windows Presentation Foundation (WPF)
Chained Popups with StaysOpen=False
| Details | A Popup with StaysOpen=False is supposed to close when you click outside the Popup. When two or more such Popups are chained (i.e. one contains another), there were many problems, including:
|
| Scope | Edge |
| Version | 4.7.1 |
| Type | Runtime |
| Affected APIs |
Crash in Selector when removing an item from a custom INCC collection
| Details | An T:System.InvalidOperationException can occur in the following scenario:
|
| Suggestion | Upgrade to .NET Framework 4.7.1. |
| Scope | Minor |
| Version | 4.7 |
| Type | Runtime |
Keytips behavior improved in WPF
| Details | Keytips behavior has been modified to bring parity with behavior on Microsoft Word and Windows Explorer. By checking whether keytip state is enabled or not in the case of a SystemKey (in particular, Key or F11) being pressed, WPF handles keytip keys appropriately. Keytips now dismiss a menu even when it is opened by mouse. |
| Suggestion | N/A |
| Scope | Edge |
| Version | 4.7.2 |
| Type | Runtime |
Resizing a Grid can hang
| Details | An infinite loop can occur during layout of a T:System.Windows.Controls.Grid under the following circumstances:
|
| Suggestion | Upgrade to .NET Framework 4.7.1. Alternatively, if you don't need the 4.7 allocation algorithm you can use the following configuration setting: |
| Scope | Edge |
| Version | 4.7 |
| Type | Runtime |
Grids 4.7.1 Download В© 2020