content
stringlengths 0
557k
| url
stringlengths 16
1.78k
| timestamp
timestamp[ms] | dump
stringlengths 9
15
| segment
stringlengths 13
17
| image_urls
stringlengths 2
55.5k
| netloc
stringlengths 7
77
|
|---|---|---|---|---|---|---|
Moving a user's audio conferencing provider to Microsoft
To use Audio Conferencing in Office 365 with Skype for Business and Microsoft Teams, users in your organization need to have an Audio Conferencing license assigned to them and their audio conferencing provider must be set to Microsoft. See Try or purchase Audio Conferencing in Office 365 to get more information on licensing and how much it costs.
To move a user's audio conferencing provider to Microsoft
If an Audio Conferencing license is assigned to a user who doesn't have an audio conferencing provider, the user's provider will be automatically set to Microsoft and you don't have to do anything else. If the user already had an audio conferencing provider, you must change the user's provider to Microsoft after assigning them an Audio Conferencing license.
To set Microsoft as the audio conferencing provider for a user that has an Audio Conferencing license assigned but is using another audio conferencing provider, do this:
Sign in to Office 365 with your work or school account.
Go to the Office 365 admin center > Skype for Business.
In the Skype for Business admin center, go to Audio conferencing.
If you see a banner notifying you that there are users who have an Audio Conferencing license assigned but don't have Microsoft set as their audio conferencing provider yet, click Click here to move them. If you don't see the banner, in the Skype for Business admin center click Users, and then select the Users ready to be moved to Audio Conferencing filter.
Select the users you want to move, and then in the Action pane, click Edit.
Select Microsoft in the Provider name list.
Note
When the audio conferencing provider of a user is changed to Microsoft, the audio conferencing information of the user will change. If you need to keep this information, please record it somewhere before changing the provider of any of the users.
Click Save.
What else should I know?
If you select the user in the list, you can view the default audio conferencing information of the user but you won't be able to see the audio conferencing PIN. You can reset the audio conferencing PIN of a user by clicking Reset.
If you want to change audio conferencing settings for a user, you can select the user from the list and then click Edit and make your changes on the Properties page.
Related topics
Set up Audio Conferencing for Skype for Business and Microsoft Teams | https://docs.microsoft.com/en-us/SkypeForBusiness/audio-conferencing-in-office-365/moving-a-user-s-audio-conferencing-provider-to-microsoft | 2018-03-17T14:44:25 | CC-MAIN-2018-13 | 1521257645177.12 | [] | docs.microsoft.com |
Configure mobile list items navigation Determine whether a tapping an item in a list opens the record or the activity stream using a system property. Before you beginRole required: admin Procedure Navigate to System Properties > Mobile UI properties. From the Destination when navigating to a record from a list property [glide.ui.m.default_record_navigation], select Activity Stream or Form. OptionDescription Activity Stream Opens the list item in the activity stream view. Form Opens the list item in the form view. | https://docs.servicenow.com/bundle/kingston-platform-user-interface/page/administer/tablet-mobile-ui/task/configure-mobile-list-form.html | 2018-03-17T14:41:59 | CC-MAIN-2018-13 | 1521257645177.12 | [] | docs.servicenow.com |
Design RESTful Services
ServiceStack encourages a message-based design so each Service should have its own distinct message (aka Request DTO) where it’s able to use explicit properties to define what each Service accepts. Something to keep in mind is how you define and design your Services in ServiceStack are de-coupled in how you expose them which can be exposed under any custom Route.
Use a logical / hierarchical Url structure
We recommend adopting a logical hierarchically structured URL that represents the identifier of a resource, i.e. the parent path categorizes your resource and gives it meaningful context. So if you needed to design an API for System that maintained Events and their Reviews it could adopt the following url structure:
/events # all events /events/1 # event #1 /events/1/reviews # event #1 reviews
Where each of the above resource identifiers can be invoked using any HTTP Verb which represents the action to take on them, e.g:
GET /events # View all Events POST /events # Create a new Event PUT /events/{Id} # Update an existing Event DELETE /events/{Id} # Delete an existing Event
Implementing RESTful Routes
For their implementation ServiceStack encourages a message-based design that groups all related operations based on Response type and Call Context. For an Events and Reviews system it could look something like:
[Route("/events", "GET")] [Route("/events/category/{Category}", "GET")] // Optional GET example public class SearchEvents : IReturn<List<Event>> { //resultset filter examples, e.g. ?Category=Tech&Query=servicestack public string Category { get; set; } public string Query { get; set; } } [Route("/events", "POST")] public class CreateEvent : IReturn<Event> { public string Name { get; set; } public DateTime StartDate { get; set; } } [Route("/events/{Id}", "GET")] [Route("/events/code/{EventCode}", "GET")] // Alternative Id public class GetEvent : IReturn<Event> { public int Id { get; set; } public string EventCode { get; set; } // Alternative to fetch Events } [Route("/events/{Id}", "PUT")] public class UpdateEvent : IReturnVoid { public int Id { get; set; } public string Name { get; set; } public DateTime StartDate { get; set; } }
Event Reviews would follow a similar pattern:
[Route("/events/{EventId}/reviews", "GET")] public class GetEventReviews : IReturn<List<EventReview>> { public int EventId { get; set; } } [Route("/events/{EventId}/reviews/{Id}", "GET")] public class GetEventReview : IReturn<EventReview> { public int EventId { get; set; } public int Id { get; set; } } [Route("/events/{EventId}/reviews", "POST")] public class CreateEventReview : IReturn<EventReview> { public int EventId { get; set; } public string Comments { get; set; } }
The above REST Service examples returns naked Types and collections which ServiceStack has a great story for, however our personal preference is to design more coarse-grained and versionable Message-based APIs where we’d use an explicit Response DTO for each Service, e.g:
[Route("/events/{EventId}/reviews", "GET")] public class GetEventReviews : IReturn<GetEventReviewsResponse> { public int EventId { get; set; } } public class GetEventReviewsResponse { public List<Event> Results { get; set; } } [Route("/events/{EventId}/reviews/{Id}", "GET")] public class GetEventReview : IReturn<GetEventReviewResponse> { public int EventId { get; set; } public int Id { get; set; } } public class GetEventReviewResponse { public EventReview Result { get; set; } public ResponseStatus ResponseStatus { get; set; } // inject structured errors if any } [Route("/events/{EventId}/reviews", "POST")] public class CreateEventReview : IReturn<CreateEventReviewResponse> { public int EventId { get; set; } public string Comments { get; set; } } public class CreateEventReviewResponse { public EventReview Result { get; set; } public ResponseStatus ResponseStatus { get; set; } }
Notes
The implementation of each Services then becomes straight-forward based on these messages, which (depending on code-base size) we’d recommend organizing in 2 EventsService and EventReviewsService classes.
Although
UpdateEvent and
CreateEvent are seperate Services here, if the use-case permits they can instead be handled by a single idempotent
StoreEvent Service.
Physical Project Structure
Ideally the root-level AppHost project should be kept lightweight and implementation-free. Although for small projects or prototypes with only a few services it’s ok for everything to be in a single project and to simply grow your architecture when and as needed.
For medium-to-large projects we recommend the physical structure below which for the purposes of this example we’ll assume our Application is called Events.
The order of the projects also show its dependencies, e.g. the top-level
Events project references all sub projects whilst the last
Events.ServiceModel project references none:
/Events AppHost.cs // ServiceStack Web or Self Host Project /Events.ServiceInterface // Service implementations (akin to MVC Controllers) EventsService.cs EventsReviewsService.cs /Events.Logic // For large projects: extract C# logic, data models, etc IGoogleCalendarGateway // E.g of a external dependency this project could use /Events.ServiceModel // Service Request/Response DTOs and DTO types Events.cs // SearchEvents, CreateEvent, GetEvent DTOs EventReviews.cs // GetEventReviews, CreateEventReview Types/ Event.cs // Event type EventReview.cs // EventReview type
With the
Events.
More Info
- This recommended project structure is embedded in all ServiceStackVS VS.NET Templates.
- The Simple Customer REST Example is a small self-contained, real-world example of creating a simple REST Service utilizing an RDBMS. | http://docs.servicestack.net/design-rest-services | 2018-03-17T14:10:18 | CC-MAIN-2018-13 | 1521257645177.12 | [] | docs.servicestack.net |
Jekyll traverses your site looking for files to process. Any files with YAML front matter are subject to processing. For each of these files, Jekyll makes a variety of data available via the Liquid templating system. The following is a reference of the available data.
ProTip™: Use Custom Front Matter
Any custom front matter that you specify will be available under
page. For example, if you specify
custom_css: truein a page’s front matter, that value will be available as
page.custom_css.
If you specify front matter in a layout, access that via
layout. For example, if you specify
class: full_pagein a layout’s front matter, that value will be available as
layout.classin the layout and its parents.
Paginator variable availability
These are only available in index files, however they can be located in a subdirectory, such as
/blog/index.html.
© 2008–2018 Tom Preston-Werner and Jekyll contributors
Licensed under the MIT license. | http://docs.w3cub.com/jekyll/variables/ | 2018-03-17T14:40:26 | CC-MAIN-2018-13 | 1521257645177.12 | [] | docs.w3cub.com |
AWS services or capabilities described in AWS Documentation may vary by region/location. Click Getting Started with Amazon AWS to see specific differences applicable to the China (Beijing) Region.
Container for the parameters to the DefineSuggester operation. Configures a suggester for a domain. A suggester enables you to display possible matches before users finish typing their queries. When you configure a suggester, you must specify the name of the text field you want to search for possible matches and a unique name for the suggester. For more information, see Getting Search Suggestions in the Amazon CloudSearch Developer Guide.
Namespace: Amazon.CloudSearch.Model
Assembly: AWSSDK.CloudSearch.dll
Version: 3.x.y.z
The DefineSugges | https://docs.aws.amazon.com/sdkfornet/v3/apidocs/items/CloudSearch/TDefineSuggesterRequest.html | 2018-03-17T14:56:27 | CC-MAIN-2018-13 | 1521257645177.12 | [] | docs.aws.amazon.com |
will be available in the second drop-down box. The list of audit files may be searched by entering text into the option or scrolling the list of available names. Hovering over a name will enable an information icon which, when hovered over, will display the name, description, and type of the audit file. Selecting the check mark to the right.
The plugin family view:
The plugin view (accessed by clicking on the Plugin Family name):
Caution: The Denial of Service plugin family contains plugins that could cause outages on network hosts if the Safe Checks option is not enabled, but it also contains useful checks that will not cause any harm. The Denial of Service plugin family can be used in conjunction with Safe Checks to ensure that any potentially dangerous plugins are not run. However, Tenable™ does not recommend enabling the Denial of Service plugin family in production environments.
For more information, see Configure Plugin Options. | https://docs.tenable.com/sccv/5_6/Content/CustomScanPolicyOptions.htm | 2018-03-17T14:44:26 | CC-MAIN-2018-13 | 1521257645177.12 | [] | docs.tenable.com |
Aldrich, Winthrop W. (1885-1974) us ambassador
Скачать
345.48 Kb.
Название
Aldrich, Winthrop W. (1885-1974) us ambassador
страница
1/8
Дата конвертации
29.10.2012
Размер
345.48 Kb.
Тип
Документы
1
2
3
4
5
6
7
8
John Foster Dulles Oral History Collection
Author Index
Anderson, Dillon (1906-1974) - Assistant to the President for National Security Affairs.
The NSC, its function and processes; the national budget; "massive retaliation"; the decision-making process; relationships; Transcript No. 9.
Reel: 1
Armstrong, W. Park, Jr. (1907-1985) - Foreign Service officer.
JFD's work in the Acheson administration (the Japanese Peace Treaty); staff meeting and briefing procedures in JFD's administration; discussion of various crises in the mid-1950s; Soviet and Communist Chinese leaders; the Suez crises; intelligence operations in the State Department and the CIA; political appointments in the State Department; the administration of the Department; JFD's relations with the Department's personnel; McCarthyism and security cases; JFD's interest in military affairs; policy-making aspects of intelligence; JFD's interest in economic affairs; Spain. [RDC]; 45 pages. 1965. Open. May be copied with permission of heirs; Transcript No. 10.
Reel: 1
Asbjornson, Mildred J. - Secretary in the office of the Secretary of State.
JFD's office staff in the Department of State; his working habits in the office, at home, and on trips; office routines and procedures. [PAC]; 34 pages. 1965. Open; Transcript No. 11.
Reel: 1
Babcock, C. Stanton (1904-1979) - Military Adviser on the Japanese Peace Treaty.
The Japanese Treaty and mutual security pacts; JFD's relations with the Japanese and British; personal relations with JFD on official and social levels. [PAC]; 26 pages. 1964; Oen; Transcript No. 12.
Reel: 1; Transcript No. 13.
Reel: 1
Barnes, Roswell P. (1901- ) - Clergyman.
Personal associations with JFD, starting in the late 1920s; the Oxford Conference of the Universal Christian Council for Life and Work (1937); detailed discussion of JFD's association with the Federal Council of Churches, especially as chairman of the Commission on a Just and Durable Peace; JFD's working habits; his political association in the 1940s; his participation in various church conferences; his views on Christian principles, especially as related to world affairs and international relations; the Dulles homes; JFD's family heritage, religious and diplomatic; his relations with church leaders. [PAC]; 42 pages. 1964. Permission required to quote or cite during donor's lifetime; Transcript No. 14.
Reel: 1
Beal, John R. - Journalist and author.
The Japanese Peace Treaty; JFD's relations with the press; the "brinkmanship" article in Life magazine; the writing of John Foster Dulles (1888-1959). [RDC]; 30 pages. 1965. Permission required to quote or cite during donor's lifetime; Transcript No. 15.
Reel: 1. [GCS]; 23 pages. 1964. Open; Transcript No. 16.
Reel: 1
Becker, Loftus E. (1911-1977) - Legal Adviser, State Department.
Personal and official relations with JFD; the Girard case; the office and function of the Legal Adviser; the Interhandel case; JFD's working habits, his use of words, working relations with State Department personnel; his relations with world leaders; Suez; JFD's relations with the President; his relations with the press. [PAC]; 38 pages. 1964. Open; Transcript No. 17.
Reel: 1 retaliation" and "brinkmanship"; the administration of the State Department. [RDC]; 34 pages. 1964. Open; Transcript No. 18.
Reel: 1
Bennett, John Coleman (1902- ) - Theologian.
JFD's
JFD's involvement with religious organizations concerned with the role of the church in international affairs during the late 1930s and early 1940s; his relations with church leaders; his views on world affairs and his interest in politics in the 1940s; changes in his outlook and viewpoints in the 1950s. [RDC]; 38 pages. 1965. Open; Transcript No. 19.
Reel: 1
Benson, Richard K. - Airplane pilot.
Anecdotes about JFD on plane trips; Duck Island. [PAC]; 34 pages; 1965. Open; Transcript No. 20.
Reel: 1; Transcript No. 21.
Reel: 1
Berendsen, Sir Carl (1890-1980) - New Zealand Ambassador to the US.
The San Francisco Conference of 1945; Far Eastern relations (the Japanese Peace Treaty, ANZUS); Suez; "brinkmanship"; comparison of the Acheson and Dulles administrations. [SD]; 25 pages. 1964. Open; Transcript No. 22.
Reel: 1
Bissell, Richard M., Jr. (1909-1994) - CIA official.
Viet Nam (US intervention after the fall of Dien Bien Phu); SEATO; U-2, detailed discussion of the program's development and operation; Suez; official relations between Foster and Allen Dulles and between the CIA and the State Department; the McCarthy era; Guatemala; Cuba; CIA participation in NSC meetings; relations with the USSR. [RDC]; 57 pages. 1966. Open; Transcript No. 23.
Reel: 1
Black, Eugene (1898-1992) - Executive Director of the International Bank for Reconstruction and Development.
Detailed account of the Aswan Dam negotiations. [RDC]; 31 pages. 1964. Open; Transcript No. 24.
Reel: 1
Bohlen, Charles E. (1904-1974) - Diplomat.
Postwar; Transcript No. 25.
Reel: 1
Bowie, Robert R. (1909- ) - Assistant Secretary of State for Policy Planning.. Transcript No. 26.
Reel: 1
Brandt, Willy (1913-1992) - Governing Mayor of West Berlin.
American-German relations; JFD's views on the East-West confrontation in Europe; the Berlin crisis and the Khrushchev ultimatum; the "agent" theory; the Suez-Hungarian crises; the role of Eleanor Dulles in US-Berlin affairs. [GAC]; 19 pages. 1964. Open; Transcript No. 27.
Reel: 1; Transcript No. 28.
Reel: 2; Transcript No. 29.
Reel: 2; Transcript No. 30.
Reel: 2
Brundage, Percival F. (1892-1979) - Director, Bureau of the Budget.
Wall Street connections with JFD in the 1920s; the Council on Foreign Relations; JFD's interest in finance, administration, international affairs, etc., in the 1920s and 1930s; relations between the State Department and the Bureau of the Budget; JFD in Cabinet and NSC meetings. [RDC}; 30 pages. 1966. Open; Transcript No. 31.
Reel: 2
Buchanan, Wiley T. Jr. (1914- ) - Chief of Protocol.
JFD's senatorial campaign; Luxembourg; the Coal and Steel Community; JFD as a negotiator; his knowledge of foreign countries; staff meetings; the Hungarian revolt; protocol, its importance to JFD; JFD's funeral; security problems with visiting dignitaries and arrangements for police protection. [PAC]; 43 pages. 1966. Permission required to quote or cite during donor's lifetime; Transcript No. 32.
Reel: 2
Bunker, Ellsworth (1894-1984) - US Ambassador to Italy and India during Eisenhower administration.
JFD's family in New York during 1930s; JFD's trip to Europe in 1953; the Marshall Plan; Italy, McCarthyism; India (foreign aid, Pakistan, Red China, nonalignment); policy of containment. [PAC]; 20 pages. 1966. Open; Transcript No. 33.
Reel: 2 discussion of NATO, its major problems and JFD's participation in its meetings; JFD's final illness. [PAC]; 48 pages. 1965. Open; Transcript No. 34.
Reel: 2:
Publications List for Howard E. Aldrich
«Возврата нет», СССР (1974), режиссер Алексей Салтыков
Демин В. П. Подборка рецензий из журнала «Спутник кинозрителя». 1974. № С. 1-21
Minutes of a meeting of the research committee held in room w1, winthrop tower on 5 december 1996
Інтерпретація еволюції спеціальної освіти: зародження, становлення, розвиток
Тіге Таврійської губернії (1885), с. Вармс Херсонської губернії (1887) [3, 182-183]. У другій половині XIX ст відкрили й перші спеціальні...
Бібліографія праць (1974-2012) Наталі Яковенко
Доповнення до «Каталогу колекції документів Київської археографічної комісії» // Архіви України. – 1974. – № – C. 50–63. (У співавторстві...
Указатель статей, помещенных в "офтальмологическом журнале" за 1974 год
Авербух С. Л. Офтальмоскопическая картина макулярной области у больных с врожденной ахромазией (5, 359-361, 1974)
Programme 10: 00 Registration 10: 30 Welcome and introduction to conference Megan Aldrich, Sotheby’s Institute of Art Morning Session: Historical Perspectivesоролев, борис данилович ыпуск 12 (544) москва «молодая гвардия», 1974 Издательство «Молодая гвардия», 1974 г
Тобольска, Дмитрий Иванович Менделеев не выдержал, не смог усидеть в помещении. Он облачился в просторный пылевик, надвинул на лоб...
Вступление
В настоящее время имена этих ученых хорошо известны. В США джон фон Нейман (1903-1957), Джон Мочли (1907-1980), Преспер Эккерт (ро | http://lib.convdocs.org/docs/index-6406.html | 2019-10-14T09:07:26 | CC-MAIN-2019-43 | 1570986649841.6 | [] | lib.convdocs.org |
Table of Contents
This DRAFT document defines how to make a theme of emoticons typically used in instant messaging applications
The basic scheme is very simple. The theme consists in one sub directory which contains all the pictures and an XML file that gives each picture ASCII symbols. A .directory file might be used.
Files involved in this specification are located according to the "desktop base directory specification" which can be found on.
All the files of the theme must be placed in a sub directory of
$XDG_DATA_DIRS/emoticons/
The name of the directory must be equal to the name of the theme.
That directory must contains a file called
emoticons.xml
the format of that file is described below.
The theme directory may also contain a .directory file which contains translations of the theme name and/or an icon for that theme.
Emoticon map files must be well-formed XML files. Implementations should ignore unknown tag or unknown attributes.
- <messaging-emoticon-map> [version="0.1"]
The root element is <messaging-emoticon-map> all other elements are contained by it.
- <emoticon file="...">
This element represents one emoticon. The attribute file is the name of the image file which must be in the same directory. The extension may be omitted. In that case, the implementation look in that directory for a file with the same name in a supported format.
There are no order for emoticon in the map. But the first icon in the map is generally used to identify the theme graphically. By convention the this SHOULD be :-)
- <string>
This element may only appear below <emoticon>. It represents the ASCII string which will be matched in the text, and replaced by the image specified by the file attribute of the emoticon.
There may be several strings per emoticon.
There is no order for string inside an emoticon. But the first one SHOULD be the default one, and will be taken if there is a GUI selector.
<messaging-emoticon-map> <emoticon file="smile.png"> <string>:-)</string> <string>:)</string> <string>:o)</string> </emoticon> <emoticon file="wink.png"> <string>;-)</string> <string>;)</string> </emoticon> <emoticon file="unhappy.png"> <string>:-(</string> <string>:(</string> </emoticon> </messaging-emoticon-map> | https://docs.kde.org/stable5/en/kdenetwork/kopete/kopete-emoticons.html | 2019-10-14T09:55:02 | CC-MAIN-2019-43 | 1570986649841.6 | [array(['/stable5/en/kdoctools5-common/top-kde.jpg', None], dtype=object)] | docs.kde.org |
Desktop Sharing
Program copyright 2002 Tim Jansen
(tim tjansen.de)
Contributors:
Ian Reinhart Geiser
(geiseri kde.org)
Documentation Copyright (c) 2003 Brad Hards
(bradh frogmouth.net)
This documentation is licensed under the terms of the GNU Free Documentation License.
This program is licensed under the terms of the GNU General Public License. | https://docs.kde.org/trunk5/en/kdenetwork/krfb/credits.html | 2019-10-14T09:51:51 | CC-MAIN-2019-43 | 1570986649841.6 | [array(['/trunk5/en/kdoctools5-common/top-kde.jpg', None], dtype=object)] | docs.kde.org |
Cloud-Init is an open-source cloud initialization program, which initializes specified customized configurations, such as the host name, key, and user data, of a newly created BMS.
Currently, all standard images (in Standard_xxx format) support Cloud-Init.
Using Cloud-Init to initialize BMS configurations will influence your BMS and IMS services.
To ensure that BMSs created using private images support customized configurations, you must install Cloud-Init or Cloudbase-Init when creating private images.
After Cloud-Init or Cloudbase-Init is installed in an image, Cloud-Init or Cloudbase-Init automatically configures initial BMS attributes when the BMS is created. For details about how to install Cloud-Init and Cloudbase-Init, see Bare Metal Server Private Image Creation Guide.
If you use the default security group rules in the outbound direction, the preceding requirements are met, and the metadata service can be accessed. The default outbound security group rule is as follows: | https://docs.otc.t-systems.com/en-us/usermanual/bms/en-us_topic_0083745263.html | 2019-10-14T09:20:54 | CC-MAIN-2019-43 | 1570986649841.6 | [] | docs.otc.t-systems.com |
Last updated 01/02/2018
Objective
In your OVH Control Panel, you can choose from many Private Cloud settings options.
This guide will show you the different options you can use.
Requirements
- You must be logged in to your OVH Control Panel. Go to the
Dedicatedsection, then select
Private Cloud.
- You must have a Private Cloud product.
Instructions
General tab
Once you have clicked
Dedicated, and opened the
Private Cloud section of your OVH Control Panel, you will see a general overview of your Private Cloud:
At the top of the page,
(1 on the image), you will find the name and description of your Private Cloud. Feel free to customise it – this will be very useful if you have several infrastructures.
On the right,
(2 on the image), you will see several buttons:
- Order an IP block, which will take you to the
IPtab
- Order a licence (cPanel, Plesk, etc.), which will take you to the
Licencestab
- Switch all resources to a fixed monthly rate (if you already pay monthly, this will not be displayed)
- Cancel your service: you will be sent an email asking you to confirm your request
General information
In the first section, you will find general information about your Private Cloud.
- Your Private Cloud version
- Its OVH reference number
- The datacentre, and more precisely, the zone in which your infrastructure is located
- The security access to your infrastructure (
Openor
Restricted) with the restrictions per source IP
- The guaranteed bandwidth feature will be available soon
- The number of virtual datacentres in your infrastructure
- The number of IP blocks
Options
You will then see the status of the NSX and vRops options.
In this example, the NSX and vRops options are enabled, and you can disable them if you do not or no longer need them.
To enable one of these options, simply click the corresponding button.
If you click
Details on this option, you will find guides for each of the options.
Datacentres
In this tab you will find a short summary of the virtual datacentres in your Private Cloud solution:
See below for all information about the datacentres.
You can add another datacentre from this page at no extra cost.
Users
All users who can log in to vSphere can be found in this section:
You can create a user by clicking on the
Create user button on the right.
For each user, you will find this information:
- ID
- Telephone number (optional)
- Validation token
- Status
Permissions in this section are set for the different users. The first column (IP) can be used to give users permission to manage the
OVH network tab and manage the
Users tab itself, whilst the second column (Failover IP) gives users permission to manage failover IPs.
If you click on the cogwheel icon to the right of the table, several options will appear:
- Modify entries in this table
- View and modify this user’s permissions by datacentre
- Change the user password
- Delete this user
We can look at the modification of permissions per datacentre in more detail:
vSphere access– this deals with the vSphere user’s overall permissions:
Add resources– this button enables you to grant or withhold the right to add additional resources via the OVH plugin in the vSphere client.
Access to the VM Network- for managing permissions over the public network section (called
VM Networkin the vSphere interface):
Access to the V(X)LAN- for managing rights on the private network section (VXLANs for the Dedicated Cloud range or VLANs for the SDDC range):
Since the permissions are being rewritten, the information here may change.
Security
You can modify the access settings for your vCenter in this tab:
You can configure the elements above and in the table using the cogwheel icons on the right. You can configure:
- A limit for login sessions
- The number of concurrent connections authorised
- The access settings, restricted or unrestricted, with an authorisation per source IP. The IPs will be in the table
The logout policy involves logging out the first or last user logged in. In this example, if 50 users are logged in, and a 51st person logs in, the first user to have logged in will be logged out. If you set the access mode to restricted and do not enter an IP, nobody will be able to log in to the vSphere client. However, the virtual machines will still be accessible.
Operations
In this last tab, you will find active operations on your infrastructure.
You can check if an operation has encountered a problem, if there is any scheduled maintenance, etc.
If you are unable to access the vSphere client, there could be an ongoing maintenance operation, and you can use this tab to check if this is the case.
Datacentre Preview
With Private Cloud solutions, your services may be based in several datacentres. By clicking on your Private Cloud, you can see them:
You can customise the name of your datacentre by clicking on the pencil icon. You can also add a customised description. You will find the main information on your datacentre, its range (SDDC or DC), the number of hosts and data stores. You can use several datacentres in one Private Cloud solution, if your product is part of the Dedicated Cloud and Software Defined Datacentre ranges.
Hosts
Here, you can view your datacentre hosts:
In this section, you will find:
- The host names
- Their profile (M, L, L+, etc.)
- Their billing method: if you are billed on an hourly basis, you can switch to monthly billing
- The host status
- The number of hours used (only for an hourly resource)
On the right of this image, you can order a new host, to be billed on a monthly basis.
Data stores
The data stores table is similar to that of the hosts:
In this section, you will find:
- The data store names
- Information about their size
- The billing method
- The data store status
- The number of hours used (only for an hourly resource)
On the right of this image, you can order a new data store, to be billed on a monthly basis.
Backup
The backup tab allows you to enable the
Veeam backup solution by clicking on the
Enable backup button:
For more information on this option, see this guide.
Windows Licence
The
Windows Licence tab allows you to activate Windows SPLA licences on your datacentre by clicking the button on the right:
You can find the pricing page here.
Go further
Join our community of users on. | https://docs.ovh.com/sg/en/private-cloud/control-panel-ovh-private-cloud/ | 2019-10-14T10:01:53 | CC-MAIN-2019-43 | 1570986649841.6 | [array(['https://docs.ovh.com/asia/en/private-cloud/control-panel-ovh-private-cloud/images/manager_general.png',
'General information'], dtype=object)
array(['https://docs.ovh.com/asia/en/private-cloud/control-panel-ovh-private-cloud/images/general_information.png',
'General information'], dtype=object)
array(['https://docs.ovh.com/asia/en/private-cloud/control-panel-ovh-private-cloud/images/options.png',
'Options'], dtype=object)
array(['https://docs.ovh.com/asia/en/private-cloud/control-panel-ovh-private-cloud/images/options_activation.png',
'Enabling options'], dtype=object)
array(['https://docs.ovh.com/asia/en/private-cloud/control-panel-ovh-private-cloud/images/datacenter.png',
'Datacentre'], dtype=object)
array(['https://docs.ovh.com/asia/en/private-cloud/control-panel-ovh-private-cloud/images/users.png',
'Users'], dtype=object)
array(['https://docs.ovh.com/asia/en/private-cloud/control-panel-ovh-private-cloud/images/rights_user_datacenters.png',
'User permissions per datacentre'], dtype=object)
array(['https://docs.ovh.com/asia/en/private-cloud/control-panel-ovh-private-cloud/images/security.png',
'Security settings'], dtype=object)
array(['https://docs.ovh.com/asia/en/private-cloud/control-panel-ovh-private-cloud/images/operations.png',
'Operations'], dtype=object)
array(['https://docs.ovh.com/asia/en/private-cloud/control-panel-ovh-private-cloud/images/datacenter_view.png',
'Datacentre Preview'], dtype=object)
array(['https://docs.ovh.com/asia/en/private-cloud/control-panel-ovh-private-cloud/images/hosts.png',
'Hosts'], dtype=object)
array(['https://docs.ovh.com/asia/en/private-cloud/control-panel-ovh-private-cloud/images/datastores.png',
'Data stores'], dtype=object)
array(['https://docs.ovh.com/asia/en/private-cloud/control-panel-ovh-private-cloud/images/backup.png',
'Backup'], dtype=object)
array(['https://docs.ovh.com/asia/en/private-cloud/control-panel-ovh-private-cloud/images/windows_licence.png',
'Windows SPLA Licence'], dtype=object) ] | docs.ovh.com |
Non Integer Values shown
One of the common issues when dealing with rrdtool is the following example:
- Assume you're reading integer values from your target system, e.g. the number of mails seen by your spam filter
- you're feeding them to rrdtool while using the standard 300 sec polling interval
- when creating graphs, you notice that there are no integers shown
Why's this?
Please take into account, that rrdtool automatically normalizes your data to an exact 300 sec interval. Even when polling every 300 sec. you will notice that measuremeants are off by some seconds from time to time.
Now let's turn back to the spam filter example. Let's assume that you receive exactly 2 mails each second. Sometimes the measurement interval spans exactly 300 sec yielding a mail count of 600. But in case the measurement interval spans only 299 seconds, the mail count will be only 598. And if the timespan is 301 sconds, the mail count should be 602.
RRDTool accounts for this and will “adjust” the value for a timespan of 300 sec. To be more specific, it even adjusts the polling intervals at exact 300 sec boundaries. In my personal tech tongue I call this “time normalization” of rrdtool.
The attached image (courtesy engeishi) shows how it works: | https://docs.cacti.net/manual:100:8_rrdtool.02a_non_integers | 2020-07-02T19:39:50 | CC-MAIN-2020-29 | 1593655879738.16 | [] | docs.cacti.net |
X.509 for TLS
Couchbase Server uses X.509 certificates to encrypt Cross Data Center Replication (XDCR) and other client-server communications.
Couchbase Server Enterprise Edition supports X.509 certificates, for Transport Layer Security (TLS).
With X.509 certificates, Couchbase Server can strongly encrypt Cross Data Center Replication and other client-server communications.
Full administrators can manage certificates, using the Couchbase CLI tools (as described in ssl-manage) and REST API (as described in Security API).
CA-based certificates can be managed and rotated without client downtime.
The following overview of Couchbase certificate-management assumes the reader’s prior knowledge of TLS/SSL, PKI certificates including X.509 certificates, and Certificate Authorities (CAs).
When to Use X.509 Certificates
An X.509 certificate does more than just distribute the public key: it is signed by a trusted (internal or third-party) CA, and thereby verifies the identity of the server, assuring clients that their information is not being sent to a rogue server.
Therefore, scenarios potentially requiring the use of X.509 certificates include:
In production, where clients have to go through the internet.
When transferring sensitive data on the wire between application and Couchbase Server, or between data centers (XDCR).
When mandated by compliance regulations.
CA Hierarchies Supported by Couchbase
Couchbase customers can associate Couchbase Server with their CA hierarchies. The CA at the top of a hierarchy is called the root authority, or root CA. Two types of CA hierarchy are supported by Couchbase: single-tier and n-tier.
- Single-Tier Hierarchy
In its simplest form, the single-tier hierarchy starts with a root CA.
In the case represented by the figure immediately above, the root CA is also the issuing CA. All certificates immediately below the root certificate inherit its trustworthiness, and can be used to secure systems.
This is the simplest form of CA hierarchy: however, most enterprises use the more complex, N-tier CA hierarchy, as described next.
- N-Tier Hierarchy
In many production deployments, a hierarchy has multiple CAs.
In a multi-tier hierarchy, the root CA issues certificates to the intermediate CAs, which in turn generate intermediate certificates: these are used to sign client certificates, such as a cluster certificate:
Trusted root CA > Intermediate CA > Cluster certificate
Trusted root CA > Intermediate CA 1 > Intermediate CA 2.... > Intermediate CA n > Cluster certificate
When you need to regenerate the intermediate certificate, ensure that the chain can be verified up to the root CA.
All intermediate certificates should be installed on your server: otherwise, some clients will assume that the connection is not secure. This results in 'untrusted' warnings like the following:
To avoid such warnings, a server should always provide a complete trust chain. The trust chain contains your certificate, concatenated with all intermediate certificates.
Configuring X.509
This section explains how to configure X.509 certificates for TLS in Couchbase Server. Note that choosing a root CA, the CA hierarchy, and obtaining a certificate from that CA chain to set up a Couchbase cluster are not within the scope of this document.
X.509 Certificate Requirements and Best Practices
Here are the basic requirements for using X.509 certificates in Couchbase:
The certificate must be in available in the
.pemformat.
The certificate must be an RSA key certificate.
The current system time must fall between the times set in the certificate’s properties
valid fromand
valid to.
Common name: This can be a certificate with a
nodename(preferable), IP address, URI (), or URI with a subject alternative name (SAN) certificate (
example.comand
example.net).
The node certificate must be designated for server authentication, by setting the optional field of the certificate’s property
enhanced key usageto
Server Authentication.
Recommended, best practices include:
To avoid man-in-the-middle attacks, do not use wildcards with IP addresses in the certificate common name.
Use an RSA key-length of 2048 bits or higher. (As computing capabilities increase, longer RSA keys provide increased security.)
The certificate chain must be valid from the node certificate up to the root certificate: this.
HTTPS URL integrity check
If you deploy a certificate on a multi-homed host, however, it may be practical to allow the certificate to be used with any of the multi-homed host names. In this case, it is necessary to define a certificate with multiple, alternative identities, and this is only possible using the
subjectAltNamecertificate-extension.
The HTTPS protocol also supports, in host names, the wildcard character *.
For example, you can define the
subjectAltName as follows:..
Per Node Certificate
The Couchbase cluster certificate is used to sign per-node Couchbase certificates, each containing the following:
The node private key, which is named
pkey.keyas shown in the configuration steps below.
The node public key certificate file, which is named
pkey.pemas shown in the configuration steps below.
The certificate chain file based on the supported CA hierarchy, This file is named
chain.pem, or /opt/couchbase/var/lib/couchbase/inbox/) on Linux.
-
The following steps configure X.509 certificates on Ubuntu 16: a root certificate is created with a single intermediate certificate and a single node certificate; and a chain certificate is created from the intermediate and node certificates. The chain certificate and node private key are then made active for the current Couchbase Server-node.
Proceed as follows, using the
sudo command where appropriate.
Create environment variables for the naming of a directory-structure, within which will reside the certificates you create for root, intermediate, and node.
export TOPDIR=SSLCA export ROOT_DIR=rootdir export NODE_DIR=nodedir export INT_DIR=intdir
Note that in cases where multiple intermediate and/or node certificates are to be included in the certificate-chain, multiple intermediate and/or directories are required — one for each intermediate or node certificate.
Create environment variables for each of the certificate-files to be created.
export ROOT_CA=ca export INTERMEDIATE=int export NODE=pkey export CHAIN=chain
Note that in cases where multiple intermediate and/or node certificates are to be included in the certificate-chain, additional environment-variable definitions — one for each of the additional intermediate and/or node certificates — are required.
Create environment variables for the administrator-credentials to be used for certificate management, the IP address at which the Couchbase Server-node is located, and the username required for role-based access to a particular resource.
export ADMINCRED=Administrator:password export ip=10.143.173.101 export USERNAME=travel-sample
Note that in this example, the username is specified as
travel-sample, which is typically associated with the Bucket Full Access role, on the bucket travel-sample. For access to be fully tested, ensure that the
travel-sampleuser has indeed been defined on the Couchbase Server-node, and is associated with the Bucket Full Access role. (See Authorization for more information on RBAC.)
Create a directory-structure in which, within a top-level directory named
SSLCA, three subdirectories reside —
rootdir,
intdir, and
nodedir— respectively to hold the certificates you create for root, intermediate, and node.
mkdir ${TOPDIR} cd ${TOPDIR} mkdir ${ROOT_DIR} mkdir ${INT_DIR} mkdir ${NODE_DIR}
Generate the root private key file (
ca.key) and the public key file (
ca.pem):
cd ${ROOT_DIR} openssl genrsa -out ${ROOT_CA}.key 2048 openssl req -new -x509 -days 3650 -sha256 -key ${ROOT_CA}.key \ -out ${ROOT_CA}.pem -subj '/C=UA/O=MyCompany/CN=MyCompanyRootCA'
Generate, first, the intermediate private key (
int.key); and secondly, the intermediate certificate signing-request (
int.csr):
cd ../${INT_DIR} openssl genrsa -out ${INTERMEDIATE}.key 2048 openssl req -new -key ${INTERMEDIATE}.key -out ${INTERMEDIATE}.csr \ -subj '/C=UA/O=MyCompany/CN=MyCompanyIntermediateCA'
Create the extension-file
v3_ca.ext; in order to add extensions to the certificate, and to generate the certificate signing-request:
cat <<EOF>> ./v3_ca.ext subjectKeyIdentifier = hash authorityKeyIdentifier = keyid:always,issuer:always basicConstraints = CA:true EOF
Generate the intermediate public key (
int.pem), based on the intermediate certificate signing-request (
int.csr), and signed by the root public key (
ca.pem).
openssl x509 -req -in ${INTERMEDIATE}.csr \ -CA ../${ROOT_DIR}/${ROOT_CA}.pem -CAkey ../${ROOT_DIR}/${ROOT_CA}.key \ -CAcreateserial -CAserial ../${ROOT_DIR}/rootCA.srl -extfile ./v3_ca.ext \ -out ${INTERMEDIATE}.pem -days 365
Generate, first, the node private key (
pkey.key); secondly, the node certificate signing-request (
pkey.csr); and thirdly, the node public key (
pkey.pem).
cd ../${NODE_DIR} openssl genrsa -out ${NODE}.key 2048 openssl req -new -key ${NODE}.key -out ${NODE}.csr \ -subj "/C=UA/O=MyCompany/CN=${USERNAME}" openssl x509 -req -in ${NODE}.csr -CA ../${INT_DIR}/${INTERMEDIATE}.pem \ -CAkey ../${INT_DIR}/${INTERMEDIATE}.key -CAcreateserial \ -CAserial ../${INT_DIR}/intermediateCA.srl -out ${NODE}.pem -days 365
Generate the certificate chain-file, by concatenating the node and intermediate certificates. This allows the client to verify the intermediate certificate against the root certificate.
cd .. cat ./${NODE_DIR}/${NODE}.pem ./${INT_DIR}/${INTERMEDIATE}.pem > ${CHAIN}.pem
Note that if multiple intermediate certificates are specified for concatenation in this way, the concatenation-order must correspond to the order of signing. Thus, the node certificate, which appears in the first position, has been signed by the intermediate certificate, which therefore appears in the second position: and in cases where this intermediate certificate has itself been signed by a second intermediate certificate, the second intermediate certificate must appear in the third position, and so on.
Note also that the root certificate is never included in the chain.
Manually copy the node private key (
pkey.key) and the chain file (
chain.pem) to the
inboxfolder of the Couchbase Server-node:
mkdir /opt/couchbase/var/lib/couchbase/inbox/ cp ./${CHAIN}.pem /opt/couchbase/var/lib/couchbase/inbox/${CHAIN}.pem chmod a+x /opt/couchbase/var/lib/couchbase/inbox/${CHAIN}.pem cp ./${NODE_DIR}/${NODE}.key /opt/couchbase/var/lib/couchbase/inbox/${NODE}.key chmod a+x /opt/couchbase/var/lib/couchbase/inbox/${NODE}.key
Upload the root certificate, and activate it:
curl -X POST --data-binary "@./${ROOT_DIR}/${ROOT_CA}.pem" \{ADMINCRED}@${ip}:8091/controller/uploadClusterCA curl -X POST{ADMINCRED}@${ip}:8091/node/controller/reloadCertificate
Note that alternatively, the following command-line interfaces can be used:
couchbase-cli ssl-manage -c ${ip}:8091 -u Administrator -p password \ --upload-cluster-ca=./${ROOT_DIR}/${ROOT_CA}.pem couchbase-cli ssl-manage -c ${ip}:8091 -u Administrator -p password \ --set-node-certificate
For the current Couchbase Server-node, enable the client certificate:
curl -X POST --data-binary "state=enable" \{ADMINCRED}@${ip}:8091/settings/clientCertAuth curl -X POST --data-binary "delimiter=" \{ADMINCRED}@${ip}:8091/settings/clientCertAuth curl -X POST --data-binary "path=subject.cn" \{ADMINCRED}@${ip}:8091/settings/clientCertAuth curl -X POST --data-binary "prefix=" \{ADMINCRED}@${ip}:8091/settings/clientCertAuth
For further information on certificate-deployment, see ssl-manage and Encryption On-the-Wire API.
Provide Certificate-Based Authentication for a Java Client
Once the root certificate for a Couchbase Server-node has been deployed, a Java client can authenticate by means of an appropriately prepared keystore.
For an overview, see Certificate-Based Authentication
Proceed as follows. Note that these instructions assume use of the Ubuntu 16 environment configured in the preceding section, Configure X.509 Certificates.
Define environment variables for the name of the keystore to be created, and its password.
export KEYSTORE_FILE=my.keystore export STOREPASS=storepass
If necessary, install a package containing the
keytoolutility:
sudo apt install openjdk-9-jre-headless
Within the top-level,
SSLCAdirectory that you created, generate the keystore:
keytool -genkey -keyalg RSA -alias selfsigned \ -keystore ${KEYSTORE_FILE} -storepass ${STOREPASS} -validity 360 -keysize 2048 \ -noprompt -dname "CN=${USERNAME}, OU=None, O=None, L=None, S=None, C=US" -keypass ${STOREPASS}
Generate the certificate signing-request:
keytool -certreq -alias selfsigned -keyalg RSA -file my.csr \ -keystore ${KEYSTORE_FILE} -storepass ${STOREPASS} -noprompt
Generate the client certificate, signing it with the intermediate private key:
openssl x509 -req -in my.csr -CA ./${INT_DIR}/${INTERMEDIATE}.pem \ -CAkey ./${INT_DIR}/${INTERMEDIATE}.key -CAcreateserial -out clientcert.pem -days 365
Add the root certificate to the keystore:
keytool -import -trustcacerts -file ./${ROOT_DIR}/${ROOT_CA}.pem \ -alias root -keystore ${KEYSTORE_FILE} -storepass ${STOREPASS} -noprompt
Add the intermediate certificate to the keystore:
keytool -import -trustcacerts -file ./${INT_DIR}/${INTERMEDIATE}.pem \ -alias int -keystore ${KEYSTORE_FILE} -storepass ${STOREPASS} -noprompt
Add the client certificate to the keystore:
keytool -import -keystore ${KEYSTORE_FILE} -file clientcert.pem \ -alias selfsigned -storepass ${STOREPASS} -noprompt
This concludes preparation of the Java client’s keystore.
Copy the file (in this case,
my.keystore) to a location on a local filesystem from which the Java client can access it.
Rotating X.509.
How to Rotate a Couchbase Server X.509 Certificate>
Troubleshoot X.509 certificates
During error messages you might encounter when configuring the cluster CA certificate, and suggested corrective actions:
Node Certificates
Here are some error messages you might encounter when configuring the node certificate and the suggested corrective actions: | https://docs.couchbase.com/server/5.0/security/security-x509certsintro.html | 2020-07-02T18:22:18 | CC-MAIN-2020-29 | 1593655879738.16 | [array(['_images/pict/ca_sys_diagram.png', 'ca sys diagram'], dtype=object)
array(['_images/pict/back-to-safety.png', 'back to safety'], dtype=object)] | docs.couchbase.com |
workerB is a browser automation platform. Its goal is to boost user productivity.
We win when you get more work done with less effort. 🚀🚀
workerB has two main components
With the help of these, you can replace your interactions on any website with a script written in JavaScript. We call these scripts actions. The workerB browser extension provides runtime support for executing these actions.
workerB platform comes with the following:
In this guide, we cover the following: | https://docs.workerb.io/ | 2020-07-02T19:21:21 | CC-MAIN-2020-29 | 1593655879738.16 | [] | docs.workerb.io |
DBINFO The DBINFO statement provides information about the database specified. The information returned is restricted by the user class number when the database is opened. Any data items, data sets, or paths of the database that are inaccessible to that user are considered to be nonexistent. Syntax {DATASET [=] dataset} DBINFO dbname$, {ITEMS [=] item } , MODE [=] mode , RETURN [=] str_var [, STATUS [=] status_array(*)] Parameters dbname$ A string variable whose value is a TurboIMAGE database name. dbname must be the variable that was passed to a successful DBOPEN.. item A string or numeric expression that evaluates to the name of a data item or evaluates to a numeric value referencing a data item, respectively. Whether the DATASET or ITEMS option is selected is dependent on the mode selected as described in the DBINFO library procedure in the TurboIMAGE/XL Database Management System. mode A numeric expression that evaluates to a short integer indicating the type of information desired. Available modes are detailed in the explanation of the DBINFO library procedure in the TurboIMAGE/XL Database Management System. str_var The name of the string to which the requested information is returned. The required length is dependent on the type of information to be returned as specified by the MODE parameter.BINFO statement. 120 DBINFO Db$,DATASET=Ds$,MODE=M,RETURN=Buf$,STATUS=S(*) 130 DBINFO Db$,DATASET Ds$,MODE M,RETURN Buf$,STATUS S(*) 140 DBINFO Db$,ITEMS S$,MODE M,RETURN Buf$,STATUS S(*) 150 DBINFO Db$,ITEMS S$,MODE M,RETURN Buf$,STATUS S(*)
MPE/iX 5.0 Documentation | http://docs.hp.com/cgi-bin/doc3k/B3271590001.10189/55 | 2008-05-16T10:18:25 | crawl-001 | crawl-001-010 | [] | docs.hp.com |
FNEND The FNEND statement defines the end of a multi-line function. A multi-line function returns both control of the execution and a value via a RETURN statement. The FNEND statement serves as a marker for the last statement in the function. Therefore, an error occurs if the FNEND statement actually executes. Syntax {FNEND } {FN END} The FNEND statement is legal only in a multi-line function. It is illegal in the main program or a subprogram. It is good programming practice to end a multi-line function with an FNEND statement and use RETURN statements within the function. However, an FNEND statement can appear more than once in a multi-line function at either the beginning of the next subunit or at the end of the containing program. The start of the next subunit in a program does indicate the end of the multi-line function, but for program documentation purposes it is a good idea to include the FNEND. Example 10 READ A 25 DATA 3 20 C= FNMath(A) !Calls the function. 30 PRINT C 99 END 100 DEF FNMath(X) !Start of the function. 110 Y=X*2 120 RETURN Y !Return from the function. 999 FNEND !Indicates the end of the function.
MPE/iX 5.0 Documentation | http://docs.hp.com/cgi-bin/doc3k/B3271590001.10189/89 | 2008-05-16T10:20:49 | crawl-001 | crawl-001-010 | [] | docs.hp.com |
The Program Analyst The interpreter maintains extensive data structures that describe the current program. That information can be valuable for developing and maintaining programs. The Program Analyst is an environment that makes this information available and provides tools for analyzing the information. The Program Analyst can be used for design optimization, memory usage analysis, program statistics information, and optimization of subunit sizes. ANALYST The ANALYST command enters the Program Analyst environment. The following conditions must be met to successfully run the Program Analyst: * The terminal fully supports the terminal-specific features of HP Business BASIC/XL. * The interpreter is running in a session, rather than a batch job. * There is at least one program line in the current program. * The program is not running or paused. * The program has no VERIFY errors. * The destination for OUTPUT and SYSTEM OUTPUT is the display. Syntax ANALYST [screen_argument] Parameters screen_argument An argument that specifies which screen to enter. If no screen is specified, the Main Menu/Browse screen is displayed. Table 2-10 lists each argument, and the screen that it displays. Table 2-10. Analyst Command Arguments -------------------------------------------------------------------------------------------- | | | | Argument | Screen Selected | | | | -------------------------------------------------------------------------------------------- | | | | S | Static Analysis. | | | | | O | Optimize. | | | | | D | Data Types. | | | | | C | Suggest COPTIONs. | | | | | G | Replace GOSUBs. | | | | | P | Optimize PACKFMTs. | | | | | E | Extract Subunit. | | | | -------------------------------------------------------------------------------------------- This section describes each screen. Each action that occurs in a particular screen is explained. The following control actions work from any screen: * To exit the Program Analyst press f8. * Pressing HALT while the Program Analyst is waiting for input transfers control to the next height level screen. * Pressing HALT while the Program Analyst is writing information to the screen returns control to the Main Menu/Browse screen. * Pressing HALT while in the Main Menu/Browse screen exits the Program Analyst. All files created by the Program Analyst have a set of comments giving the file name, the date and time of creation, the name of the screen being used, and the original name of the program as their first few lines. The user interface capabilities used in the Program Analyst are available in HP Business BASIC/XL applications through the following statements and functions: ON KEY ON HALT CURSOR RESPONSE ACCEPT TINPUT
NOTE The features of the Program Analyst can change from one release to the next. Whenever you receive a new version of HP Business BASIC/XL, check the NEWS category in the HELP facility for information on changes and enhancements.
In some screens, the Program Analyst creates file whose names have the form BBPAnn. After you have merged one of these files, purge it. If you have many of these files in your group, the Program Analyst spends extra time trying to find an unused name. The Main Menu/Browse Screen. The purpose of this screen is to provide general information about the current program. The Main Menu/Browse Screen displays the following information about the current program: * The name of the program (the BSAVE file name). * The time and date when the program was last saved. * The overall subunit space and fixed data space requirements of the program. * The subunit space and fixed data space requirement of each subunit. * The source code listing, shown in blocks of eight lines. The cursor is on the first character of the current subunit name. Table 2-11 shows the actions that you can perform while in the Main Menu/Browse screen. Table 2-11. Main Menu/Browse Screen Actions --------------------------------------------------------------------------------------------- | | | | Action | Effect | | | | --------------------------------------------------------------------------------------------- | | | | Softkeys | Pressing one of the labeled softkeys moves between adjacent subunits | | | or to a different screen. | | | | --------------------------------------------------------------------------------------------- | | | | Line number | Entering a line number moves to that line. If the line exists, it is | | | the first line displayed, and the subunit containing it is the | | | current subunit. | | | | --------------------------------------------------------------------------------------------- | | | | Subunit Name | Entering a subunit name moves to that subunit. If the name entered | | | matches a subunit in the program, that subunit is the current subunit | | | and its first eight lines are displayed. | | | | --------------------------------------------------------------------------------------------- | | | | RETURN | Pressing RETURN displays the next eight lines of the current subunit. | | | This method can only be used in the current subunit, and cannot be | | | used to move to the next subunit. | | | | --------------------------------------------------------------------------------------------- The Static Analysis Screen. The purpose of this screen is to provide detailed statistics about the program and its system requirements. The Static Analysis screen displays detailed information about each subunit of a program. It contains three types of information. The following lists describe the information that this screen provides. Interpreter Resource Utilization: This section contains information about resource utilization within the interpreter. Resources include tables, data segments, and interpreter space. The fields and their contents are: Field Contents Global Tables The amount of space (in words) taken to store the interpreter's directory information for locating and managing all of the programs subunits. Included are tables holding the names of the subunits. Local Tables For the subunit being displayed, this value is the amount of space for all tables that reside in the subunit space area of the interpreter's data stack. New Run-time Tables When a program contains references to external routines or intrinsics, the interpreter requires additional space for parameter information at run-time. This value is an estimate of that space requirement. Recoverable The interpreter's tables can sometimes become cluttered with unnecessary information, particularly when extensive editing has been done. The tables can be cleaned by saving the program in ASCII format (through the SAVE LIST command) and then issuing a GET command. The value displayed is an estimate of the number of words in the subunit space that would be recovered by a SAVE LIST and GET. COMMON Space The spaced required by all variables declared in COM statements. Local Space Space for locally declared (or undeclared) variables and parameters. This number is broken down into Numeric Space and String Space fields. Software Metrics This section provides statistics about the program. Many techniques exist for measuring the size and complexity of software and the amount of structure it contains. The Program Analyst can measure these features quickly and accurately. The significance of the numbers is left up to the programmer. The fact that the numbers are generated should not be considered an endorsement of a particular technique, nor is it the intent to pass judgement on the user's code. This section contains the following information: Field Contents Source Lines The number of lines in the subunit. This is the number of unique line numbers. Continuation lines are not counted. Comments The total number of comments including REM statements, comment lines, and comments placed at the end of other program lines. NCSS Non-Comment Source Statements. The number of program lines that do not consist entirely of a comment or REM. Code Volume An attempt to quantify the information content of (Halstead) a group of source statements, in this case a subunit or program. Code volume is a number calculated from the number of unique identifiers and operators and the number of occurrences of these identifiers and operators. Complexity (McCabe) This value is the number of decision points in the subunit or program, plus one. Structure Compliance Indicates the percentage of branches that are (DeMarco) accomplished without explicit GOTO statements. All of the structured statements are counted as branches, including each value or range in a CASE statement. Statement Frequency The Statement Frequency section lists the 21 most frequently used statements in the subunit. The statement names are displayed with the frequency count. The Optimize Screens. The Program Analyst contains four screens that are specifically designed to help improve the efficiency of the current program. The next four sections describe each of these screens. The Data Types Screen. The purpose of this screen is to provide information to minimize run-time conversions through more efficient definitions of variable data types. This screen displays information for the entire MAIN subunit. The name of the subunit and the first and last line numbers are displayed at the top of the screen. A predicted number of conversions is below the subunit information is shown in a table. The lines with the most conversions are indicated to the right of the table. The Program Analyst predicts static conversion numbers. If a statement (such as a FOR statement) is to be executed multiple times, the Program Analyst counts the conversion only once. If the Program Analyst finds a control variable that is a floating-point type, or a default REAL or DECIMAL type and the Program Analyst can determine that the starting value, limit, and step (if present) are all integers, the line number of the FOR loop is reported. A FOR loop that meets those criteria is very inefficient because the control variable has to be converted. In addition, the FOR loop can produce incorrect results. After the information about the MAIN subunit is display, the cursor is at the beginning of the Line Range field at the top of the screen. To move to a different part of the program, enter a line range or a single line number, or press a softkey to move to the previous or next subunit. If you select a single line, the line itself is listed at the bottom of the screen. The data type of each numeric variable is displayed. The Program Analyst cannot accurately detect conversions that occur during a call to an external routine, an intrinsic, a subprogram, or a function. Conversions may be generated if an actual parameter does not match the declared parameter. Also, any conversions that take place to determine which CASE to execute in a SELECT structure are not reported. If your program uses GLOBAL OPTION DECIMAL and does not have OPTION DECIMAL or OPTION REAL statements in each of the subunits, issue the VERIFY command before entering the Program Analyst . This notifies all the subunits that they will be executing in DECIMAL mode and ensures that you get the most accurate information about conversions. The Suggest COPTIONs Screen. The purpose of this screen is to predict the benefit of each of the compiler options (COPTIONs) in terms of generated code savings. The Suggest COPTIONs screen estimates the number of words of compiled code that would be eliminated through the use of each compiler option. The information is displayed in four columns. The first column contains the names of all the compiler options. If the subunit or program currently being displayed has a compiler option in effect, the code savings is displayed in the Current column. If the program or subunit is not current taking advantage of that option, the potential savings is displayed in the Potential column. The final column indicates whether any features that would prevent the use of an option are being used. The Program Analyst cannot estimate the actual size of a compiled subunit. When you enter the Suggest COPTIONs screen, the cursor is positioned under the first letter in the subunit or program name. You can type a subunit name or line number or press a softkey to move to another subunit or line. The Replace GOSUBs Screen. The purpose of this screen is to replace GOSUB statement with the subroutines the reference. This improves performance in some situations. If a program has GOSUBs that execute many thousands of times, the overhead associated with them becomes noticeable. The Replace GOSUBs screen can, with certain restrictions, be used to replace a GOSUB with the body of the referenced subroutine. This is possible when there are enough available line numbers after the GOSUB to insert the entire subroutine before the next line, and the subroutine does not contain and GOTO statements or any lines that are targets of branches. The Replace GOSUBs screen prompts you for a line range to use to search for eligible GOSUBs. It also asks for the maximum number of lines to be inserted for each GOSUB. The Program Analyst then creates an ASCII file containing a copy of the referenced subroutine. If you choose to replace the GOSUB with the subroutine, the GOSUB statement is deleted and the copy of the subroutine is inserted in its place. If the subroutine contains consecutive assignment statements, the Program Analyst combines them into fewer lines if possible. The existence of this screen should not suggest that all GOSUBs should be eliminated. Only those that are used very frequently should be considered for replacement. The Replace GOSUBs screen is useful in conjunction with the Extract Subunit screen described later. Replace GOSUBs can help to resolve subroutine references that might otherwise prevent a successful extraction. The Optimize PACKFMTs Screen. The purpose of this screen is to generate SKIP clauses for PACKFMT statement to minimize packing and unpacking of variables. Often a subunit needs to access only a few items specified in a PACKFMT statement. In a PACK or UNPACK statement, the entire record will be transferred between the string buffer and the variable, even if the PACKFMT statement has information for many more items than the subunit is using. To improve efficiency, the PACKFMT specification can contain one or more SKIP clauses. A SKIP specifies that a certain number of bytes in the string buffer are to be ignored during an UNPACK and skipped over during a PACK. The Optimize PACKFMTs screen determines which items can be skipped, calculates the number of bytes to skip, and then modifies a PACKFMT accordingly. When you enter this screen, you are prompted for the line number of a PACKFMT statement. You can enter a line number or use a softkey to list the line numbers of all of the PACKFMT statements in your program. If the correct line number of a PACKFMT is entered, each item in the PACKFMT statement is examined. If the PACKFMT statement is used anywhere else in the subunit, or if it is in common or is a parameter to the subunit, the Program Analyst assumes that it is needed and cannot be skipped. Otherwise, the Program Analyst determines the number of bytes in that item and generates a SKIP. If adjacent items can be skipped, the Program Analyst creates only one SKIP clause to cover those items. The items that can be skipped are highlighted. If skippable items are found, pressing RETURN will cause the Program Analyst to create an ASCII file containing the following statements: * The original PACKFMT line with the actual statement commented out with a !. * The new PACKFMT statement with a line number one greater than the original. When this file is merged (using the MERGE command) back into the program, the original line serves as documentation of the complete record layout. If you are referencing a PACKFMT statement by a line number instead of a label, you need to modify the appropriate PACK or UNPACK statement. When determining the number of bytes in a string variable, the Program Analyst uses the maximum declared length (or 18 if the string is undeclared). The Program Analyst assumes that strings are always padded out to their maximum length before packing them. This is recommended practice because the maximum length is always used during an UNPACK. The Optimize PACKFMTs screen can also be used to optimize IN DATASET statements. You can modify a IN DATASET statement so that it looks like a PACKFMT statement, optimize the modified statement, merge the statement into the program, and then modify it back to an IN DATASET statement. The Extract Subunit Screen. The purpose of this screen is to assist in dividing large subunits into smaller subunits. Manually removing lines form one part of a program and using the lines to create a new subunit can be tedious. There are many dependencies that must be examined. The Program Analyst can be very useful for extracting subunits. Using the information in the interpreter, the Program Analyst can detect all of the following dependencies: * Branches that will be broken if lines are removed. * Variables that have been shared between the old and new subunits that must become parameters or placed in common. * Single-line functions definitions and OPTION, IMAGE, and PACKFMT statements that will be needed in the new subunit. On entry of a line range, the Program Analyst displays the effects of removing this line range from its subunit. The Program Analyst examines all GOTOs, GOSUBs, and structured statements to determine whether they would be affected. It also determines whether variables (including files) need to be passed as parameters to the proposed new subunit. Once you have identified a line range that can be extracted without breaking any branches or structures, the Program Analyst creates the new subunit and the CALL to it.
NOTE The Program Analyst allows you to extract a subunit even if there are broken branches. Manual editing may be required before the new program can run.
Factors Affecting Extraction. The following factors that can affect extraction cannot be fully analyzed: * DATA, READ, and RESTORE statements. * Report Writer usage. * SORT USING statements. * THREAD statements. * RETURN statements. * ON ERROR, ON KEY, ON HALT, etc. The Program Analyst may produce warnings if these features are used in the subunit being divided. However, the Program Analyst continues to create the subunit. If will be up to you to make any necessary manual changes. When the Program Analyst creates a new subunit, it handles the following requirements automatically: * Creation of parameter lists. * Copying of necessary common block declarations. * Copying of necessary single-line function definitions. * Copying of necessary IMAGE and PACKFMT statements. * Moving declarations of variables that are only using in the new subunit into that subunit. * Copying of OPTION statements. The Program Analyst does not alter your program. It produces two ASCII files that you can GET and MERGE to create an altered program. If you are planning to extract more than one subunit, you must do the GET and MERGE for the first subunits before analyzing subsequent subunits. Extracting a Subunit. The following is a list of the steps required to extract a subunit: 1. Renumber the program to allow space between lines so the Program Analyst can insert any necessary lines. 2. Get and examine a listing. The Program Analyst normally assumes lines are to be extracted from the MAIN subunit. Also, the Program Analyst cannot create a multi-line function this way. Look at the listing to find logical subunit material. 3. Enter the Program Analyst and go to the Extract Subunit screen. Enter the line range that you want to analyze. Use existing line numbers. 4. When you enter a line range, the Program Analyst displays information about branches, structured statement, variables, and detectable problem conditions. Try different line ranges until you find one that will not cause many broken branches. 5. Press the softkey labeled Extract. Use any legal HP Business BASIC/XL identifier. The Program Analyst creates the two files used to produce the altered program. The first file is the original program with the extracted lines replaced by a CALL statement, and the second is the new subunit. 6. Exit the Program Analyst. 7. GET the original program file (the one whose name begins with g) and then MERGE the new subunit file (the one whose name begins with m). Use a line number on the MERGE command that will add the new subunit to the end of the program. 8. Renumber the program, and SAVE it. During the SAVE, the Program Analyst will identify any remaining broken structures that will need manual correction.
MPE/iX 5.0 Documentation | http://docs.hp.com/cgi-bin/doc3k/B3271590001.10189/11 | 2008-05-16T10:21:47 | crawl-001 | crawl-001-010 | [] | docs.hp.com |
GET KEY The GET KEY statement's action depends on whether a filename parameter is included in the statement. If a filename parameter is included and the file has a BKEY format, then the GET KEY statement defines the fields of the user-definable keys by obtaining all of the required information from the file. If the file specified does not have a BKEY format, an error occurs. If the filename is not specified, then the value of the fields for the user-defined keys is the value of the fields set during the previous GET KEY, SCRATCH KEY, or SAVE KEY statement. The default key set (blank key labels, and the ASCII 7 BEL function) is displayed when GET KEY is issued without first issuing SCRATCH KEY, SAVE KEY or a GET KEY. Syntax {GET KEY} {GETKEY } [fname] Parameters fname The file that GET KEY uses to obtain information about the user-definable keys. A file name represented by a quoted string literal, an unquoted string literal or a string expression as described in chapter 6. Examples GET KEY GETKEY "keydef" !Uses file Keydef 100 GETKEY 200 GETKEY keydef2 !Uses file Keydef2 300 GET KEY Filename$ + "." + Groupname$ !Uses the file named in 310 !Filename$ in group Groupname$
MPE/iX 5.0 Documentation | http://docs.hp.com/cgi-bin/doc3k/B3271590001.10189/91 | 2008-05-16T10:24:11 | crawl-001 | crawl-001-010 | [] | docs.hp.com |
FLUSH INPUT The FLUSH INPUT statement empties the input buffer. The input buffer is a buffer where all the data that you have typed in is stored. If an INPUT statement reads three variables, and you have typed in six, the last three remain in the input buffer. If there is data remaining in the input buffer and another INPUT statement is issued, the INPUT statement will pick up that remaining data. The FLUSH INPUT clears that buffer, so that the next INPUT statement will not use that data. Syntax FLUSH INPUT Examples 100 INPUT A,B,C: !Extra input for this statement, e.g., 1,2,3,4,5,6 110 INPUT :D,E,F !is used by this statement, i.e., D = 4, E = 5, F = 6 120 !but 200 INPUT A,B,C: !extra input for this statement 210 FLUSH INPUT !is flushed from the buffer 220 INPUT :D,E,F !and not used by this statement. 999 END
MPE/iX 5.0 Documentation | http://docs.hp.com/cgi-bin/doc3k/B3271590001.10189/88 | 2008-05-16T10:27:50 | crawl-001 | crawl-001-010 | [] | docs.hp.com |
BREAK WHEN The BREAK WHEN statement provides a general mechanism for automatic summary level breaks. The DETAIL LINE statement causes the execution of the statement. If the break condition is true, all summary levels from the BREAK level and up are triggered. This causes TRAILER and HEADER sections to be printed. The BREAK WHEN statement can occur anywhere in the report description. There can only be one BREAK statement per summary level, either BREAK IF or BREAK WHEN. There is no BREAK statement for the report level. Syntax BREAK break_level WHEN control_expr [CHANGES] BREAK break_level WHEN num_ctl_expr [CHANGES] BY num_by_expr Parameters break_level The summary level triggered if the break condition is satisfied. This value must be in the range [0, 9]; a level of zero causes the statement to be ignored. control_expr A numeric or string expression. When BREAK WHEN is num_ctl_expr evaluated, the value of this expression is recorded. Then this value is compared at the next DETAIL LINE to see if any change has occurred. A break occurs occur if a change takes place. num_by_expr A numeric expression indicating how much the control expression must change before a break occurs. See below for exact details about how this works. The control expression must be numeric to use a BY clause. Examples 100 BREAK 1 WHEN Salesman$ CHANGES 100 BREAK 3 WHEN Region CHANGES 100 BREAK N WHEN Product CHANGES BY Base_product_num The BEGIN REPORT statement sets all BREAK WHEN statements to busy, unless the break_level is zero. When the report ends, the lines are no longer busy. The level expression is evaluated only during BEGIN REPORT. In addition, the BY clause value is evaluated only during BEGIN REPORT. The control expression is evaluated during DETAIL LINE, TRIGGER BREAK, and BEGIN REPORT. The DETAIL LINE statement checks all BREAK statements when its total-flag is nonzero. The BREAK statements are evaluated in summary level order, from one to nine. The control expression of the BREAK WHEN statement is evaluated at this time. Conditions for satisfying a break are given below. The LASTBREAK function is set as soon as a break condition is found. DETAIL LINE remembers the lowest level broken and triggers the TRAILER and HEADER sections from that level through nine. First, the TRAILERS are triggered from the highest existing level descending to the lowest level broken. Next, the HEADERS are triggered from the lowest level broken up to the highest existing level. When BEGIN REPORT executes, the level expressions for all BREAK statements are evaluated first. A second pass is made for BREAK WHEN statements. During this pass, the control expression is evaluated and the result put into OLDCV (or OLDCV$) for the break level. Then, if present, the BY clause is evaluated and its value recorded. This value is used when a break occurs at the current level. The TRIGGER BREAK statement also evaluates the BREAK WHEN control expressions for all broken levels. This is to update the OLDCV and OLDCV$ values for all broken levels. These evaluations are done before the actual break occurs. All OLDCV values are updated when a break occurs. The values are updated between the printing of the TRAILER sections and the HEADER sections. Satisfying a BREAK WHEN Condition There are two forms of the BREAK WHEN statement; both have a control expression. The statements differ in what changes can be specified for the control expression. String Control Variables. When the report is activated via BEGIN REPORT, the value of the control expression is recorded. With each DETAIL LINE, the current value of the control expression is compared to the recorded value in OLDCV$. If the two values are not the same, the break level is triggered. After any break at the specified level, the new value of the control expression is recorded in place of the old value, OLDCV$. This process takes place after all trailers have been output, but before headers are printed. Examples BREAK 3 WHEN Sales_Office$ CHANGES In this example, a break at level 3 occurs whenever the control expression Sales_Office$ changes value. Numeric Control Variables. Numeric control expressions have an optional BY clause in the BREAK WHEN statement. If the BY clause is not present or evaluates to zero, the statement works exactly as it does with a string control expression. That is, a break is triggered whenever the control expression in OLDCV changes value. The BY clause establishes a limit value that the control expression must exceed before a break occurs. The numeric expression in the BY clause determines the increment by which the limit changes after a break. However, the limit is NOT set by adding the BY expression to the control expression. When a BEGIN REPORT executes, the control expression is recorded and the BY clause is evaluated. At this time, a break limit is set up as well. This limit is set up in the following manner: * If the BY expression is positive, the limit is set to the multiple of the BY clause closest to, but still greater than, the control expression. * If the BY expression is negative, the limit is set to the multiple of the BY clause closest to, but still less than, the control expression. At each DETAIL LINE, the control expression is compared to the limit value. If the control expression is greater than or equal to the limit (less than or equal if BY was negative), a break is triggered. After the trailers print, but before the headers are output, a new limit is established using the rules above. The BY clause is not reevaluated; only the limit is changed. The break limit is reevaluated at any break at the BREAK WHEN level. This can be caused by breaking at this level or a lower level from a DETAIL LINE or a TRIGGER BREAK statement. Examples BREAK N WHEN Product_no CHANGES BREAK 8 WHEN Profits CHANGES BY 100000 BREAK A(1) WHEN Sales CHANGES BY -50 In the first example, a break takes place when the control PRODUCT_NO changes value. It does not matter how much it changes, nor whether it gets larger or smaller. In the second example, a break occurs when the variable PROFITS exceeds a multiple of one hundred thousand. Assuming that PROFITS has an initial value of 50000, the first break limit is 100000. If PROFITS then changes to 235000, break level 8 is triggered; the next break limit is set to 300000, the next multiple larger than PROFITS. The third example is similar to the second, except that the BY clause is negative. If SALES has an initial value of 480, the break limit is set to 450 (not 430). If SALES gets larger, no break ever occurs. Only when SALES becomes 450 or less does the break occur. For example, if SALES drops to 220, a break occurs and the new limit is set to 200. It is important to remember that this is the multiple of a BY clause. Control Expression Storage Requirements The control expression for BREAK WHEN statements is kept by the OLDCV function. The data space required to contain this expression is determined during BEGIN REPORT, when the values are first examined. The space for OLDCV and OLDCV$ are allocated as follows: * For numeric variables and array elements, space is allocated based on the data type of the variable. There should be no way to get an error with OLDCV in this case. * For other numeric space is allocated based on the data type returned when the expression is initially examined. Thus, if BEGIN REPORT finds an INTEGER expression, space is allocated for an INTEGER. If the expression later returns a REAL outside the INTEGER range, an error occurs. * For other string variables and array elements, space for OLDCV$ is allocated based on the maximum length of the string variable. Thus, the value of the string may be shorter than the space allocated. * For string expressions including substrings, space for OLDCV$ is allocated based on the actual length of the evaluated expression. This could cause a string overflow if a later evaluation returns a longer string. A BY clause stores two values: the BY value itself, and the limit, which causes a break. Both of these values are stored in REAL or DECIMAL, depending on the option in the report subunit.
MPE/iX 5.0 Documentation | http://docs.hp.com/cgi-bin/doc3k/B3271590001.10189/33 | 2008-05-16T10:27:40 | crawl-001 | crawl-001-010 | [] | docs.hp.com |
DETAIL LINE The DETAIL LINE statement is the foundation for Report Writer execution. When the DETAIL LINE statement is executed, all break conditions are tested and triggered, if appropriate, before the detail line output is produced. In addition, this statement causes all totals to be incremented. This statement can not occur within a report definition. Also, it can not be executed while any other break condition such as a level break or a page break is being executed. Syntax [ [LINES]] DETAIL LINE totals_flag [WITH num_lines [LINE ]] [USING image [; output_list]] Parameters totals_flag A numeric expression in the SHORT INTEGER range. This value is used as a Boolean to determine what work must be done. num_lines The maximum number of lines expected to be needed by this statement. This number reflects ALL output done before the next DETAIL LINE statement executes. image An image string or a line reference to an IMAGE line. output_list A list of output items that is identical to the list for the PRINT USING statement. Examples The following examples show the DETAIL LINE statement. 100 DETAIL LINE J WITH 3 LINES 100 DETAIL LINE True 100 DETAIL LINE 0 WITH 2 LINES USING Image_line;A, B If the report has not been activated, DETAIL LINE reports an error. If the report output has not started, this statement starts the report output. When starting the report, DETAIL LINE evaluates all BREAK statements in order to update OLDCV/OLDCV$ values, but no break takes place. Once the report output has started, all work depends on the value of the totals_flag. The totals flag is always evaluated by DETAIL LINE. If its value is TRUE (nonzero), break conditions are checked and totals are automatically accumulated. If the totals flag is FALSE (zero), this work is not done. The output of DETAIL LINE can be controlled by the PRINT DETAIL IF statement. If this statement exists in the report, it is evaluated. If the PRINT DETAIL IF statement is FALSE (zero), the DETAIL LINE statement ends. The WITH and USING clauses are not executed. If PRINT DETAIL IF returns TRUE, or if the statement does not occur in the report description, the WITH and USING clauses are executed if they exist. The work done by DETAIL LINE is shown in the following section. The description of executing a break condition occurs after the TRIGGER BREAK statement. Execution of DETAIL LINE The following is a sequential description of what happens when the DETAIL LINE statement executes. * Checks are made to see that DETAIL LINE can be executed. For this to take place, the report must be active and that there are no Report Writer sections currently executing. * If necessary, the report is started. This will cause the REPORT HEADER, PAGE HEADER, and all HEADER sections to execute. * The totals_flag is evaluated. This value is used as a Boolean value. * If the totals_flag is true (nonzero), do the following: * Evaluate ALL break statements, watching for the lowest numbered BREAK statement that is satisfied. The BREAK IF and BREAK WHEN statements are evaluated in summary level order, from one to nine. During these checks, the CURRENT LEVEL from the RWINFO built-in function changes to reflect the BREAK statement executed. * If a BREAK condition is satisfied, LASTBREAK is set to the lowest numbered BREAK statement with a satisfied BREAK condition. Take the following steps: * Set CURRENT LEVEL to LASTBREAK. * Trigger breaks from level LASTBREAK through nine. This causes the TRAILER and HEADER sections to execute. Some Report Writer counters are updated, totals are reset and OLDCV values are reset. This process is described under TRIGGER BREAK. * Accumulate all TOTALS. GRAND TOTALS are evaluated and added first, then TOTALS are done in ascending level number order. * Evaluate the PRINT DETAIL IF statement. If the statement does not occur, or if the expression is true (nonzero), do the following: * Evaluate the WITH clause of DETAIL LINE. If the number of lines left before the page trailer or end of page is smaller than the WITH value, automatically trigger a page break. If a WITH clause is not specified, there must be one line left on the page. * If the USING clause is present on the DETAIL LINE statement, print the detailed line as indicated by the USING clause and the expressions that follow it.
MPE/iX 5.0 Documentation | http://docs.hp.com/cgi-bin/doc3k/B3271590001.10189/67 | 2008-05-16T10:28:41 | crawl-001 | crawl-001-010 | [] | docs.hp.com |
DBLOCK The DBLOCK statement applies a logical lock to a database, a data set, or a data item value to all but one user. Then, the user can write to the locked area. The PREDICATE statement aids in locking database items in DBLOCK modes five and six. Without the PREDICATE statement, the PACK statement must be used to build a predicate string for the DBLOCK statement. Syntax DBLOCK dbname$ [, MODE [=] lock_mode] [ {DATASET [=] dataset }] [, {DESCRIPTOR [=] str_expr}] [, STATUS [=] status_array(*)] Parameters dbname$ A string variable whose value is a TurboIMAGE database name. dbname must be the variable that was passed to a successful DBOPEN. lock_mode Evaluates to an integer indicating the type of locking desired: Code Effect 1 (default) Locks database unconditionally 2 Locks database conditionally 3 Locks data set unconditionally 4 Locks data set conditionally 5 Locks data item entry unconditionally 6 Locks data item entry conditionally If a data item is locked unconditionally in mode 5, the entry for that item does not have to exist for the lock to succeed.. Required only if lock_mode is three or four. str_expr A string expression that is required only if lock_mode is five or six. Its value is a predicate lock string that describes the locking condition. The PREDICATE statement is used to set up the predicate lock string. The format of the PREDICATE lock descriptors is presented in the description of the DBLOCK library procedure in the TurboIMAGE/XL Database Management System.BLOCK statement. In line 30, a PREDICATE statement has been issued for use with lines 150 and 160. 30 PREDICATE Pred$ FROM Ds$ WITH Item$="skates" 100 DBLOCK Db$,STATUS=S(*) 110 DBLOCK Db$,MODE=1,STATUS=S(*) 120 DBLOCK Db$,MODE=2,STATUS=S(*) 130 DBLOCK Db$,MODE 3,DATASET Ds$,STATUS S(*) 140 DBLOCK Db$,MODE 4,DATASET Ds$,STATUS S(*) 150 DBLOCK Db$,MODE 5,DESCRIPTOR Pred$,STATUS S(*) 160 DBLOCK Db$,MODE 6,DESCRIPTOR Pred$,STATUS S(*)
MPE/iX 5.0 Documentation | http://docs.hp.com/cgi-bin/doc3k/B3271590001.10189/56 | 2008-05-16T10:29:21 | crawl-001 | crawl-001-010 | [] | docs.hp.com |
Fedora 9 provides basic support for encrypted swap partitions and
non-root file systems. To use it, add entries to
/etc/crypttab and reference the created devices
in
/etc/fstab.
New in Fedora 9, the installer Anaconda has support for creating encrypted file systems during installation. For more information on that, refer to the Fedora Installation Guide.
Installing to encrypted volumes, including the root file system, is now supported. There is no configuration tool for adding or removing keys from volumes at a later time, or otherwise doing modification of the encryption. Refer to this feature page for more information:
For full instructions on using encrypted file systems, refer to the Fedora Encryption and Privacy Guide.
The new ext4 file system is available in Fedora 9 as a nearly feature complete preview. Testers: | http://docs.fedoraproject.org/release-notes/f9preview/ta/sn-FileSystems.html | 2008-05-16T14:13:23 | crawl-001 | crawl-001-010 | [] | docs.fedoraproject.org |
You can find a tour filled with pictures and videos of this exciting new release at.
Tämä julkaisu sisältää merkittäviä uusia versioita monista avainkomponenteista ja teknologioista. Seuraavat osiot antavat lyhyen yleiskuvan tärkeistä muutoksista verrattuna edelliseen Fedora-julkaisuun.
Fedora sisältää useita eri spinejä, jotka ovat tietystä ohjelmistopakettijoukosta rakennettuja Fedoran muunnelmia. Jokaisessa spinissä on tietynlaisten käyttäjien vaatimuksia vastaava ohjelmistoyhdistelmä. Käyttäjillä on seuraavat vaihtoehdot verkkoasennuksessa käytettävän erittäin pienen boot.iso-levykuvan lisäksi:
Tavallinen levykuva työpöytä-, työasema- ja palvelinkäyttöön. Tämä spin tarjoaa hyvän päivityspolun ja samankaltaisen ympäristön edellisten Fedora-julkaisujen käyttäjille.-laitteilla ja -työkaluilla on nyt paremmat graafiset käyttöliittymät ja järjestelmäintegraatio.. | http://docs.fedoraproject.org/release-notes/f9preview/fi/sn-OverView.html | 2008-05-16T20:39:21 | crawl-001 | crawl-001-010 | [] | docs.fedoraproject.org |
Notes
This release of the Python agent is a bug fix release which improves our introductory support for instrumenting Tornado 4 applications. Full details about the status of our Tornado 4 support can be found on our Introductory Tornado 4 support page.
The agent can be installed using easy_install/pip/distribute via the Python Package Index or can be downloaded directly from our download site.
For a list of known issues with the Python agent, see Status of the Python agent.
New Feature
New attributes captured for Tornado 4 applications
The following attributes are now captured for requests made to Tornado 4 applications:
request.headers.accept
request.headers.host
port
Bug Fixes
Potentially too many metrics created for
tornado. traces
The
tornado. for Tornado 4 applications could cause a "metric grouping issue" in the function traces it created, if it was used to make requests to a large number of unique URLs. To address this issue, the URL is no longer included in the name of the function trace.
Transactions in Tornado 4 applications could be created with invalid agent settings
In the prior release, if a transaction started before the agent had completed registration with the collector, the transaction could have invalid settings, which would result in various errors in the agent log, including an
AttributeErrorwhen an external call was made during the transaction. These errors only happened at application startup until registration was complete. With this release, transactions cannot start with invalid settings.
The
did not process the cross application tracing headers in the response
Failing to process the response headers resulted in the inability to link to cross application tracing details in the Transaction Trace Details view, as well as missing
ExternalTransactionand
ExternalAppmetrics. Now, the
in the agent processes the cross application tracing headers correctly.
Known Tornado 4 Limitations Addressed
Explain plans for queries made with psycopg2's "async mode" are disabled automatically
Currently, the Python agent does not support explain plans for queries made in psycopg2's "async mode." In the prior release, it was necessary to add the configuration setting
transaction_tracer.explain_enabled = falseto disable explain plans, or else errors would occur during data harvest, potentially causing loss of data. With this release, the agent disables explain plans automatically when async mode is detected.
Added support for Synthetics Transaction Traces
Tornado 4 applications will now recognize incoming requests from Synthetics and generate transaction traces for Synthetic requests.
Status of Tornado 4 Support
A current list of known limitations can be found on our Introductory Tornado 4 support page. No new known limitations have been added since our introductory release (v2.62.0.47). In the next few releases, we plan to continue addressing these issues. | https://docs.newrelic.com/docs/release-notes/agent-release-notes/python-release-notes/python-agent-264048 | 2022-05-16T08:11:04 | CC-MAIN-2022-21 | 1652662510097.3 | [] | docs.newrelic.com |
Ubuntu 14.04 will be end of life in April 2019, this document is a step by step procedure for Scylla users to upgrade Ubuntu 14.04 to 16.04.
OS: Ubuntu 14.04
Scylla: 2018.1 to:
Not to use new 2018.1
sudo apt-get clean all sudo apt-get update sudo apt-get upgrade
Related issue:
sudo apt-get remove scylla-gcc73-libstdc++6
This step will take some time and will require manual interaction.
sudo apt-get update sudo do-release-upgrade sudo reboot
Update Scylla repo to repo for Ubuntu 16.04, Scylla RPM repo <
sudo apt-get dist-upgrade scylla-enterprise
sudo systemctl start scylla-server
Check cluster status with
nodetool status and make sure all nodes, including the one you just upgraded, are in UN status.
Use
curl -X GET " to check scylla version.
Check scylla-server log .
On this page | https://docs.scylladb.com/upgrade/upgrade-enterprise/upgrade-guide-from-ubuntu-14-to-16/ | 2022-05-16T09:01:46 | CC-MAIN-2022-21 | 1652662510097.3 | [] | docs.scylladb.com |
Getting started
Customize your site
Advanced
Reference
How Super works
Super takes your Notion pages and turns them in to a high performing, fast, SEO-optimized website. And this means Super works a bit differently to Notion and other website builders.
Super and Notion workflow
In a nutshell, you manage your content in Notion, and manage your site in Super.
Notion
Notion is where the content for your site lives and is the place you spend most of your time when creating your site. You use Notion to:
- Manage your content
- Update text, images and other media
- Create site pages
- Create your site layout and structure
But what is Notion?
Notion is a powerful all-in-one app used to create documents, manage projects, organise content and so much more. Are you new to Notion? Visit their official getting started guide to learn more.
Super
Super works behind the scenes to turn your pages into a static webpage that is fast and high performance but still stays in sync with Notion. You use Super to:
- Deliver super fast web experience to your users
- Customize the appearance of your site
- Add a domain to your website
- Manage your site SEO settings
- Manage your site pages
How Super sites update
Super creates a static version of your Notion page and caches it to deliver it super fast to your users and search engines.
In creating the static page, we manage the load on Notion, and we cache the static page in our Content Delivery Network. Also, the browser caches pages too.
Here's what's going on behind the scenes:
- Super sites are designed to stay up to date on demand which means that page updates are triggered by site visits.
- When you visit a site page, the Content Delivery Network refreshes the page cache in the background.
- When you refresh the page in your browser after about 5-10 seconds, you will likely see the new version of the page.
This delivers fast pages to maximise User Experience and SEO performance. Once you have regular traffic to your site the cache is kept up to date every 10-15 seconds.
Updates not displaying on your site
There are only a few reasons why updates aren't showing on your site, use the sections below to understand and troubleshoot the issue.
Updating the CDN Cache
Super uses a CDN (Content Delivery Network) to optimize the delivery of content to your users so sites are scalable and fast. The CDN Cache is updated on demand when someone visits your site (this means that once your site is receiving regular traffic it will automatically stay up to date. If you have a very quiet site, you may need to trigger the CDN update manually).
You can trigger a CDN cache update by visiting a page 5 seconds after the last page visit. This visit will get the previous content from the cache and in the background the CDN cache is updated ready for the next visit.
Here are the steps to update the CDN cache for a page:
- Visit your site page. The Content Delivery Network refreshes the page cache in the background.
- Refresh the page in your browser after about 5-10 seconds. You will likely see the new version of the page. If not, wait 5-10 seconds and repeat the refresh.
Updates still aren't showing
In some circumstances, the automatic refreshes of these caches can mean that it seems like your site is not updating, but the cache refresh is just going through its cycle. And even though at each step the timeout is 5 seconds, sometimes these become cumulative and add up to a seemingly long time period. Pressing the refresh button more often does not make the cache expire any faster.
Given the five-second caches between Notion, Super and our Content Delivery Network, try refreshing the page and then wait 5-10 seconds, then refresh again. This usually gives the system enough time to check for new content, load it, rebuild the page, and publish it.
Remember there are multiple levels of caching going on – Notion caches updates that get published to their API, Super caches updates to the CDN, and the CDN caches content, and finally, the browser caches the content.
Clearing the browser cache
When you are developing your site, it can be exciting to see the changes live in the browser. But sometimes when you visit your site in the browser, you might notice the page has not updated. This is because modern browsers cache your sites content (keep a copy of it) to make it load faster.
In order to clear the cache and view the latest updates directly from Super, you'll need to force refresh your browser. Please note: If you've made recent changes in Notion or Super, you'll need to force refresh the browser twice 5-10 seconds apart. Once to trigger the CDN cache refresh, and a second time to retrieve the update content.
How to hard / force refresh and clear your browser cache: In most browsers on PC and Mac, you can perform a simple action to force a hard refresh. Hold down the Shift key on your keyboard and click on the reload icon on your browser’s toolbar. For more specific instructions for your Operating system and browser, check out this page.
How to get consistent updates on your site
We use Super for all our sites too, and our staff have their own Super sites. The best way to check if updates have been made on your site is to use the site preview via the Super Dashboard. If updates are showing here, then you can be confident that the updates will show on the live site once the cache cycle has completed.
Our ways of developing our sites making sure that sites display updates smoothly and frequently is using one of the following methods:
- Make a change in Notion
- Head into your Site preview in the site editor via the Super dashboard and refresh the page (top right refresh button).
- The page should update.
- Make a change in Notion
- Refresh the site page in the browser
- Wait 5 seconds
- Refresh your page in the browser again
- The page should update
If changes aren't appearing in the dashboard or the page after the above refreshes, please wait for 5-10 seconds before repeating.
The expected total time from Notion content change to published content visible will be between 1-2 minutes. This is a by-product of the architectural decision to make Super incredibly high performance and scalable.
Create confidently
Even if changes are not being displayed to your website right away, you can continue to manage content in Notion confidently knowing that your site changes will be displayed eventually. In the rare occasion where your site has not updated within a few hours, please contact our customer support team.
Troubleshooting and Tips
If updates are showing in the Super dashboard preview but not in the browser:
- the browser cache needs clearing (Try hard refreshing your site)
If updates are not showing in the Super dashboard preview:
- Notion has not delivered the updates to Super yet, wait a few minutes and press the refresh button at the top right of the Dashboard preview. Check the public Notion share URL in a private browser to make sure the content is available. | https://docs.super.so/how-super-works | 2022-05-16T08:25:39 | CC-MAIN-2022-21 | 1652662510097.3 | [] | docs.super.so |
Configuring OnCommand Workflow Automation
Contributors
OnCommand Workflow Automation (WFA) enables you to configure various settings—for example, AutoSupport and notifications.
When configuring WFA, you can set up one or more of the following, as required:
AutoSupport (ASUP) for sending ASUP messages to technical support
Microsoft Active Directory Lightweight Directory Access Protocol (LDAP) server for LDAP authentication and authorization for WFA users
Mail for email notifications about workflow operations and sending ASUP messages
Simple Network Management Protocol (SNMP) for notifications about workflow operations
Syslog for remote data logging | https://docs.netapp.com/us-en/workflow-automation-50/help/concept-advanced-configuring-oncommand-workflow-automation.html | 2022-05-16T09:56:56 | CC-MAIN-2022-21 | 1652662510097.3 | [] | docs.netapp.com |
Spaaza Store
Spaaza has a web application called Spaaza Store which is designed to be used by staff and sales associates in a physical environment - usually a retail store.
Through the Spaaza Store interface staff can create or change customer accounts, search for existing accounts, view and activate available benefits on behalf of customers (for example vouchers, or points wallet balance) and view a customers purchase history. The core functionality of Spaaza Store is described below.
Spaaza Store is responsive and is designed to work on any device in a store environment, including phones and tablets. It can also be embedded directly into POS software, with integration points to make this possible.
Languages and localisation
Spaaza Store is currently available in English, German and Dutch. If you require an additional language that is not yet supported please get in touch with our team.
Access and logging in
Staff can access Spaaza Store at the URL store.spaaza.com. If you are using the staging environment of Spaaza the URL is store-test01.spaaza.com.
Staff will need a Spaaza account to log in, this can be created using Spaaza Console (our management system, designed for head office users). Once logged in staff can select the physical store they are in. It is also possible to set “I’m not in a store” this can be useful if Spaaza Store is being used at an offsite event for customers for example.
If Spaaza Store has been integrated into the POS environment then the POS session can be used to automatically log in the staff member and set the store.
Creating a customer account
Staff can create an account in Spaaza Store by clicking on the “+ Customer” button on the home page (below the search box) or by clicking or tapping on the “+” button on the top right.
On the customer creation form, fields marked with red * are required. Once the required customer data has been added staff can click or tap on the “Create” button. If an account already exists or data is in the incorrect format staff will be notified through an error message. If the account creation is successful the staff member will be shown the new customer’s profile screen.
In most implementations, Spaaza will use the webshop to create the new customer account through an integration with the webshop software in these cases once the account has successfully been created in Spaaza Store it will also have been created in the webshop.
Editing a customer account
To edit a customer account Staff can open a customer’s profile page in Spaaza Store and click on the “Edit” button. The required fields can then be changed and saved and the staff member will be redirected back to the profile page.
In most implementations, Spaaza will use the webshop to alter the customer account through an integration with the webshop software in these cases once the account has successfully been updated in Spaaza Store it will also have been updated in the webshop.
Searching for customers
To search for existing customers staff can enter a search query into the search box at the top of the screen and tap or click on enter/submit. Alternatively, staff can visit the home page (by clicking/tapping on the brand icon in the top left) and enter the required search term into the search box there.
Spaaza Store will present search results if the following match the query:
- combination of first and last name
- Spaaza member/card number
- legacy or auxiliary member/card number
- webshop ID
Viewing and interacting with a customer’s incentives
One of the primary uses for Spaaza Store is to allow staff to look up what incentives have been issued already or are available for a customer. For example the customer’s points balance or any available vouchers. Staff then interact with these incentives on behalf of a customer. Some common interactions are described below.
To view an existing customer’s profile page staff can search for a customer and then click or tap on the relevant result.
Activating (claiming) or deactivating (un-claiming) vouchers
Spaaza Store can be used to activate a voucher so that it will be redeemed on the next transaction. In Spaaza this process is also often referred to as “claiming” a voucher. Similarly, staff can also deactivate or “un-claim” a voucher in Spaaza Store. A voucher needs to be in the claimed state for it to be successfully used or “redeemed” on a transaction. A voucher may also be set to “claimed” by default when it is created (a campaign setting).
To activate (claim) a voucher in Spaaza Store click or tap on the “Use now” button shown on the voucher. To deactivate (un-claim) a voucher click or tap on the “Use later” button.
Viewing and spending savings from a wallet
A Spaaza Monetary or “Credit” Wallet allows customers to save and spend digital currency value within a brand. If a customer has a wallet balance on their account then staff can use Spaaza Store to redeem part or all of the saved amount.
The total saved amount for the customer is shown below the title of the wallet (e.g. Boardriders Bucks) on the customer’s profile page in Spaaza Store.
To use the balance staff can select one of the predefined value options shown as buttons or they can select “all” button to apply the full saved amount. The predefined value options shown are based on the total amount saved. The button with the amount that will be applied to the next purchase is shown as highlighted once selected.
To de-select an amount to be spent, staff can tap or click again on the highlighted button. If no buttons are highlighted then no value has been activated to be spent.
Viewing wallet history
To view the history of debit and credit mutations on a Spaaza points or monetary wallet a staff member can click or tap on the “View history” button on a wallet shown on a customer’s profile page in Spaaza Store.
Adding or subtracting wallet value manually
It is possible to give store staff the option to add or remove wallet balance on Spaaza Store but functionality is not enabled by default. If you would like to allow your store staff to do this please contact a member of the Spaaza team to request this.
To add or subtract value:
- click or tap on the button “Add/remove” shown on the wallet in Spaaza Store
- enter the amount of value to add in the input field. For a negative value use a minus sign, for example, “-10”
- click or tap on the button “Change…”
You can set restrictions on the value of mutations staff can make manually in the wallet settings in Console.
Viewing purchase history and receipts
Spaaza Store includes access to the full customer purchase history stored in Spaaza, together with a Spaaza generated digital receipt.
Click or tap on the tab “Purchase History” on the customer profile page in Spaaza Store and all of the purchases are listed. To view a particular receipt click or tap on the purchase. | https://docs.spaaza.com/docs/store.html | 2022-05-16T07:35:57 | CC-MAIN-2022-21 | 1652662510097.3 | [] | docs.spaaza.com |
This section helps you remedy common problems and understand how better to use Veracode Greenlight. Issue Solution I am having trouble signing on or managing users. Review the Administration section. I am having trouble generating an API ID. Review Using the Veracode Greenlight REST API. I do not know on which IDE to install Greenlight. See About Veracode Greenlight. I need to open a support case with Veracode Technical Support. Provide this information to Veracode Technical Support: Your IDE. For example, Eclipse, IntelliJ, or Visual Studio. Your IDE version. - Your Veracode Greenlight version. If you are scanning at the file level or the project level. The programming language of the application you are trying to scan. The size of the file you are trying to scan. Whether autoscan is on or off. A list of third-party plugins, such as Sonar Lint, you use for code analysis. A Greenlight debug log for your IDE. Before you can see debug logs, you must: Enable Debug Logs for Greenlight for Eclipse View Debug Logs in Veracode Greenlight for Visual Studio and Veracode for VS Code Enable Greenlight Debug Logs for Android Studio or IntelliJ | https://docs.veracode.com/r/Troubleshooting_Veracode_Greenlight | 2022-05-16T08:04:07 | CC-MAIN-2022-21 | 1652662510097.3 | [] | docs.veracode.com |
1. Introduction
1.1. Overview
Zope is a free and open-source, object-oriented web application server written in the Python programming language. The term ZOPE is an acronym for “Z Object Publishing Environment” (the Z doesn’t really mean anything in particular). However, nowadays ZOPE is simply written as Zope. It has three distinct audiences.
- Site Managers
Individuals who use of Zope’s “out of the box” features to build websites. This audience is interested in making use of Zope’s existing array of features to create content management solutions. They are generally less concerned about code reuse than the speed with which they can create a custom application or website.
- Developers
Individuals who wish to extend Zope to create highly customized solutions. This audience is likely interested in creating highly reusable custom code that makes Zope do something new and interesting.
- Administrators
Individuals responsible for keeping a Zope site running and performing installations and upgrades.
This guide is intended to document Zope for the second audience, Developers, as defined above. If you fit more into the “user” audience defined above, you’ll probably want to start by reading The Zope Book ..
1.2. Organization of the book
This book describes Zope’s services to the developer from a hands on, example-oriented standpoint. This book is not a complete reference to the Zope API, but rather a practical guide to applying Zope’s services to develop and deploy your own web applications. This book covers the following topics:
- Getting Started
This chapter provides a brief overview of installation and getting started with application development.
- Components and Interfaces
Zope uses a component-centric development model. This chapter describes the component model in Zope and how Zope components are described through interfaces.
- Object Publishing
Developing applications for Zope involves more than just creating a component, that component must be publishable on the web. This chapter describes publication, and how your components need to be designed to be published.
- Zope Products
New Zope components are distributed and installed in packages called “Products”. This chapter explains Products in detail.
- Persistent Components
Zope provides a built-in, transparent Python object database called ZODB. This chapter describes how to create persistent components, and how they work in conjunction with the ZODB.
- Acquisition
Zope relies heavily on a dynamic technique called acquisition. This chapter explores acquisition thoroughly.
- Security
When your component is used by many different people through the web, security becomes a big concern. This chapter describes Zope’s security API and how you can use it to make security assertions about your object.
- Debugging and Testing
Zope has built in debugging and testing support. This chapter describes these facilities and how you can debug and test your components. | https://zope.readthedocs.io/en/latest/zdgbook/Introduction.html | 2022-05-16T09:04:47 | CC-MAIN-2022-21 | 1652662510097.3 | [] | zope.readthedocs.io |
Ag callback to the local host.
The local host can troubleshoot with API Reference when exceptions occur.
The host in a channel calls the
removeInjectStreamUrl method.
addInjectStreamUrl
removeInjectStreamUrl
streamInjectedStatusOfUrl
didJoinedOfUid
didOfflineOfUid
To receive the injected media stream, the audience need to subscribe to the host. | https://docs-preprod.agora.io/en/Interactive%20Broadcast/inject_stream_apple?platform=Android&changePlatformAlert=Android | 2022-05-16T09:30:04 | CC-MAIN-2022-21 | 1652662510097.3 | [] | docs-preprod.agora.io |
java.lang.Object com.atlassian.jira.functest.framework.TestSuiteBuilder
public final class TestSuiteBuilder
Divides up a set of tests such that they can be performed in parallel. It does this by taking a set of tests and dividing them up into composite test of roughly even size.If a passed test is annotated with
Splitablethen its individual test methods will be broken out into the different tests. All other tests have all their test methods within the same batch.
public TestSuiteBuilder(int batch, int maxBatch)
batch- the batch the splitter should return. A value of -1 can be specified when maxBatch is also passed -1. This indicates that no batching should be performed.
maxBatch- the number of batches that splitter should divide the tests into. A value of -1 can be specified when batch is also passed -1. This indicates that no batching should be performed.
public TestSuiteBuilder()
public TestSuiteBuilder addTests(Collection<Class<? extends junit.framework.TestCase>> tests)
tests- the set of tests to divide.
public TestSuiteBuilder addTests(Class<? extends junit.framework.TestCase>... tests)
public TestSuiteBuilder addTest(Class<? extends junit.framework.TestCase> test)
public TestSuiteBuilder addSingleTestMethod(Class<? extends junit.framework.TestCase> testClass, String methodName)
testClass- the TestCase class
methodName- method name
public TestSuiteBuilder log(boolean log)
public TestSuiteBuilder batch(int batch)
public TestSuiteBuilder maxBatch(int maxBatch)
public TestSuiteBuilder parallel(boolean parallel)
public TestSuiteBuilder watch(long timeout, long delay, TimeUnit unit, Class<? extends junit.framework.Test>... classes)
public junit.framework.Test build()
public String toString()
toStringin class
Object | https://docs.atlassian.com/software/jira/docs/api/6.2-ClusteringEAP01/com/atlassian/jira/functest/framework/TestSuiteBuilder.html | 2022-05-16T09:09:55 | CC-MAIN-2022-21 | 1652662510097.3 | [] | docs.atlassian.com |
The documentation you are viewing is for Dapr v1.3 which is an older version of Dapr. For up-to-date documentation, see the latest version.
Kubernetes secrets
Default Kubernetes secret store component
When Dapr is deployed to a Kubernetes cluster, a secret store with the name
kubernetes is automatically provisioned. This pre-provisioned secret store allows you to use the native Kubernetes secret store with no need to author, deploy or maintain a component configuration file for the secret store and is useful for developers looking to simply access secrets stored natively in a Kubernetes cluster.
A custom component definition file for a Kubernetes secret store can still be configured (See below for details). Using a custom definition decouples referencing the secret store in your code from the hosting platform as the store name is not fixed and can be customized, keeping you code more generic and portable. Additionally, by explicitly defining a Kubernetes secret store component you can connect to a Kubernetes secret store from a local Dapr self-hosted installation. This requires a valid
kubeconfig file.
Scoping secret store accessWhen limiting access to secrets in your application using secret scopes, it’s important to include the default secret store in the scope definition in order to restrict it.
Create a custom Kubernetes secret store component
To setup a Kubernetes secret store create a component of type
secretstores.kubernetes. See this guide on how to create and apply a secretstore configuration. See this guide on referencing secrets to retrieve and use the secret with Dapr components.
apiVersion: dapr.io/v1alpha1 kind: Component metadata: name: mycustomsecretstore namespace: default spec: type: secretstores.kubernetes version: v1 metadata: - name: "" | https://v1-3.docs.dapr.io/zh-hans/reference/components-reference/supported-secret-stores/kubernetes-secret-store/ | 2022-05-16T08:45:37 | CC-MAIN-2022-21 | 1652662510097.3 | [] | v1-3.docs.dapr.io |
StackInstanceFilter
The status that stack instances are filtered by.
Contents
- Name
The type of filter to apply.
Type: String
Valid Values:
DETAILED_STATUS
Required: No
- Values
The status to filter by.
Type: String
Length Constraints: Minimum length of 6. Maximum length of 10.
Required: No
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the following: | https://docs.aws.amazon.com/AWSCloudFormation/latest/APIReference/API_StackInstanceFilter.html | 2022-05-16T07:47:04 | CC-MAIN-2022-21 | 1652662510097.3 | [] | docs.aws.amazon.com |
Performance and utilization metrics
HPE Consumption Analytics platform can collect certain performance and utilization metrics from your cloud providers. You can use this data for debugging and troubleshooting, measuring performance, monitoring resource usage, and auditing. This article lists the specific HPE Consumption Analytics platform fields that are collected from each provider and, where applicable, how they are aggregated.
When viewing a report, your data might be displayed with additional aggregation beyond what is described below. This is because HPE Consumption Analytics platform.
Microsoft Azure virtual machines
HPE Consumption Analytics platform collects metrics in twenty-four hourly samples on a daily basis. The aggregation is performed both by Azure to create those hourly numbers and by HPE Consumption Analytics platform platform only collects metrics from Azure for VMs.
Amazon Web Services
These metrics are collected as a single number for a given day, so the aggregation shown here is performed by AWS CloudWatch to create that number.
HPE Consumption Analytics platform reads metrics for the following namespaces:
- EC2
- Redshift
- RDS
- EBS
- ElastiCache
Virtual machines
- CPU Utilization (average)
- Network In MB (sum)
- Network Out MB (sum)
- Storage Read Bytes (sum)
- Storage Write Bytes (sum)
RDS and Redshift databases
- Read Throughput (sum)
- Write Throughput (sum)
EBS volumes
- Storage Read Bytes (sum)
- Storage Write Bytes (sum)
Google Cloud Platform
HPE Consumption Analytics platform does not collect performance and utilization metrics from Google Cloud Platform. | https://docs.consumption.support.hpe.com/CCS/HPE_Consumption_Analytics_Portal_User_Guides/Viewing_usage_and_billing_data/0080_Performance_and_utilization_metrics | 2022-05-16T09:17:27 | CC-MAIN-2022-21 | 1652662510097.3 | [] | docs.consumption.support.hpe.com |
Load document from stream
There might be the case when source or target document is not physically located on the disk. Instead, you have the document in the form of a stream. In this case, to avoid the overhead of saving stream as a file on disk, GroupDocs.Merger provides a way to work with document streams directly.
The following are the steps to be followed:
Following code snippet describes this case.
using (Stream stream = File.OpenRead(@"c:\sample.docx")) { using (Merger merger = new Merger(stream)) { Console.WriteLine($"Document loaded from stream successfully."); } } | https://docs.groupdocs.com/merger/net/load-document-from-stream/ | 2022-05-16T09:29:49 | CC-MAIN-2022-21 | 1652662510097.3 | [] | docs.groupdocs.com |
Ino
From Joomla! Documentation
I'm just a old volunte
Do not hesitate to contact me if you have any question about JDocs, Crowdin.
- [email protected]
Social media profiles
- Twitter: @G_Genovino
- Facebook: [1]}} (~~~~) | https://docs.joomla.org/User:Ino | 2022-05-16T09:08:03 | CC-MAIN-2022-21 | 1652662510097.3 | [] | docs.joomla.org |
When logged into an online service, users can often see information about their friends and other users they've met online, such as whether these users are online, what they're doing, if they're available to join matches, and so on. The Presence Interface provides the Online Subsystem with access to these features.
Presence Status
Most online servies recognize several basic presence states for each user, such as "online", "offline", and "away", as well as game-specific states like "In the lobby" or "Playing a match on (Map)". However, these settings are not always visible, or may be visible to some users but not others, due to service-specific privacy policies and account settings. The Online Subsystem does not interact with these policies or settings, but the information that it retrieves will be affected by them.
Defining Presence
The
FOnlineUserPresence class contains all information related to a user's presence.
In addition to basic information like whether or not the user is currently online, and whether or not the user is playing a game, the user's presence (using the
FOnlineUserPresenceStatus class) stores more in-depth information.
This generally includes a localized string for display, an enumerated value (of type
EOnlinePresenceState) to describe the user's basic state, and a set of key-value pairs to hold any game-specific custom data, which can be used when building the exact presence display message.
Presence Data on Xbox Live
On Microsoft's Xbox Live service (for the Xbox One), developers can go through the Xbox Developer Portal site's "Rich Presence Strings" section to set up localized status strings and get keys for those strings.
To use a string you've set up as your presence status, visible to other users online, put that key into the
StatusStr variable within the
FOnlineUserPresence parameter that the
SetPresence function accepts.
These strings support the insertion of variables, indicated by braces.
For example, the English-language version of a string might be "Playing a match on {current_map}", where "current_map" is a variable that the game can update when setting presence.
To set a variable, add an element to the
Properties array of your
FOnlinePresence which you pass to
SetPresence.
In our example, the element would contain the key "Event_current_map" and a value that represents the map name in English, as it should appear in the message, such as "Forest Map".
Presence Data on PlayStation Network
On Sony's Playstation Network, developers can put a non-localized string into the
StatusStr variable within the
FOnlineUserPresence parameter that the
SetPresence function accepts.
If this variable is left empty, the
Properties variable will be checked for an entry with a key value of "DefaultPresenceKey" to use instead.
Other users will see this string when they successfully query your presence status.
There is also a hidden string, available by setting up a custom property in your
FOnlineUserPresenceStatus parameter with the "CustomData" key (or the
CustomPresenceDataKey constant) that will be received by other users running the same game.
This string will not be displayed, but can be used for any purpose the developer chooses.
Regardless of whether the status string is sent through the variable or the "DefaultPresenceKey" entry in the
Properties variable, it will be stored in the "DefaultPresenceKey" entry in the
Properties variable on other users' machines.
The Friends interface has access to some presence information, such as session ID keys, that are not available through the Presence interface on PlayStation Network.
Retrieving Information About Other Users
The basic flow for collecting presence information about a specific user begins with making a request to the online service through
QueryPresence, specifying that user by
FUniqueNetId.
Once that operation finishes, the provided
FOnPresenceTaskCompleteDelegate will be called, indicating the user and whether the request succeeded or failed.
If successful, the local presence information cache will contain up-to-date presence information, which is available through the
GetCachedPresence function.
Some online services proactively notify the Online Subsystem about user presence.
On these services, although you don't actually have to call
QueryPresence or wait for its delegate, the usual code flow should remain unchanged so that it will work across multiple services.
Setting a User's Presence
The
SetPresence function sets the presence status of a local user through the online service.
This is an asynchronous call due to the need to verify the new status with the online service, and a delegate of type
FOnPresenceTaskCompleteDelegate will be called upon completion.
Presence status itself is described by the FOnlineUserPresenceStatus class. | https://docs.unrealengine.com/4.26/en-US/ProgrammingAndScripting/Online/PresenceInterface/ | 2022-05-16T10:06:37 | CC-MAIN-2022-21 | 1652662510097.3 | [] | docs.unrealengine.com |
User Guide
Local Navigation
About the BlackBerry Desktop Software
The BlackBerry Desktop Software is designed to link the data, media files, and applications on your BlackBerry smartphone or BlackBerry PlayBook tablet with your Mac computer.
You can use the BlackBerry Desktop Software to do the following tasks with your smartphone or tablet:
- Back up and restore your smartphone and tablet data
- Synchronize your media files (music, pictures, and videos)
- Import pictures and videos
- Update your BlackBerry Device Software or BlackBerry Tablet OS
- Manage multiple smartphones and tablets
Additionally, you can use the BlackBerry Desktop Software to do the following tasks with your smartphone:
- Transfer your smartphone settings and data to a new BlackBerry smartphone
- Synchronize your organizer data (calendar entries, contacts, tasks, and memos)
- Add, update, or delete your smartphone applications
- Charge your smartphone
Features that aren't supported for the tablet won't appear on the BlackBerry Desktop Software screens when your tablet is connected.
The main screen of the BlackBerry Desktop Software provides you with quick access to common tasks, such as opening your smartphone or tablet options and importing media files, and provides information about your connected smartphone or tablet, such as the model information and the date that your data was last backed up or synchronized.
If you have used the BlackBerry Desktop Software with other smartphones or tablets, you can connect these smartphones or tablets and switch between them using the Device menu.
Was this information helpful? Send us your comments. | http://docs.blackberry.com/en/smartphone_users/deliverables/42975/About_BlackBerry_Desktop_Software_2.2_1765956_11.jsp | 2014-09-15T04:35:06 | CC-MAIN-2014-41 | 1410657104119.19 | [] | docs.blackberry.com |
In order for Module positions to be available for selection in the Module Manager they must be declared in the templateDetails.xml file for your template. The <positions> element in this file contains sub-elements for each Module position that is supported by the template.
The
templateDetails.xml file contains all the installation and core information for a template, including the module positions it utilizes and displays. Here is a brief list of the commonly used names for the various module positions.
.
A Joomla! template displays a set of modules added to a specific position using the
<jdoc:include /> statement shown below (for further information about
<jdoc:include /> see jdoc statements):
<jdoc:include | http://docs.joomla.org/index.php?title=Declaring_module_positions&curid=163&diff=104057&oldid=30946 | 2014-09-15T04:12:20 | CC-MAIN-2014-41 | 1410657104119.19 | [] | docs.joomla.org |
This article introduces you to the new
JLayouts features in Joomla! 3.2.
Most of the changes are focused in improve the flexibility of the system for third party developers.
Let's use an example: you have articles that have tags, but also contacts have tags, but also categories have tags....
In the old template system previous to
JLayouts (basically what we still use for views) render that would require to copy paste the same HTML rendering in as many places as you wanted to display your tags. Well, that's not so hard no? Ok but then we have a bug, someone fixes it for content but forgets to do it for categories, and then someone adds a cool feature but only for contacts..... Problems start and the system becomes harder to maintain.
Yannick Gaultier contributed
JLayouts to solve this issue. An awesome simple system behind the concept of reusable pieces of code that allows you to render HTML from objects/arrays of data.
Thanks to the JLayout system you can render the tags of an item with:
echo JLayoutHelper::render('joomla.content.tags', $itemTags);
That will basically echo the output of the file in
/layouts/joomla/content/tags.php passing
$itemTags as paremeter for internal use. What we were doing in modules but in a standard way. The only requirement is that
$itemTags object shares the same structure for all the items.
So what are the benefits of that?
We only have to maintain one layout. Designers only have to customise a layout.
Another of the cool benefits of
JLayouts is to become another tool for devs to untie HTML code from PHP code. In an ideal world 100% of the markup in a page should be overridable by a designer/developer without touching Joomla! core. That means that if you load a JS file you should do it in a place that a designer can override it if he decides to not use your JS but replace it with another library. This is actually one of the most important problems we have in Joomla! and the reason why most designers run scared after trying to collaborate for some time.
All the layout system is just 4 files. You can include them in your library for 2.5 support and/or extend them in your own classes.
With the previous JLayout system a call like this:
$layout = new JLayoutFile('joomla.content.tags'); $layout->render($itemTags);
Would search for the layout in:
[0] => templates/mytemplate/html/layouts [1] => layouts
Cool! That means that I can override it. But also you could force the folder where you wanted to load layouts with:
$layout = new JLayoutFile('joomla.content.tags', JPATH_SITE . '/components/com_mycomponent/layouts'); $layout->render($itemTags);
That would search layouts in:
[0] => templates/mytemplate/html/layouts [1] => components/com_mycomponent/layouts
Nice because it's still overridable!
With the previous layout system we still have some problems:
I faced those problems in my job and that's where I started to improve the system. Some of them had a "hard" solution using the old system but I wanted an easy automatic system that also works for complex solutions.
After my initial proposal Joomla! magic started and people came with more suggestions. The final result is a cool system much better that my initial proposal. The magic of open source.
As a clue of the new improvements this can be sample call to layouts now:
$layout = new JLayoutFile('joomla.content.tags', null, array('debug' => true, 'client' => 1, 'component' => 'com_tags'));
One of the modifications is that now the system automatically searches for layouts in the component loaded.
Now the same call that we used before:
$layout = new JLayoutFile('joomla.content.tags'); $layout->render($itemTags);
Will search automatically for layouts in these folders (ordered by priority):
[0] => templates/mytemplate/html/layouts/com_mycomponent [1] => components/com_mycomponent/layouts [2] => templates/mytemplate/html/layouts [3] => layouts
That means that you can use the standard layouts, override them at component level and override the component override at template level.
In our example a developer can customise the way that tags are shown in his component and a designer can override the way that tags are shown in that component.
The previous example automatically detects the component when the layout has been called. But what happens if I want to render my tags the same way they are rendered in com_tags? This is also covered with this sample call:
$layout = new JLayoutFile('joomla.content.tags', null, array('component' => 'com_tags'));
Other of the things that the system now automatically detects is the client from where it's called. That means that if you are in frontend it will search for layouts in frontend.
But I want to render my tags in backend in the same way that com_tags renders them in the frontend! This is covered with this sample call:
$layout = new JLayoutFile('joomla.content.tags', null, array('client' => 0, 'component' => 'com_tags'));
Client parrameter supports these values:
Let's say that you end having a custom folder for layouts but you don't want to store all of them. You just want to, for example, add a folder where joomla has to search for layouts and if it doesn't find them load the standard ones. For example in my company we have a library that contains our shared custom layouts for all our components.
This is done with the new call:
$layout = new JLayoutFile('joomla.content.tags'); $layout->addIncludePaths(JPATH_LIBRARIES . '/hacknsa');
That will add /libraries/hacknsa in the top level to search for layouts (maximum priority). This method also supports an array of paths. In an array remember that the latest will have the highest priority.
Another of the proposals (in this case from Robert Deutz) was to be able to specify suffixes of the layout. The original idea was to allow extensions to load search a layout specific active Joomla! version or use the default one. Example:
$layout = new JLayoutFile('joomla.content.tags', null, array('suffixes' => array('j3x', 'j25'))); echo $layout->render($this->item->tags->itemTags);
But that's only one of the uses. Imagine that you need a different layout for RTL (Right To Left) languages. You can add it to all the searches to always look for it in case of active RTL language enabled. Or imagine a customer address whose zip code, is shown in different places/formats depending on the country. You can add a check for a specific layout for the customer country.
One of the things I found bad in JLayouts is that you cannot inherit the settings of a layout and use them to render another small part of code without having to specify again all the options. Let's see another example: customisable invoices. This way you can have a global call like:
echo JLayoutHelper::render('invoice', $invoiceData);
And then inside the layout something like:
<div class="invoice"> <div class="customer"> <?php echo $this->sublayout('shopper', $displayData['shopper']); ?> </div> <div class="header"> <?php echo $this->sublayout('header', $displayData); ?> </div> <div class="products"> <?php echo $this->sublayout('products', $displayData['products']); ?> </div> <div class="footer"> <?php echo $this->sublayout('footer', $displayData); ?> </div> </div>
Which is a main invoice layout calling sublayouts. So users can just override the header of the invoice without dealing with the rest of the system.
When calling a sublayout the systems tries to find a folder called like this layout with the sublayouts inside. In this example we would have a main layout
invoice.php and in the same folder a folder called
invoice containing the sublayouts (
shopper.php,
header.php,
products.php &
footer.php).
Sublayouts will inherit any setting passed to the parent layout. So they search in the same include paths, in the same client, in the same component and for the same suffixies.
When you start dealing with layouts in various include paths, clients, components... You can easily end not knowing where is the system loading the layouts from. This is why I included a UBU (Useful But Ugly :D ) debug system. To enable it you only have to pass the option
debug to true like
$layout = new JLayoutFile('joomla.content.tags', null, array('suffixes' => array('j3x', 'j25'), 'debug' => true)); echo $layout->render($this->item->tags->itemTags);
You will see something like:
Layouts are a cool thing when used properly but a terrible thing when used in the wrong places. And now everybody wants to convert everything to layouts. This is why you can easily find layouts that are used by articles, banners, contacts, clients, weblinks, newsfeeds. You would say "but that's cool no? We are saving code!". No! We are just creating a single layout with tons of if statements inside it to deal with all the differences between components.
In my opinion there are no benefits in using a layout to render 4 fields. That's something that has to be done in the template and is not going to be ever reused outside the core. And that's my advice: if it can be reused outside the core then it makes sense as layout. Examples of layouts: render a list, a button, a menu, a field, pagination.... Another good advice: if it cannot be overriden is better in a layout.
Layouts are not the solution for everything.
Imagine the current jQuery loading in core. This is done from JHtml classes. Why not make JHtml search for a overrides automatically in the component folder? So I can have my own custom jQuery version tested with the other libraries in my component. Yes, it can conflict with other module requirements but isn't that what we already have? At least we will avoid loading jQuery multiple times. This is not really a task for layouts but to apply the same concept to JHtml.
Now imagine that top menu contains a bug on a button or in something that is inside a layout. You can fix it inside a layout override on your own component and wait until the core fixes it. Same if you have a library that conflicts with core. Lot of support saved explaining that the issue is a core bug.
This are only some of the ideas behind the concept.
Layouts are a really powerful tool and is one of those things that can help us to improve the relations between coders vs desginers. There are a lot of places to use layouts. Some of them still not discovered, some of them waiting there for someone to do the job. Do you want to help us? | http://docs.joomla.org/index.php?title=J3.x:JLayout_Improvements_for_Joomla!&diff=105024&oldid=105015 | 2014-09-15T05:24:54 | CC-MAIN-2014-41 | 1410657104119.19 | [] | docs.joomla.org |
ClustrixDB provides several mechanisms to identify queries that consume a disproportionate amount of system resources. Such queries are typically a result of poor indexing or bugs in the application.
ClustrixDB supports the following syntax for killing queries:
The following statement will output the longest running query in the system. It's often the first step that a system administrator will take to identify possible problems on a misbehaving cluster. The sessions virtual relation provides a great deal of detail about each session's executing state. In addition to current statements, the connection information and transaction state will also be displayed.
In a fully relational SQL database such as ClustrixDB, long running write transactions may cause a problem. Frequently, misbehaving applications erroneously leave the AUTOCOMMIT option OFF, leaving every session to run in a single, very long transaction. When such cases occur, these transactions will accrue a large collection of write locks, preventing other transactions that attempt to modify the same data from running. To identify such cases, ClustrixDB includes several columns in the sessions relation that track the age of the transaction, the number and types of statements executed in the current transaction, and whether the transaction has issued any writes (boolean value 0, 1).
For example, to find the oldest write transaction in the system, issue the following: | https://docs.clustrix.com/display/CLXDOC/Identifying+and+Killing+Rogue+Queries | 2020-10-23T20:59:09 | CC-MAIN-2020-45 | 1603107865665.7 | [] | docs.clustrix.com |
Unable to start built-in HTTP and DOM sensor listener on port 3330 due to exception
This error is displayed when the ports used by Sboxr are already in use by another process. One likely reason could be that you have already started one instance of Sboxr and it is using these ports.
To resolve this, close all those instances and launch Sboxr again.
Unable to start Kestrel. System.IO.IOException: Failed to bind to address http://[::]:3333: address already in use
If any Sboxr'd Chrome instances opened in an earlier use of Sboxr are still active, then close them before launching Sboxr again.
If the problem persists then ensure that port number 3333 is unused on your machine.
Sboxr cannot proceed further because the Database couldn't be created
Sboxr will create a database to store all session data. This error indicates that it couldn't create this database due to access restrictions.
Check whether you have WRITE Permissions in the folder where the database is being created. By default it happens inside the same directory where all other Sboxr files are located. If you have selected a custom path for storing session data then you should check the permissions of that directory.
Sboxr Licensing Server is not reachable to validate your License
For validating your License, Sboxr will connect to its Licensing Server. The error indicates that the Licensing Server is not reachable.
Check your Connection Settings and ensure you have Internet Connectivity.
ERROR:cert_verify_proc_nss.cc(974)] CERT_PKIXVerifyCert for ssl.gstatic.com failed err=-8179
The above error message might be displayed for Linux users for each domain they are visiting through Sboxr'd Chrome.
This is shown due to the SSL interception that Sboxr is doing. It does not affect Sboxr's functionality and can be safely ignored. | https://docs.sboxr.com/faq | 2020-10-23T22:16:42 | CC-MAIN-2020-45 | 1603107865665.7 | [] | docs.sboxr.com |
The mobile version as well as the desktop one allows you to adapt the scheduler to a particular language and a region.
To localize the scheduler to some language you should know the following:
All locale's parameters for the mobile version are contained in the scheduler.locale.labels object and to redefine the parameters you should 'rewrite' this object.
For 'rewriting' you should use the technique below:
scheduler.locale.labels = labels;
where labels is any object variable that contains the redefined parameters.
var labels = { icon_today : "...", ... }
In order to localize dates (week days and months) you should follow the instruction given in the article Components Localization.
The table below presents all localization parameters available for the mobile version of the scheduler.
scheduler.locale.labels = { list_tab: "List", day_tab: "Day", month_tab: "Month", icon_today: "Today", icon_save: "Save", icon_done: "Done", icon_delete: "Delete event", icon_cancel: "Cancel", icon_edit: "Edit", icon_back: "Back", icon_close: "Close form", icon_yes: "Yes", icon_no: "No", confirm_closing: "Your changes will be lost, are your sure ?", confirm_deleting: "The event will be deleted permanently, are you sure?", label_event: "Event", label_start: "Start", label_end: "End", label_details: "Notes", label_from: "from", label_to: "to", label_allday: "All day", label_time: "Time" };
Recurring events use the same technique, but take another locale object - scheduler.locale.labels.recurring.
Localization parameters for recurring events:
Back to topBack to top
scheduler.locale.labels.recurring = { none: "Never", daily: "Daily", day: "day(s)", every: "Every", weekly: "Weekly", week: "week(s) on", each: "Each", on_day: "on the", monthly: "Monthly", month: "month(s)", month_day: "on what day of the month", week_day: "on what day of the week", yearly: "Yearly", year: "year(s) in", counters: ["the first","the second","the third", "the fourth", "the fifth"], never: "Never", repeat: "Repeat", end_repeat: "End repeat", endless_repeat: "Endless repeat", end_repeat_label: "Repeat will end by" }; | https://docs.webix.com/mobile_calendar__localization.html | 2020-10-23T21:24:46 | CC-MAIN-2020-45 | 1603107865665.7 | [] | docs.webix.com |
Tip answered in the Documentation or encounter any kind of problem related to the Growtheme, remember that we are happy to help and just an email away. You can write us directly to and we usually reply and resolve your issue within 24 hours (often less).
Please make sure to include the domain where the Growtheme is running and if possible the following login credentials so we reduce needless going back and forth before taking a deep look into the causes for your particular problem:
- WordPress Admin Login (Login URL, Username, Password)
- FTP Server Login (Server, Username, Password)
- Optional: Web Hosting Provider Login (Provider, Username, Password)
This is only necessary if you are not sure of your FTP Server Login. Your Hosting Provider is usually the place where you bought your Domain Name.
Remember that all your details will be kept private. If you’d prefer, you can create as well temporary user names and passwords and then delete them once we are finished helping. Also, please test the login information before you send this to us to make sure it works! | https://docs.growtheme.com/additional-features/get-premium-support/ | 2020-10-23T21:32:47 | CC-MAIN-2020-45 | 1603107865665.7 | [] | docs.growtheme.com |
Add a Search Client
SearchUnify provides powerful search clients to help users find information, such as cases, community threads, and the data inside their organizations. The search clients come in several flavors, each calibrated to work on a platform. However, before a search client can be set up on a platform, it needs to be added into your instance and configured. This article demonstrates the steps to adding a search client to your instance. For configuration, visit the Edit Search Client Configurations section.
Adding a Search Client
- Open Search Clients and click Add New Search Client.
- Select a platform where a search client will be installed.
- Give your search client a name in Enter Platform Name, write your SearchUnify instance web address in Enter Base URL, and click Save.
You have successfully added a search client if you can see if your search client on the Manage Search Clients screen.
Last updated: Friday, September 25, 2020 | https://docs.searchunify.com/Content/Search-Clients/Add.htm | 2020-10-23T21:28:43 | CC-MAIN-2020-45 | 1603107865665.7 | [] | docs.searchunify.com |
Welcome to Django Kubernetes Manager’s documentation!¶
Django Kubernetes Manager is an open source project to wrap the complexity of Kubernetes management in the simplicity of Django Rest Framework.
Documentation is (mostly) autogenerated, so if you notice anything that should be changed or added, please create a PR 🙋
Introduction¶
Our engineering team has developed several data processing apps, and found celery wasn’t quite enough for dispatching heavier tasks. We decided to try Kubernetes Jobs, and while pleased with performance, wanted a less verbose, more object oriented way to interact with our clusters.
And thus Django Kubernetes Manager was spawned. Using Django Rest Framework and the kubernetes client library, our devs came up with the idea to treat each object we’d be deploying as a Model instance, and use the DRF viewsets and actions to create an RESTful API framework from which we could extend for each projects particular needs. | https://django-kubernetes-manager.readthedocs.io/en/latest/?badge=latest | 2020-10-23T21:40:42 | CC-MAIN-2020-45 | 1603107865665.7 | [array(['_images/dkm-logo.png', 'DjangoKubernetesManager'], dtype=object)] | django-kubernetes-manager.readthedocs.io |
The Rights Manager library defines all the ways you can customize a Configurable Rights Pool. In general, granting more rights to a Smart Pool requires users to place greater trust in the smart pool creator.
The library is designed to be easily extensible (e.g., the method signatures don't change as more rights are added). Let's take a look at the current set of rights, and how they might be applied to real use cases.
Pause Swapping: allows the controller to halt trading (swaps) on the underlying core pool. Like finalized core pools, Configurable Rights Pools are created with trading enabled. With pause swapping, the controller (or logic in the smart contract) can toggle trading on and off. For instance, the controller might want to "short-circuit" the contract in certain pathological cases, such as market crashes.
Change Swap Fee: allows the controller to change the Swap Fee after contract deployment, within the bounds set by the underlying core pool (e.g., it cannot be zero, or greater than 10%). With this right, it would be possible to implement fee optimization strategies (e.g., maximize return, or minimize impermanent loss).
Change Weights: the controller can call updateWeight (to directly update a single token's weight), or updateWeightsGradually (to linearly transform a set of weights over time). This enables liquidity bootstrapping, UMA-style perpetual synthetics, and many other strategies. Note that altering weights will change balances - which means transferring tokens - in order to leave prices unchanged. When updating weights gradually, the protocol enforces a minimum time between updates, and a minimum total time for the update. These parameters are set at create time, and are immutable thereafter.
Add/Remove Tokens: allows the controller to change the composition of the pool. Needless to say, this requires a lot of trust in the smart pool owner, but enables powerful strategies, especially in combination with other rights. For example, a perpetual "rolling" synthetic. Adding a token is a two-step process meant to mitigate this risk and lower the trust required. The protocol emits an event when a token is "committed" (about to be added), and enforces a minimum wait time before the controller can "apply" (actually add) the token.
Whitelist LPs: when this right is enabled, no one can add liquidity (including the controller, beyond initial creation of the pool), unless they are added to a whitelist by the creator. This enables things private investment clubs, exclusive token launches, etc.
Change Cap: Inspired by PieDAO's capped pools, Configurable Rights Pools have a "cap" on the total supply of pool tokens that can be issued. This can be used for experimental/risky pools, to limit potential losses, or to halt further provision of liquidity at any time. When this right is not enabled, there is no cap. When it is enabled, the cap is set to the initial supply on creation - and can be changed later by the controller. | https://docs.balancer.finance/smart-contracts/rights-manager | 2020-10-23T21:43:43 | CC-MAIN-2020-45 | 1603107865665.7 | [] | docs.balancer.finance |
Endpoint Policies Work
You can configure NetScaler Gateway to check if a user device meets certain security requirements before a user logs on. This is called a preauthentication policy. You can configure NetScaler Gateway to check a user device for antivirus, firewall, antispam, processes, files, registry entries, Internet security, or operating systems that you specify within the policy. If the user device fails the preauthentication scan, users are not allowed to log on.
If you need to configure additional security requirements that are not used in a preauthentication policy, you configure a session policy and bind it to a user or group. This type of policy is called a post-authentication policy, which runs during the user session to ensure the required items, such as antivirus software or a process, is still true.
When you configure a preauthentication or post-authentication policy, NetScaler Gateway downloads the Endpoint Analysis Plug-in and then runs the scan. Each time a user logs on, the Endpoint Analysis Plug-in runs automatically.
You use the following three types of policies to configure endpoint policies:
- Preauthentication policy that uses a yes or no parameter. The scan determines if the user device meets the specified requirements. If the scan fails, the user cannot enter credentials on the logon page.
- Session policy that is conditional and can be used for SmartAccess.
- Client security expression within a session policy. If the user device fails to meet the requirements of the client security expression, you can configure users to be placed into a quarantine group. If the user device passes the scan, users can be placed into a different group that might require additional checks.
You can incorporate detected information into policies, enabling you to grant different levels of access based upon the user device. For example, you can provide full access with download permission to users who connect remotely from user devices that have current antivirus and firewall software requirements. For users connecting from untrusted computers, you can provide a more restricted level of access that allows users to edit documents on remote servers without downloading them.
Endpoint analysis performs the following basic steps:
- Examines an initial set of information about the user device to determine which scans to apply.
- Runs all applicable scans. When users try to connect, the Endpoint Analysis Plug-in checks the user device for the requirements specified within the preauthentication or session policy. If the user device passes the scan, users are allowed to log on. If the user device fails the scan, users are not allowed to log on. Note: Endpoint analysis scans completes before the user session uses a license.
- Compares property values detected on the user device with desired property values listed in your configured scans.
Produces an output verifying whether or not desired property values are found.
Attention: The instructions for creating endpoint analysis policies are general guidelines. You can have many settings within one session policy. Specific instructions for configuring session policies might contain directions for configuring a specific setting; however, that setting can be one of many settings that are contained within a session profile and policy.
How Endpoint Policies Work. | https://docs.citrix.com/en-us/netscaler-gateway/11-1/vpn-user-config/endpoint-policies/ng-endpoint-how-it-works-con.html | 2020-10-23T22:31:35 | CC-MAIN-2020-45 | 1603107865665.7 | [] | docs.citrix.com |
TOPICS×
Activity Map overview
On January 16, 2020, Adobe Analytics started moving to a new domain -. This change may cause Activity Map to stop working for some customers in specific cases. As you know, Activity Map is injected into the customer page in an iframe (one iframe for the Activity Map toolbar and one iframe for the Activity Map Bottom Panel). You may have set a Content Security Policy directive on your web page for "frame-src" that does not include ".adobe.com". In this case, Activity Map will stop working on such a web page.
Activity Map is an Adobe Analytics application that is designed to rank link activity using visual overlays and provide a dashboard of real-time analytics to monitor audience engagement of your web pages.
Activity Map lets you set up different views to visually identify the acceleration of customer activity, quantify marketing initiatives, and act on audience needs and behaviors.
Getting started for Admins
Getting started for Users
Activity Map features | https://docs.adobe.com/content/help/en/analytics/analyze/activity-map/activity-map.html | 2020-10-23T23:02:10 | CC-MAIN-2020-45 | 1603107865665.7 | [] | docs.adobe.com |
report. To define the groupings, the fields available for grouping:
Grouping by Columns
In the basic Transaction journal report, no default grouping by columns is specified. | https://docs.codejig.com/en/entity2305843015656313960/view/4611686018427399061 | 2020-10-23T21:47:06 | CC-MAIN-2020-45 | 1603107865665.7 | [] | docs.codejig.com |
scriptsA piece of code that allows you to create your own Components, trigger game events, modify Component properties over time and respond to user input in any way you like. More info
See in Glossary that contain the mathematical calculations and algorithms for calculating the Color of each pixelThe smallest unit in a computer image. Pixel size depends on your screen resolution. Pixel lighting is calculated at every screen pixel. More info
See in Glossary rendered, based on the lighting input and the Material configuration.
Textures are bitmap images. A Material can contain references to textures, so that the Material’s Shader can use the textures while calculating the surface color of a GameObjectThe fundamental object in Unity scenes, which can represent characters, props, scenery, cameras, waypoints, and more. A GameObject’s functionality is defined by the Components attached to it. More info
See in Glossary. InspectorA Unity window that displays information about the currently selected GameObject, Asset or Project Settings, allowing you to inspect and edit the values. More info
See in Glossary in Unity allows you to assign your own Texture to these Texture variables.
For most normal renderingThe process of drawing graphics to the screen (or to a render texture). By default, the main camera in Unity renders its view to the screen. More info
See in Glossary (such as rendering characters, scenery, environments, solid and transparent GameObjects, hard and soft surfaces) the Standard ShaderA built-in shader for rendering real-world objects such as stone, wood, glass, plastic and metal. Supports a wide range of shader types and combinations. More info
See in Glossary | https://docs.unity3d.com/2018.4/Documentation/Manual/Shaders.html | 2020-10-23T21:33:27 | CC-MAIN-2020-45 | 1603107865665.7 | [] | docs.unity3d.com |
If your workflows fail or the NSX Edges are unstable, you can perform troubleshooting steps.
Problem
When you change the distributed port group configuration on the vSphere Client, workflows might fail and the NSX Edges might become unstable.
Cause
Removal or modification of the distributed port groups for overlay and uplink that were created during the NSX Edge cluster setup of cluster configuration, is not allowed by design.
Solution
If you require to change the VLAN or IP Pool configuration of NSX Edges, you must first remove elements of NSX-T Data Center and the vSphere with Tanzu configuration from the cluster.
For information about removing elements of NSX-T Data Center, see the NSX-T Data Center Installation Guide. | https://docs.vmware.com/en/VMware-vSphere/7.0/vmware-vsphere-with-tanzu/GUID-E338A8B8-9474-4B9A-ABEE-2DCA736A8AC8.html | 2020-10-23T22:05:01 | CC-MAIN-2020-45 | 1603107865665.7 | [] | docs.vmware.com |
To track the number of transactions per day, you just add a chart and set it up in 3 steps:
1. Drag-and-drop the chart from the Components panel.
2. Add a new dataset and select the resource and the collection you want to display:
3. In the following example the transaction records are made to be displayed on this chart as their exact counts, grouped by the creation date across a period of time:
The tool is ready. Now you may want to share it with your teammates. | https://docs.jetadmin.io/getting-started/quickstart/adding-a-chart | 2020-10-23T21:12:35 | CC-MAIN-2020-45 | 1603107865665.7 | [] | docs.jetadmin.io |
Give knowledge objects of the same type unique names
When you create knowledge objects that are processed at search time, it is best if all knowledge objects of a single type have unique names. This helps you avoid name collision issues that can prevent your configurations from being applied at search time.
For example, to avoid name collision problems, you should not have two inline field extraction configurations that have the same
<class> value in your Splunk implementation. However, you can have an inline field extraction, a transform field extraction, and a lookup that share the same name, because they belong to different knowledge object types.
You can avoid these problems with knowledge object naming conventions. See Develop naming conventions for knowledge objects.
Configurations sharing a host, source, or source type
When two or more configurations of a particular knowledge object type share the same
props.conf stanza, they share the host, source, or source type identified for the stanza. If each of these configurations has the same name, then the last configuration listed in the stanza overrides the others.
For example, say you have two lookup configurations named
LOOKUP-table in a
props.conf stanza that is associated with the
sendmail source type:
[sendmail] LOOKUP-table = logs_per_day host OUTPUTNEW average_logs AS logs_per_day LOOKUP-table = location host OUTPUTNEW building AS location
In this case, the last
LOOKUP-table configuration in that stanza overrides the one that precedes it. The Splunk software adds the
location field to your matching events, but does not add the
logs_per_day field to any of them.
When you name your lookup
LOOKUP-table, you are saying this is the lookup that achieves some purpose or action described by "table." In this example, these lookups achieve different goals. One lookup determines something about logs per day, and the other lookup has something to do with location. Rename them.
[sendemail] LOOKUP-table = logs_per_day host OUTPUTNEW average_logs AS logs_per_day LOOKUP-location = location host OUTPUTNEW building AS location
Now you have two different configurations that do not collide.
Configurations belonging to different hosts, sources or source types
You can also run into name collision issues when the configurations involved do not share a specific host, source, or source type.
For example, if you have lookups with different hosts, sources, or source types that share the same name, you can end up with a situation where only one of them seems to work at any given time. If you know what you are doing you might set this up on purpose, but in most cases it is inconvenient.
Here are two lookup configurations named
LOOKUP-splk_host. They are in separate
props.conf stanzas.
[host::machine_name] LOOKUP-splk_host = splk_global_lookup search_name OUTPUTNEW global_code [sendmail] LOOKUP-splk_host = splk_searcher_lookup search_name OUTPUTNEW search_code
Any events that overlap between these two lookups are only affected by one of them.
- Events that match the host get the host lookup.
- Events that match the source type get the source type lookup.
- Events that match both get the host lookup.
For more information about this, see Configuration file precedence in the Admin Manual
Configurations belonging to different apps
When you have configurations that belong to the same knowledge object type and share the same name, but belong to different apps, you can also run into naming collisions. In this case, the configurations are applied in reverse lexicographical order of the app directories.
For example, say you have two field alias configurations.
The first configuration is in
etc/apps/splk_global_lookup_host/local/props.conf:
[host::*] FIELDALIAS-sshd = sshd1_code AS global_sshd1_code
The second configuration is in
etc/apps/splk_searcher_lookup_host/local/props.conf:
[host::*] FIELDALIAS-sshd = sshd1_code AS search_sshd1_code
In this case, the
search_sshd1_code alias would be applied to events that match both configurations, because the app directory
splk_searcher_lookup_host comes up first in the reverse lexicographical order. To avoid this, you might change the name of the first field alias configuration to
FIELDALIAS-global_sshd.! | https://docs.splunk.com/Documentation/Splunk/7.2.0/Knowledge/Knowledgeobjectnamecollisions | 2020-10-23T22:38:55 | CC-MAIN-2020-45 | 1603107865665.7 | [array(['/skins/OxfordComma/images/acrobat-logo.png', None], dtype=object)] | docs.splunk.com |
Important: #80266 - Moved config.sys_language_softExclude to compatibility7¶
See Issue #80266
Description¶
The TypoScript option
config.sys_language_softExclude to set
certain TCA table fields to
l10n_mode=exclude during frontend request
runtime has been moved to compatibility7.
If any installation depends on this option in the TYPO3 frontend, the extension should be installed.
However, as the TCA option
l10n_mode=exclude has been superseded
by the TCA option
allowLanguageSynchronization the actual use-case
for this TypoScript setting should be re-evaluated. | https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/8.7/Important-80266-MovedConfigsysLanguageSoftExcludeToCompatibility7.html | 2020-10-23T22:32:57 | CC-MAIN-2020-45 | 1603107865665.7 | [] | docs.typo3.org |
.
All other actions (create, update, delete) redirect to list or show action, by default.
Partials¶
- FormFieldErrors.html Inline validation/error messages for form inputs.
- Poll/
- Administration.html Box below voting. Just visible for the poll author and administrators.
- AuthorInfo.html Username/Mail of poll author.
- FormFields.html All form fields a poll has (but options).
-.
- TableHead.html Table head of voting table.
- Type/
- Simple.html Options section for simple poll
- Schedule.html Options section (with date picker) for scheduled poll | https://docs.typo3.org/p/fgtclb/t3oodle/master/en-us/DevNotes/TemplatesPartials.html | 2020-10-23T22:29:04 | CC-MAIN-2020-45 | 1603107865665.7 | [] | docs.typo3.org |
Ubuntu.Components.ListItemDrag
Provides information about a ListItem drag event. More...
Properties
- accept : bool
- from : int
- maximumIndex : int
- minimumIndex : int
- status : enum
- to : int
Detailed Description
The object cannot be instantiated and it is passed as parameter to ViewItems::dragUpdated attached signal. Developer can decide whether to accept or restrict the dragging event based on the input provided by this event.
The direction of the drag can be found via the status property and the source and destination the drag can be applied via from and to properties. The allowed directions can be configured through minimumIndex and maximumIndex properties, and the event acceptance through accept property. If the event is not accepted, the drag action will be considered as cancelled.
Property Documentation
The property can be used to dismiss the event. By default its value is true, meaning the drag event is accepted. The value of false blocks the drag event to be handled by the ListItem's dragging mechanism.
Specifies the source index the ListItem is dragged from.
These properties configure the minimum and maximum indexes the item can be dragged. The properties can be set in ViewItems::dragUpdated signal. A negative value means no restriction defined on the dragging interval side.
The property provides information about the status of the drag. Its value can be one of the following:
- ListItemDrag.Started - indicates that the dragging is about to start, giving opportunities to define restrictions on the dragging indexes, like minimumIndex, maximumIndex
- ListItemDrag.Moving - the dragged item is moved upwards or downwards in the ListItem
- ListItemDrag.Dropped - indicates that the drag event is finished, and the dragged item is about to be dropped to the given position.
Specifies the index the ListItem is dragged to or dropped. | https://phone.docs.ubuntu.com/en/apps/api-qml-current/Ubuntu.Components.ListItemDrag | 2020-10-23T22:30:21 | CC-MAIN-2020-45 | 1603107865665.7 | [] | phone.docs.ubuntu.com |
QtContacts.SortOrder
The SortOrder element defines how a list of contacts should be ordered according to some criteria. More...
Properties
- blankPolicy : enumeration
- caseSensitivity : enumeration
- detail : enumeration
- direction : enumeration
- field : int
Detailed Description
This element is part of the QtContacts module.
See also QContactSortOrder and ContactModel.
Property Documentation
This property enumerates the ways in which the sort order interprets blanks when sorting contacts.
- SortOrder.BlanksFirst - Considers blank values to evaluate to less than all other values in comparisons.
- SortOrder.BlanksLast - Considers blank values to evaluate to greater than all other values in comparisons.
This property holds the case sensitivity of the sort order, the value can be one of:
- Qt.CaseInsensitive
- Qt.CaseSensitive - (default)
This property holds the detail type of the details which will be inspected to perform sorting.
See also ContactDetail::type.
This property holds the direction of the sort order, the value can be one of:
- Qt.AscendingOrder - (default)
- Qt.DescendingOrder
This property holds the detail field type of the details which will be inspected to perform sorting. For each detail elements, there are predefined field types. | https://phone.docs.ubuntu.com/en/apps/api-qml-development/QtContacts.SortOrder | 2020-10-23T21:15:36 | CC-MAIN-2020-45 | 1603107865665.7 | [] | phone.docs.ubuntu.com |
Working with questions
This example shows a question that expects an answer. The conversation cannot progress until the user chooses one of these 3 answers. These are defined as quick replies (on the Answers tab of the interaction):
This question defines the answers as buttons (on the Answers tab of the interaction):
On the Canvas, answers defined as quick replies and buttons appears as separate elements that are linked to the interaction that owns them and to any directly linked, following interaction:
You can also define answers using any of the predefined types, such as date or email address.
Handling unexpected and unwanted answers
There are several ways of handling unexpected or unwanted answers. For example:
- Handle unexpected answers by setting up a default answer such as That wasn't really what I was expecting. This is part of the bot configuration. See Defining the bot's default responses.
- Handle unwanted answers that you'd like to have a specific response for by setting up an intention. Use a message to send some text in response to the unwanted answer and then link back to the original question. The interactions would look like this:
For further information about this example, see Example: handling unwanted and unexpected answers.
See also
Choosing the type of interaction to use | https://docs.converse.engageone.co/Interactions/overview_questions.html | 2020-10-23T21:22:46 | CC-MAIN-2020-45 | 1603107865665.7 | [array(['../images/example-question2.png', None], dtype=object)
array(['../images/example-question3.png', None], dtype=object)
array(['../images/example-question-with-messages.png', None], dtype=object)
array(['../images/example-question-with-intentions.png', None],
dtype=object) ] | docs.converse.engageone.co |
DashboardExtractDataSource.DriverName Property
Gets or sets a custom driver used to write data to/read data from the current data extract.
Namespace: DevExpress.DashboardCommon
Assembly: DevExpress.Dashboard.v20.1.Core.dll
Declaration
[DefaultValue(null)] [Browsable(false)] public string DriverName { get; set; }
<DefaultValue(Nothing)> <Browsable(False)> Public Property DriverName As String
Property Value
Remarks
By default, the DashboardExtractDataSource stores data within a file. If necessary, you add a custom logic for writing/reading extract data by implementing the ICustomExtractDriver interface. After you have implemented a custom driver, you can use it in two ways.
- To use a custom driver across all data extracts, assign its instance to the ExtractDriverStorage.DefaultDriver property.
- To use a custom driver for the specified data extract, register this driver in the ExtractDriverStorage using the ExtractDriverStorage.RegisterCustomDriver method and assign its name to the DriverName property.
NOTE
Note that the value of DriverName is saved to the dashboard XML definition. This allows you to determine the driver name when opening the dashboard supplied with data using DashboardExtractDataSource with a custom driver.
See Also
Feedback | https://docs.devexpress.com/Dashboard/DevExpress.DashboardCommon.DashboardExtractDataSource.DriverName | 2020-10-23T22:11:49 | CC-MAIN-2020-45 | 1603107865665.7 | [] | docs.devexpress.com |
InstallShield 2019
Project • This information applies to InstallScript projects.
With a single InstallScript project, you can create one installation that installs to 32-bit locations on 32-bit systems, and to 64-bit and 32-bit locations as needed on 64-bit systems.
InstallScript installations are always 32-bit so they can run only 32-bit DLL code (or launch 32-bit or 64-bit .exe files). However, all InstallScript installations support accessing 64-bit locations through the 64-bit component setting, as well as through other methods.
Reading from and Writing to the 64-Bit System32 Folder
InstallScript includes the following system variables that let you choose between 32-bit and 64-bit System32 folders on target systems:
Although the WINSYSDIR64 variable is set to the 64-bit Windows folder, 64-bit Windows includes functionality to automatically redirect 32-bit applications (such as the InstallScript engine) to the 32-bit System32 folder (SysWOW64). Therefore, if you are installing files or folders to WINSYSDIR64, you can disable file system redirection by placing the folders or files constant WOW64FSREDIRECTION with the functions Disable and Enable to disable 64-bit Windows file system redirection while writing to or reading from the WINSYSDIR64 folder through your InstallScript code, and then re-enable it once the write or read is complete. Since some Windows functionality that could be used by the installation requires that redirection be enabled to work, Windows documentation recommends that you disable redirection only for as long as necessary.
Reading from and Writing to Other 64-Bit Destination Folders
InstallScript includes several addition system variables that let you choose between other 32-bit and 64-bit locations on target systems:
Reading from and Writing to 64-Bit Registry Locations
The 64-bit version of Windows includes functionality that maps some 64-bit registry locations to 32-bit equivalents. For example, on a 64-bit version of Windows, HKEY_LOCAL_MACHINE\Software\Wow6432Node is the 32-bit equivalent of HKEY_LOCAL_MACHINE\Software.
If you want to install registry data to a 64-bit area of the registry without having it redirected to a 32-bit area, you can place the registry data REGDB_OPTION_WOW64_64KEY option with the REGDB_OPTIONS variable to avoid registry redirection while editing the registry or reading from the registry through your InstallScript code, and then use the REGDB_OPTION_USE_DEFAULT_OPTIONS option with REGDB_OPTIONS to enable changes to the 32-bit area of the registry. Since some Windows functionality that could be used by the installation requires that redirection be enabled to work, Windows documentation recommends that you disable redirection only for as long as necessary.
Installing Self-Registering 64-Bit COM Servers
InstallShield supports 64-bit self-registration of COM servers. For the component that contains the self-registering DLL, .exe, .tlb, or .olb file, select Yes for the component’s Self-Register setting.
Note that 32-bit self-registering files should not be installed to the 64-bit System32 folder, since file system redirection cannot be disabled for self-registration. Thus, if you have a 32-bit self-registering COM server that needs to be installed to the 32-bit System32 folder, ensure that No is selected for the 64-Bit Component setting of the component that contains the COM server.
About Add or Remove Programs Information
InstallScript installations do not support reading or writing Add or Remove Programs information in the 64-bit part of the registry. Therefore, InstallScript installations always install Add or Remove Programs information in the 32-bit part of the registry. In addition, the REGDB_OPTION_WOW64_64KEY option does not disable registry reflection for registry functions such as CreateInstallationInfo, MaintenanceStart, RegDBGetItem, RegDBSetItem, RegDBGetAppInfo, RegDBSetAppInfo, and RegGetUninstCmdLine.
See Also
Targeting 64-Bit Operating Systems | https://docs.revenera.com/installshield25helplib/helplibrary/Targeting64Bit-IS.htm | 2020-10-23T20:50:51 | CC-MAIN-2020-45 | 1603107865665.7 | [] | docs.revenera.com |
Q：Which version of VeChain Work should I download?
A：VeChain Work supports both iOS and Android systems. Please download and install the following QR code according to your device:
Q：I can not see product information after scanning the QR code.
A：Please confirm whether the product information status corresponding to the product QR code is set as public:
Enter the console- internal project-select the project-create SKU-view the status of SKU
Q：What should I do if I fail to bind SKU by scanning with the Work app?
A：Please make sure you have confirmed the delivery.
Q：What should I do if I fail to log in with my account?
A： Please confirm whether your account is a user account, you can contact your admin to confirm:
The admin can log in to the console, enter【project management】-【user management】and view the account information;
Or confirm whether your account password is correct. If you forget the password, you can contact the admin to reset the password.
Q：What should I do if I fail to see the traceability information after I add it on the Work app?
A：Log in with the user account (who made the operation) into the Work app and enter the operation menu of the project. View the submission record in the upper right corner-confirm whether the submission is successful.
Please sign in to leave a comment. | https://docs.vetoolchain.com/hc/en-us/articles/360040377651-FAQs | 2020-10-23T21:19:47 | CC-MAIN-2020-45 | 1603107865665.7 | [array(['/hc/article_attachments/360068916112/_____2020-09-16___1.52.10.png',
'_____2020-09-16___1.52.10.png'], dtype=object)
array(['/hc/article_attachments/360051024032/image-1.png', None],
dtype=object)
array(['/hc/article_attachments/360051024012/image-2.png', None],
dtype=object)
array(['/hc/article_attachments/360051023992/image-3.png', None],
dtype=object)
array(['/hc/article_attachments/360051124271/image-4.png', None],
dtype=object) ] | docs.vetoolchain.com |
中国語繁体字(traditional)
using UnityEngine;
public class Example : MonoBehaviour { void Start() { //This checks if your computer's operating system is in the Traditional Chinese language if (Application.systemLanguage == SystemLanguage.ChineseTraditional) { //Outputs into console that the system is in Traditional Chinese Debug.Log("This system is in Traditional Chinese. "); } } } | https://docs.unity3d.com/ja/2020.2/ScriptReference/SystemLanguage.ChineseTraditional.html | 2020-10-23T22:12:45 | CC-MAIN-2020-45 | 1603107865665.7 | [] | docs.unity3d.com |
Installation
To install Kentico, run the Kentico_12_0.exe file, which opens the Kentico Installer:
Installing Kentico
Evaluation
You can begin by installing Kentico for evaluation purposes (uses the MVC development model).
Installation for development
Check if your development server meets the recommended configuration.
Install Kentico on your local computer by following our installation guide, either for MVC projects or Portal Engine projects. If you come across any difficulties with selecting the right options, see Installation Questions and Answers for recommendations.
Where to get more information?
To learn how to develop websites, see the Kentico 12 Service Pack Tutorial.
You can also visit our DevNet portal for developers, with articles, forums, a knowledge base and other documentation materials.
If you need advice on how to use Kentico, feel free to contact our support. The support team operates non-stop and will be happy to help you.
Was this page helpful? | https://docs.xperience.io/k12sp/installation | 2020-10-23T21:16:20 | CC-MAIN-2020-45 | 1603107865665.7 | [] | docs.xperience.io |
Configure). Click Submit. Click the test connection link at the bottom to test the SMTP, POP3, or IMAP account.. Note: The address in the From field on the Notification form takes precedent over this field. Password Password when Authentication type is Password. Note: You may need to increase the size of this field to accommodate longer passwords. By default, this field has a size of 40. Enable SSL Enables Secure Socket Layers when connecting to an Email Server. Enable TLS Enables Transport Layer Security when connecting to an Email Server. Port Connection TCP port. | https://docs.servicenow.com/bundle/geneva-servicenow-platform/page/administer/notification/task/t_ConfigureAnEmailAccount.html | 2018-02-17T23:44:26 | CC-MAIN-2018-09 | 1518891808539.63 | [] | docs.servicenow.com |
<![CDATA[ ]]>Production > Drawing and Design > Character Building > Rigging > Creating a Hierarchy
Creating.
Here is a basic rig with pegs example:
| https://docs.toonboom.com/help/harmony-11/workflow-standalone/Content/_CORE/_Workflow/020_Character_Building/043_H2_Creating_a_Hierarchy.html | 2018-02-17T23:10:44 | CC-MAIN-2018-09 | 1518891808539.63 | [array(['../../../Resources/Images/_ICONS/Home_Icon.png', None],
dtype=object)
array(['../../../Resources/Images/HAR/_Skins/stage.png', None],
dtype=object)
array(['../../../../Skins/Default/Stylesheets/Images/transparent.gif',
'Closed'], dtype=object)
array(['../../../Resources/Images/HAR/_Skins/draw.png',
'Toon Boom Harmony 11 Draw Online Documentation'], dtype=object)
array(['../../../../Skins/Default/Stylesheets/Images/transparent.gif',
'Closed'], dtype=object)
array(['../../../Resources/Images/HAR/_Skins/sketch.png', None],
dtype=object)
array(['../../../../Skins/Default/Stylesheets/Images/transparent.gif',
'Closed'], dtype=object)
array(['../../../Resources/Images/HAR/_Skins/controlcenter.png',
'Installation and Control Center Online Documentation Installation and Control Center Online Documentation'],
dtype=object)
array(['../../../../Skins/Default/Stylesheets/Images/transparent.gif',
'Closed'], dtype=object)
array(['../../../Resources/Images/HAR/_Skins/scan.png', None],
dtype=object)
array(['../../../../Skins/Default/Stylesheets/Images/transparent.gif',
'Closed'], dtype=object)
array(['../../../Resources/Images/HAR/_Skins/stagePaint.png', None],
dtype=object)
array(['../../../../Skins/Default/Stylesheets/Images/transparent.gif',
'Closed'], dtype=object)
array(['../../../Resources/Images/HAR/_Skins/stagePlay.png', None],
dtype=object)
array(['../../../../Skins/Default/Stylesheets/Images/transparent.gif',
'Closed'], dtype=object)
array(['../../../Resources/Images/HAR/_Skins/stageXsheet.png', None],
dtype=object)
array(['../../../../Skins/Default/Stylesheets/Images/transparent.gif',
'Closed'], dtype=object)
array(['../../../Resources/Images/HAR/Stage/Breakdown/an_mixrigging.png',
None], dtype=object)
array(['../../../Resources/Images/HAR/Stage/Breakdown/HAR11/HAr11_Body_Rigging_Timeline_Example.png',
None], dtype=object) ] | docs.toonboom.com |
Responsive GUI¶
And now for the hard part of making the widget responsive. We will do this by offloading the learner evaluations into a separate thread.
First read up on threading basics in Qt and in particular the subject of threads and qobjects and how they interact with the Qt’s event loop.
We must also take special care that we can cancel/interrupt our task when the user changes algorithm parameters or removes the widget from the canvas. For that we use a strategy known as cooperative cancellation where we ‘ask’ the pending task to stop executing (in the GUI thread), then in the worker thread periodically check (at known predetermined points) whether we should continue, and if not return early (in our case by raising an exception).
We use
Orange.widgets.utils.concurrent.ThreadExecutor for thread
allocation/management (but could easily replace it with stdlib’s
concurrent.futures.ThreadPoolExecutor).
import concurrent.futures from Orange.widgets.utils.concurrent import ( ThreadExecutor, FutureWatcher, methodinvoke )
We will reorganize our code to make the learner evaluation an explicit task as we will need to track its progress and state. For this we define a Task class.
class Task: """ A class that will hold the state for an learner evaluation. """ #: A concurrent.futures.Future with our (eventual) results. #: The OWLearningCurveC class must fill this field future = ... # type: concurrent.futures.Future #: FutureWatcher. Likewise this will be filled by OWLearningCurveC watcher = ... # type: FutureWatcher #: True if this evaluation has been cancelled. The OWLearningCurveC #: will setup the task execution environment in such a way that this #: field will be checked periodically in the worker thread and cancel #: the computation if so required. In a sense this is the only #: communication channel in the direction from the OWLearningCurve to the #: worker thread cancelled = False # type: bool def cancel(self): """ Cancel the task. Set the `cancelled` field to True and block until the future is done. """ # set cancelled state self.cancelled = True # cancel the future. Note this succeeds only if the execution has # not yet started (see `concurrent.futures.Future.cancel`) .. self.future.cancel() # ... and wait until computation finishes concurrent.futures.wait([self.future])
In the widget’s
__init__ we create an instance of the ThreadExector
and initialize the task field.
#: The current evaluating task (if any) self._task = None # type: Optional[Task] #: An executor we use to submit learner evaluations into a thread pool self._executor = ThreadExecutor()
In handleNewSignals we call _update.
def handleNewSignals(self): self._update()
And finally the _update function that will start/schedule all updates.
def _update(self): if self._task is not None: # First make sure any pending tasks are cancelled. self.cancel() assert self._task is None if self.data is None: return # collect all learners for which results have not yet been computed need_update = [(id, learner) for id, learner in self.learners.items() if self.results[id] is None] if not need_update: return
At the start we cancel pending tasks if they are not yet completed. It is important to do this, we cannot allow the widget to schedule tasks and then just forget about them. Next we make some checks and return early if there is nothing to be done.
Continue by setting up the learner evaluations as a partial function capturing the necessary arguments:
learners = [learner for _, learner in need_update] # setup the learner evaluations as partial function capturing # the necessary arguments. if self.testdata is None: learning_curve_func = partial( learning_curve, learners, self.data, folds=self.folds, proportions=self.curvePoints, ) else: learning_curve_func = partial( learning_curve_with_test_data, learners, self.data, self.testdata, times=self.folds, proportions=self.curvePoints, )
Setup the task state and the communication between the main and worker thread. The only state flowing from the GUI to the worker thread is the task.cancelled field which is a simple trip wire causing the learning_curve’s callback argument to raise an exception. In the other direction we report the percent of work done.
# setup the task state self._task = task = Task() # The learning_curve[_with_test_data] also takes a callback function # to report the progress. We instrument this callback to both invoke # the appropriate slots on this widget for reporting the progress # (in a thread safe manner) and to implement cooperative cancellation. set_progress = methodinvoke(self, "setProgressValue", (float,)) def callback(finished): # check if the task has been cancelled and raise an exception # from within. This 'strategy' can only be used with code that # properly cleans up after itself in the case of an exception # (does not leave any global locks, opened file descriptors, ...) if task.cancelled: raise KeyboardInterrupt() set_progress(finished * 100) # capture the callback in the partial function learning_curve_func = partial(learning_curve_func, callback=callback)
See also
progressBarInit(),
progressBarSet(),
progressBarFinished()
Next, we submit the function to be run in a worker thread and instrument a FutureWatcher instance to notify us when the task completes (via a _task_finished slot).
self.progressBarInit() # Submit the evaluation function to the executor and fill in the # task with the resultant Future. task.future = self._executor.submit(learning_curve_func) # Setup the FutureWatcher to notify us of completion task.watcher = FutureWatcher(task.future) # by using FutureWatcher we ensure `_task_finished` slot will be # called from the main GUI thread by the Qt's event loop task.watcher.done.connect(self._task_finished)
In _task_finished we handle the completed task (either success or failure) and then update the displayed score table.
@pyqtSlot(concurrent.futures.Future) def _task_finished(self, f): """ Parameters ---------- f : Future The future instance holding the result of learner evaluation. """ assert self.thread() is QThread.currentThread() assert self._task is not None assert self._task.future is f assert f.done() self._task = None self.progressBarFinished() try: results = f.result() # type: List[Results] except Exception as ex: # Log the exception with a traceback log = logging.getLogger() log.exception(__name__, exc_info=True) self.error("Exception occurred during evaluation: {!r}" .format(ex)) # clear all results for key in self.results.keys(): self.results[key] = None else: # split the combined result into per learner/model results ... results = [list(Results.split_by_model(p_results)) for p_results in results] # type: List[List[Results]] assert all(len(r.learners) == 1 for r1 in results for r in r1) assert len(results) == len(self.curvePoints) learners = [r.learners[0] for r in results[0]] learner_id = {learner: id_ for id_, learner in self.learners.items()} # ... and update self.results for i, learner in enumerate(learners): id_ = learner_id[learner] self.results[id_] = [p_results[i] for p_results in results]
Also of interest is the cancel method. Note that we also disconnect the _task_finished slot so that _task_finished does not receive stale results.
def cancel(self): """ Cancel the current task (if any). """ if self._task is not None: self._task.cancel() assert self._task.future.done() # disconnect the `_task_finished` slot self._task.watcher.done.disconnect(self._task_finished) self._task = None
We also use cancel in
onDeleteWidget()
to stop if/when the widget is removed from the canvas.
def onDeleteWidget(self): self.cancel() super().onDeleteWidget() | http://orange-development.readthedocs.io/tutorial-responsive-gui.html | 2018-02-17T23:11:48 | CC-MAIN-2018-09 | 1518891808539.63 | [] | orange-development.readthedocs.io |
Choosing which hard drives and folders to back up
Applies To: Windows SBS 2008
Windows Home Server automatically backs up the client computers daily. But if you add or remove a hard drive from a client computer, you need to inform Windows Home Server of the change. You can also exclude certain folders from being backed up.
To choose which hard drives and folders to back up
On the client computer, in the notification area, right-click the Windows Home Server icon to display the Windows Home Server console.
Select the client computer.
On the Computers & Backup tab, click Configure Backup.
On the Welcome to Backup Configuration Wizard page, click Next.
On the Choose Volumes to Back Up page, select the volumes and hard drives that you want to back up, clear the ones that you do not want to back up, and then click Next.
On the Choose Folders to Exclude from Backup page, click Add, and then browse to the folder that you do not want to back up.
Click the folder, and then click Exclude.
On the Choose Folders to Exclude from Backup page, click Next, and then finish the wizard. | https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-essentials/ee378519(v=ws.10) | 2018-02-17T23:33:21 | CC-MAIN-2018-09 | 1518891808539.63 | [] | docs.microsoft.com |
Phone number management for Spain
Use this table to find information on getting and managing phone numbers in Spain for Skype for Business Online and Microsoft Teams.
For more information, see Manage phone numbers for your organization.
Related topics
Different kinds of phone numbers used for Calling Plans
Manage phone numbers for your organization
Emergency calling terms and conditions
Skype for Business Online: Emergency Calling disclaimer label | https://docs.microsoft.com/en-us/SkypeForBusiness/what-are-calling-plans-in-office-365/manage-phone-numbers-for-your-organization/phone-number-management-for-spain?ui=zh-CN&rs=zh-CN&ad=CN | 2018-02-18T00:20:54 | CC-MAIN-2018-09 | 1518891808539.63 | [] | docs.microsoft.com |
The Object Storage services (swift) work together to provide object storage and retrieval through a REST API.
Your environment must at least include the Identity service (keystone) prior to deploying Object Storage.
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents. | https://docs.openstack.org/mitaka/install-guide-ubuntu/swift.html | 2018-02-17T23:05:33 | CC-MAIN-2018-09 | 1518891808539.63 | [] | docs.openstack.org |
Commonly Used Properties
RadGridView
GridViewTableElement
The following table list the properties exposed by RadGridView.TableElement:
Methods
Begin/End Update
The Begin/End Update block should be used when a repeated operation that affects grid layout is performed several times. This block will suspend the grid layout and it will be updated only once when the EndUpdate method is called. An example is available here | https://docs.telerik.com/devtools/winforms/gridview/common-properties | 2018-02-17T23:41:01 | CC-MAIN-2018-09 | 1518891808539.63 | [] | docs.telerik.com |
You are viewing documentation for version 2 of the AWS SDK for Ruby. Version 3 documentation can be found here.
Exception: Aws::States::Errors::ActivityLimitExceeded
- Inherits:
- ServiceError
- Object
- RuntimeError
- Errors::ServiceError
- ServiceError
- Aws::States::Errors::ActivityLimitExceeded
- Defined in:
- (unknown)
Instance Attribute Summary
Attributes inherited from Errors::ServiceError
Method Summary
Methods inherited from Errors::ServiceError
Constructor Details
This class inherits a constructor from Aws::Errors::ServiceError | https://docs.aws.amazon.com/sdkforruby/api/Aws/States/Errors/ActivityLimitExceeded.html | 2018-02-17T23:56:32 | CC-MAIN-2018-09 | 1518891808539.63 | [] | docs.aws.amazon.com |
Legacy Documentation
You are using the documentation for version 3.5.15. Go here for the latest version or check here for your available upgrades to ExpressionEngine 4.
ExpressionEngine 3.x Change Log¶
- Version 3.5.15
- Version 3.5.14
- Version 3.5.13
- Version 3.5.12
- Version 3.5.11
- Version 3.5.10
- Version 3.5.9
- Version 3.5.8
- Version 3.5.7
- Version 3.5.6
- Version 3.5.5
- Version 3.5.4
- Version 3.5.3
- Version 3.5.2
- Version 3.5.1
- Version 3.5.0
- Version 3.4.7
- Version 3.4.6
- Version 3.4.5
- Version 3.4.4
- Version 3.4.3
- Version 3.4.2
- Version 3.4.1
- Version 3.4.0
- Version 3.3.4
- Version 3.3.3
- Version 3.3.2
- Version 3.3.1
- Version 3.3.0
- Version 3.2.1
- Version 3.2.0
- Version 3.1.4
- Version 3.1.3
- Version 3.1.2
- Version 3.1.1
- Version 3.1.0
- Version 3.0.6
- Version 3.0.5
- Version 3.0.4
- Version 3.0.3
- Version 3.0.2
- Version 3.0.1
- Version 3.0.0
Version 3.5.15¶
Release Date: January 24, 2018
Fixed a bug where validation did not force selecting an heir when deleting a member and ‘Reassign’ entries was selecting, which could result in data loss.
Version 3.5.14¶
Release Date: December 15, 2017
- 3.5.13¶
Release Date: December 13, 2017
Important
This release marks the last normal patch update for ExpressionEngine 3. With the release of ExpressionEngine 4, v3 is now Legacy software and will only receive critical bug fixes such as security patches and protections against dataloss, for one year. Please consider upgrading.
- 🔒 & 🏎
- Added PHP 7.2 compatibility.
- Fixed a potential stored XSS bug in the control panel.
- Increased security against potential environment information leakage.
- Fixed a bug (#23281) where a PHP error could be thrown by a non-functional filter in the Pages module control panel.
Version 3.5.12¶
Release Date: November 3, 2017
- Important:
- 🗑🔒‼️ If you are using the Site Manager and are planning on deleting a Site, make certain to update to version 3.5.12 first: Fixed a bug (#23266) where member group setting assignments were lost when a Site was deleted.
- Loosened the redirect warning for external links in the control panel to allow redirects to all subdomains.
- Optimized a query used in the category archive tag.
- Updated the developer documentation regarding the legacy Output class (#23215).
- Fixed a bug (#23218) where the live look template view button went on holiday (it took all the colors from the custom statuses too!).
- Fixed a bug (#21743) where date fields belligerently remained localized.
- Fixed a bug (#23253) where you could not edit entries that have existing content in the Discussion Forum tab.
- Fixed a bug (#23265) where guest Channel Forms could white screen (fatal PHP error) in certain circumstances.
- Fixed a bug in the forum module where permission to upload settings did not always stick.
- Fixed a bug in the forum module where you could not uncheck all permission checkboxes and have it stick.
- Fixed a bug where the control panel log didn’t have enough room to save a valid username.
- Fixed a bug in the forum where the visitor statistics section did not appear.
- Fixed a bug (#23191) in the control panel entry search where quoted searches failed.
- Fixed some incorrect DocBlocks (#23245).
- Fixed a bug (#23236) where channel sets used the channel title instead of the channel short name.
- Fixed a bug where when a member group left town it left some if its things behind.
- Developers:
- Added a URL_TITLE_MAX_LENGTH constant.
Version 3.5.11¶
Release Date: August 24, 2017
- Optimized the entry manager for speed.
- Restored check for banned email addresses when registering/updating a member record.
- Added per page filter to a number of tables in the control panel.
- Altered the AJAX response headers to accomidate IE’s JSON ignorance.
- Fixed a bug where clearing out a File field may fire off numerous form validation AJAX requests.
- Fixed a bug (#23171) where the template parser got overwhelemd with really large templates and found a happy place instead of doing work.
- Fixed a bug where trying to automatically resize SVG files would throw an error.
- Fixed a display issue with abstracted Extension settings when there are many checkboxes/multi-select options.
- Fixed a bug where abstracted Extension settings items could not have field instructions.
- Fixed a bug (#23174) where Simple Commerce emails did not respect the Mail Format email preference, preventing it from being able to send HTML emails.
- Fixed a bug where setting PHP memory in gigabytes setting could result in memory errors when uploading.
- Fixed a bug (#22741) in the installer where the superadmin user created during installation was assumed to have a member_id of 1. We all know what they say about assumptions, don’t we?
- Fixed a bug where the list of addons in the member group permissions included some non-addons.
- Fixed a bug (#23183) where the template create button did not show on the template manager page for some member groups with permission to create templates.
- Fixed a bug where saving templates when caching was disabled caused an error.
- Fixed a bug where thumbnails were not removed when deleting a file record with a missing file.
- Fixed a bug (#23181) where it was not possible to delete the last row in a grid field when editing via the channel entry form.
- Fixed a bug (#23195) where third party fieldtypes could not be uninstalled if the file name wasn’t standard issue.
- Fixed a bug in the forum settings where you couldn’t manage moderator notifications.
- Developers:
- Fixed a bug (#21702) where the legacy file model’s
ee()->file_model->delete_files($Id);would show a system error if deleting a record that has a missing image file and fail to delete any stray thumbnails.
- Fixed a bug (#23207) where the legacy form validation error for too short passwords didn’t display the required password length properly.
Version 3.5.10¶
Release Date: June 27, 2017
- Security Fixes
- Fixed a potential reflected XSS issue.
- Fixed a potential issue that could lead to arbitrary execution of ExpressionEngine tags.
- Optimized Relationship control panel display query.
- Fixed a missing language key in the member module.
- Fixed a bug (#23133) where images could not be resized proportionally in the File Manager.
- Fixed a bug (#23157) where saving a channel entry may attempt to assign categories twice.
- Fixed a bug (#23160) where member groups without member deletion permissions may see an error in the control panel.
- Fixed a bug where
{current_url}and
{current_path}were entirely unencoded.
Version 3.5.9¶
Release Date: June 16, 2017
- Improved the display of long filenames in grid fields.
- Fixed a bug (#23153) where manually-sorted multi-relationship fields may not appear sorted correctly on the front-end.
Version 3.5.8¶
Release Date: June 15, 2017
- Security Fixes (thanks again to Mustafa Hasan from HackerOne!):
- Eliminated a couple areas that could disclose the full server path.
- Fixed a potential remote code execution issue (identified by Erik McClements).
- Improved XSS protection in a few areas of the control panel.
- Tightened off-site redirect protection / warning.
- Optimized entry saving on installations with large numbers of categories.
- Optimized {category_menu} tag parsing in the channel entry form.
- Modified upload filename sanitization so that numeric segments are no longer suffixed with an underscore.
- Channel Form’s Grid CSS jumped the starting block. It has been reset and issued a warning.
- Fixed a syntax error in compressed Channel Form JavaScript introduced in 3.5.7.
- Added a crossing guard to prevent PHP errors from entering traffic when the Pages module references non-existent entries.
- Added some extra no cache headers for Chrome so it would stop trying to server the CSRF token from cache.
- Fixed a bug (#23125) where the Pages module did not have a nested view.
- Fixed a bug (#23119) where the Relationship field filter would not work unless the member has access to the Relationship module.
- Fixed a bug (#23098) where sticky entries were not sticky in Relationship field output.
- Fixed a bug (#23111) where permissions to send email to member groups and to view the email cache could not be set.
- Fixed a bug (#23106) where the date picker may appear blank in Firefox.
- Fixed a bug (#23108) where selecting a category for an entry in Channel Form would not automatically assign its parents to the entry.
- Fixed a bug (#23097) where third-party RTE tools would not be loaded.
- Fixed a bug (#23136) where the maximum file size field description incorrectly said megabytes instead of kilobytes.
- Fixed a bug (#23132) where value/label pairs could not be used in member fields.
- Fixed a bug (#23131) where templates could not be deleted from the template manager search results screen.
- Fixed a bug (#23148) with grid column widths; some wanted a percentage!
- Fixed a bug (#23118) where the 3.1.0 updater was checking if a variable exists after using it. Impulse control!
- (#23115) Open/Closed statuses now respect your language pack’s translation in the Entry Manager.
Version 3.5.7¶
Release Date: May 18, 2017
- Fixed a bug (#23080) where the File Manager may have performance problems for non-super admins when many member groups and upload folders are present.
- Fixed a bug (#23076) where slashes could not be saved in extension settings.
- Fixed a bug (#23053) where
liveUrlTitle()may not work when multiple Channel Forms are present.
- Fixed a bug where the template parser would be unable to parse a large number of global variables.
- Fixed a bug where an entry’s year, month and day fields could be saved as 0 when using dd/mm/yyyy localization.
- If a Channel is limited to 1 entry, and 1 entry already exists, the Edit menu will take you straight to edit that entry for simplicity. Automated tests for the win.
- Grid fields now respect assigned column widths.
- Simplified a query in the RSS module that was necessary in versions < 1.4.0. No typo.
- Fixed a bug where comment expiration date field was visible when a channel allows comments, but comments are disabled at the system level.
- Fixed a bug (#23090) where the edit category modal on the Publish page would not properly close and reflect a successful edit.
- Fixed a bug where member accept and decline notifications did not always respect the control panel settings.
- Fixed a bug where the frontend member profile email console pop-up did not display properly.
- Fixed a bug where the control panel login could improperly redirect if a custom homepage was set but no URL was entered.
Version 3.5.6¶
Release Date: April 13, 2017
- Fixed a bug where floating point numbers could not be used in queries.
- Fixed a bug where the Rich Text Editor field did not honor the required setting.
- Fixed an issue where enabling Gzip compression would prevent front-end pages with PHP errors from rendering in most browsers.
- Improved memory footprint of the control panel homepage when a site has thousands of Banned members.
<cite>is now allowed in Channel Entry titles.
- Fixed an issue in the control panel where the banned member page and pending member page searches included all members.
Version 3.5.5¶
Release Date: April 10, 2017
- Security Fixes:
- Mitigated a potential remote code execution vulnerability.
- Improved cryptographic security when pseudo-random numbers are used.
- Further hardened protections against SQL injection.
- Option fields (select, multiselect, radio, and checkboxes) can now have one blank value.
- Channels who have no more room for entries will not show under the Create menu.
- The uncommon “Disallowed Key Characters” error will now reveal which input key was blocked when
$debugis set to
1in your
index.phpand
admin.phpfiles.
- Improved performance of categories in Channel Form new entry forms when massive numbers of categories are involved.
- Fixed a bug (#23040) causing a Notice-level PHP error in Channels with Versioning enabled on first-save.
- Fixed a bug where an Ajax call was being made to update the order of categories when it should not have.
- Fixed a bug (#22894) where removing a category group from a channel may cause category groups not to be reorderable in the layout editor.
- Fixed a bug (#23021) where avatar upload and selection might not work on some multi-site installs.
- Fixed a bug (#23020) where visiting the control panel with no URI segments upon already being logged in would not redirect you to your preferred homepage.
- Fixed a bug (#23029) where using a Relationship shortcut tag inside a Grid tag pair would not parse when it was the only Relationship field in the channel.
- Fixed a bug where the
{date_header}and
{date_footer}template variables did not work inside Relationships.
- Fixed a bug (#22389) where multiple Channel Forms on single page may not work.
- Fixed a bug (#23044) where an “Unable to load the requested file” error may appear when editing a custom field.
- Fixed a bug in the forum templates where editing your member profile preferences was not allowed on the frontend. See the version notes for details.
- Developers:
- Fixed a bug where the Curl service could not send parameters along with POST requests.
Version 3.5.4¶
Release Date: March 16, 2017
- Important:
- 🗑🔒‼️ Fixed a potential data loss issue when deleting admins who have edited templates.
- Browsers will (mostly) now be tricked into not autofilling password setting fields (e.g. SMTP username & password) in the control panel with your password, even if the browser’s autofill is enabled. Commence fist shaking at browser vendors for their algorithms that try to guess those fields and not providing a reliable way to prevent it. Developers: If you are using the Shared Form View, your inputs with
type="password"will automatically benefit.
- Improved the clarity of an error message if something goes wrong with your site preferences in the database.
- Improved breadcrumb clarity when editing fields in the Channel Manager.
- Made the Status Groups UI consistent with other areas of the Channel Manager.
- Modified the Redirect library that handles links from the control panel to external sites to be ok with URLs with query string parameters.
- Fixed a bug where parsing category fields may show a PHP error.
- Fixed a bug (#22993) where the RTE field may not show underlined text properly in the publish field.
- Fixed a bug (#23005) where Relationship field filtering on the publish may not work if editing an MSM site with a different domain than the control panel.
- Fixed a bug (#22419) where the
:total_resultsshortcut relationship variable would return the wrong count when used inside Grid.
- Fixed a bug (#22789) where deleting a channel entry with a comment would trigger PHP errors.
- Fixed a bug where children were overlooked while some deeply nested relationships were partying with grids.
- The new View Activity won’t try to hoodwink you into thinking other members are stalking you, or that so many significant events occurred at the start of the Unix Epoch.
- Fixed a PHP error that would occur when trying to destructively overwrite non-image files on upload.
- Trying to edit a field group that doesn’t exist now 404s instead of complaining in an unhelpful manner with PHP warnings.
- Fixed a bug where default HTML buttons were not always added to the correct site when adding new buttons.
- Fixed a bug where entry revisions could be duplicated and entry revision pruning did not obey the max revision setting.
- Fixed a bug where pagination limits weren’t applied to banned and pending memeber pages in the control panel.
- Developers:
- Fixed a bug in the
cp_js_endhook where you could not use the CP/URL Service.
Version 3.5.3¶
Release Date: March 1, 2017
- Security
- Eliminated a timing attack opportunity.
- Added “View Activity” section to Member Profile administration page, along with prominent email and IP address.
- Added more helpful error message for when an add-on hasn’t specified a namespace (bug #22948).
- Importing a Channel Set with an uninstalled fieldtype will alert you to install it before the set can be imported.
- Improved file uploads to allow for overwriting of files!
- Really added a search_id parameter to the search module tags.
- The URL title generated by
unique_url_title=in Channel Form will have the unique ID separated by the URL separator and will trim the URL title length to 200 characters.
- Tweaked legacy view file loader to ignore the php.ini short_open_tag setting for PHP 5.4+.
- Fixed a bug (#20783) where saving a Grid field with searchable data would show an error in third-party content types.
- Fixed a bug (#21778) where the statistics module did not return data when hit tracking was disabled.
- Fixed a bug (#22936) where outputting image manipulation heights and widths in a template could output a decimal number for certain image dimensions.
- Fixed a bug (#22950) where the a Select All checkbox on a multi-select-style field would not work.
- Fixed a bug (#22956) where saving a Grid option fieldtype column with no value/label pairs set may show an error on the publish form.
- Fixed a bug (#22959) where there was no validation for channel field short name length.
- Fixed a bug (#22960) where a file field associated with a non-existent upload directory would show PHP errors.
- Fixed a bug (#22961) where saving an entry while the Manage Category controls were activated would cause the entry to lose Category associations.
- Fixed a bug (#22964) where you could only 100 entries could be deleted at a time from the entries listing.
- Fixed a bug (#22967) where Toggle fields in Grids were not respecting their default value.
- Fixed a bug (#22969) where the file field would not show thumbnails for SVG files.
- Fixed a bug (#22975) where URLs added to the menu via the
cp_custom_menuhook may double-up on session IDs.
- Fixed a bug (#22978) where SimplePie may show a PHP error when throwing an exception.
- Fixed a bug (#22981) where the Create New link in Relationship fields would not open the publish form in a new window.
- Fixed a bug (#22982) where there was a broken link to create email templates in Simple Commerce.
- Fixed a bug in the 3.0.1 update where a PHP error could occur if orphaned layouts existed.
- Fixed a bug in the 3.5.0 update routine where the new
email_smtp_cryptosettings might not be copied to all sites in the Site Manager, resulting in PHP warnings until the Email settings are saved in each Site.
- Fixed a bug in the Simple Commerce module where saving the settings could throw a PHP error.
- Fixed a bug in the forum module where admin notifications for new topics were switched with the notification emails for topic replies.
- Fixed a bug where
show_message()may output an unencoded URL.
- Fixed a bug where a PHP error could occur changing a user’s member group on the profile page on PHP < 5.4.
- Fixed a bug where custom member and category fields allowed reserved words for their short names.
- Fixed a bug where one could not save existing Grid or Relationship fields in environments with improper PDO configuration.
- Fixed a bug where the Manage Categories would not toggle off if there was a custom Toggle field on the publish form.
- Fixed a bug where the View link in top navigation for MSM played favorites and only linked to Site #1.
- Fixed a bug where the password reset tokens could expire too soon depending on the server_offset config.
- Fixed a regression from 2.x where the template parser might leave markers in place with nested plugins.
Version 3.5.2¶
Release Date: February 2, 2017
- Fixed a security bug where some path names were not properly sanitized.
- Fixed a security bug involving PHP object injection.
- Fixed a bug (#22882) where one could not delete a forum category.
- Fixed a bug (#22883) where saving an existing entry would not highlight its row in the entries table.
- Fixed a bug (#22888) where saving a new channel field set to be hidden would not be collapsed on the publish form.
- Fixed a bug (#22902) where Channel Sets that contain fields with value/label pairs would not import correctly.
- Fixed a bug (#22901) where changing your password due to admin password requirements would not update the account’s password.
- Fixed a bug where fieldtypes in Grid may not parse using the configured field format.
- Fixed a bug (#22905) where a multi-relationship field in Channel Form would try to use the field’s control panel UI.
- Fixed a bug (#22908) where upgrading from a pre-2.7 installation may truncate some channel data columns if they aren’t set as
text.
- Fixed a bug (#22914) where the FTP library’s
delete_dir()may fail.
- Fixed a bug when decrypting old values using the default key.
- Removed the profiler from the CP login page.
- Clarified the language for the authenticate and save actions.
- Fixed a bug where non-ExpressionEngine cookies were run through security checks when the cookie prefix was not explicitly set.
- Fixed a bug where the channel form Allow Comments field did not respect the default in the channel settings.
- Fixed a bug where a PHP error could occur on the CP Overview page when RSS feeds contained code blocks under PHP 5.3.
- Developers:
- Fixed a bug where the post_save_settings event could fire on a fieldtype when an entry was saved.
Version 3.5.1¶
Release Date: January 20, 2017
- Improved security of the Encrypt Service to protect against man-in-the-middle attacks.
- Value/Label pairs can now be used in custom member and category fields.
- Changed the file field to display directories alphabetically in the directory select dropdown on the field settings page.
- Removed the requirement for specifying a replacement value in the search and replace utility.
- Channel form URL title creation now matches the publish page behavior, creating lower case titles by default.
- Ever get the login modal in the CP but you were sure you checked “remember me” when you logged in? We fixed that.
- Fixed a bug where the Loader class may sometimes show an error about a non-numeric value under PHP 7.1.
- Fixed a bug where the updater may show an error if certain add-ons are installed.
- Fixed a bug (#22893) where new template routes could not be added.
- Fixed a bug (#22886) where unchecking the
stickyor
allow_commentscheckboxes in Channel Form would not apply the change.
- Fixed a bug where data encrypted in older versions of ExpressionEngine would not decrypt without using the specific algorithm-method it was originally encrypted with.
- Fixed a bug (#22880) where Channel Sets didn’t export upload destinations for file fields in a Grid.
- Fixed a bug where validation could fail when adding a new member in the control panel due to a field playing hide-and-seek, but not playing fair.
- Fixed a display issue with the new File Field UI with long filenames/titles.
- Fixed a bug in the control panel where the member profile delete member confirmation modal included invalid members in the list of members to reassign entries to.
Version 3.5.0¶
Release Date: January 16, 2017
- Added PHP 7.1 compatibility.
- Added value/label option capability to Checkboxes, Radio Buttons, Select, Multiselect
- Added
{if has_categories}conditional to the Channel Entries tag.
- Added
{category_count},
{category_reverse_count}, and
{category_total_results}variables to the Channel Entries
{categories}{/categories}variable pair.
- Added
entry_id=and
url_title=parameters to the Related Categories Mode of the Channel Entries Tag, to enable this tag to function with custom template routing.
- The
{redirect=}variable can now take full URLs, including external URLs instead of just path segments.
- Usernames and screen names now have a maximum length of 75 characters.
- Improved clarity and usability of File field interface.
- Greatly improved model query performance.
- The
{category_name}variable is now run through typography parsing for pretty quotes and dashes.
- Updated the SimplePie parser version used by the RSS parser to 1.4.3.
- Members must verify themselves when creating a member with control panel access.
- Added Email Newline and Connection Type to Outgoing Email Settings, to simplify configuration with some email providers (formerly available as config overrides only,
- Discussion Forums:
- Updated code sample formatting to use the new styleable blocks. Highlight/Prism/Rainbow/etc. your code samples in forum posts.
- Made special forum conditionals nestable.
- Added
{forum_id}variable to the Thread Rows partial.
- Added
{if is_moderator}conditionals to Threads and Thread Rows partials.
- Added
{topic_date}variable to Threads partial.
- Added
{topic_class}variable to Topic Rows partial.
- Made Poll data available to Thread Rows, so polls can be shown inline with the author’s post.
- Fixed a bug where models could not set NULL values.
- Fixed a bug where model foreign key changes did not trigger reloads.
- Fixed a bug (#20308) where you could only upload the same file name 99 times. Upload as many as you want!
- Fixed a bug on the control panel profile section’s ban members page where a MySQL error occurred when searching banned members.
- Fixed an Obscurum Insectum when
mbstring.func_overloadis enabled, entry content contains multibyte characters, and there is a relationship field with no relationships set.
- Fixed a bug (#22864) where members registering via the Member module could not register if secure passwords were required.
- Fixed a bug (#22865) where if a high minimum username or password length was set, the validation error message would not show the configuration value correctly.
- Fixed a bug (#22867) where deleting a category from the publish screen would uncheck any existing category selections for that entry.
- Fixed a bug (#22872) where changing Channels fields from one type to another may destroy data.
- Fixed a bug (#22869) where repeated searches in the template manager may show a “Request-URI Too Large” error.
- Fixed a bug (#22874) where File fields may show an “Undefined index” error on the front end in rare cases.
- Fixed a bug (#22875) where URL titles generated by Channel Form’s
unique_url_title=parameter did not respect the
word_separatorpreference.
- Fixed a bug (#22876) where the wrong member was marked as the author for entry revisions.
- Fixed a bug (#22873) where having a
:total_rowsGrid modifier in a conditional in a template may show an error when certain add-ons are present.
- Fixed a bug where Channel entry titles that had a
;show up to the party uninvited, when an
&was in the title. No longer: Channel entries titles are by invitation only.
- Altered frontend system message redirects to default to use a JavaScript redirect in order to accommodate a rare IE form submission quirk.
- Worked around a Safari bug where searching for entries in the control panel with autofill enabled on a site using SSL would repeatedly select the text in the textbox.
- Developers:
- Added an Encrypt service that uses OpenSSL for encryption, as Mcrypt has ben deprecated as of PHP 7.1.
- Added
core_boothook to run tasks on every ExpressionEngine request.
- Added request caching to member field model structure to eliminate duplicate queries for some operations.
Version 3.4.7¶
Release Date: December 30, 2016
- Security
- Hardened security in the Email library, prevents attacks similar to PHPMailer CVE-2016-10033, CVE-2016-10045, and Swift Mailer CVE-2016-10074.
- Optimized an inefficient query in the file model.
- Fixed a bug where the
unique_url_title=title parameter was not working in Channel Form.
- Fixed a bug (#22838) where the HTML Button creation form would show a PHP error if no other HTML buttons existed.
- Fixed a bug where switching MSM sites may show a PHP error if the member is set to redirect to the publish form but no Channel is set.
- Fixed a bug (#22841) where deleting a member from their profile page would not give an option to reassign their entries.
- Fixed a bug (#22849) where deleting a member would also delete any files they had uploaded.
- Fixed a bug (#22842) where the author would have to focus the URL title field to validate the field despite it being autofilled by the Title field.
- Fixed a bug (#22013) where if saving Grid settings failed due to duplicate column labels/names, deleting the offending column would not clear the validation errors.
- Fixed a bug (#22858) where statuses on the publish form were not displayed in their set status order.
Version 3.4.6¶
Release Date: December 13, 2016
- Fixed a bug (#22785) where the parsing a template may show an undefined index error in rare cases.
- Fixed a bug (#22798) where RTE tool buttons may appear multiple times when rendered via Channel Form.
- Fixed a bug (#22799) where all “unauthorized” error messages came with a 500 status code instead of a 403.
- Fixed a bug (#22803) where an alternate MySQL port number entered in the installer would not get written to the config.php file.
- Fixed a bug (#22811) where there was a typo in a language key.
- Fixed a bug (#22813) where the
relationships_display_field_optionshook was passed invalid arguments.
- Fixed a bug (#22814) where deleting a member from their profile page may show a PHP error.
- Fixed a bug (#22816) where the Relationship fields could not be filtered when filtering from more than nine channels.
- Fixed a bug (#22817) where Grid and Relationship field data was not revisioned.
- Fixed a bug (#22818) where channel form inline errors for custom fields didn’t display.
- Fixed an issue where the Add-on Manager would be empty on some servers by accommodating an issue (#22819) with incorrectly typed variables from the database on environments with improper/non-standard PDO configuration.
- Fixed a bug where the updater may attempt to add the same database column more than once.
Version 3.4.5¶
Release Date: December 6, 2016
- Added a link to the Multiple Site Manager in the site switcher menu.
- Added
autocomplete="off"to all password fields in the control panel.
- Added clickjacking prevention to the URL redirect warning page.
- Improved performance of and fixed various issues filtering Relationship fields on the publish form.
- Improved accuracy of error message with File fields in Channel Form.
- Fixed a bug (#22754) where the SQL manager could not sort by table disk size.
- Fixed a bug (#22721) where the Redirect library may mistakenly think a protocol-relative URL was malicious.
- Fixed a bug (#22720) where the add-ons list in the control panel was not filtered by member access for non-Super Admins.
- Fixed a bug (#22736) where running the updater with templates saved as files may show an error.
- Fixed bugs (#22427 & #22080) where Channel Form would not allow setting of certain fields, and would eat global variables.
- Fixed a bug (#22766) where Channels that have reached their maximum entry limit may not be able to edit existing entries.
- Fixed a bug (#22761) where certain settings in the member profile would appear unsaved.
- Fixed a bug (#22030) where entry revisions were created regardless of Channel preference.
- Fixed a bug (#22089) where editing checkbox fields in Channel Form that were populated by another channel field would not show their checked status.
- Fixed a bug (#22007) where setting the ID parameter on a Channel Form would cause the date picker not to initialize.
- Fixed a bug where member notification emails were always sent in plain text regardless of the mail format setting.
- Fixed a bug where links bound with the FilePicker may have their callback overwritten with a default callback.
- Fixed a bug (#22755) where editing an entry with a Relationship field may show its entry choices in the wrong order.
- Fixed a bug (#22756) where deselecting an entry in a single Relationship field may re-select the entry upon filtering.
- Fixed a bug (#22053) where saving a
ChannelEntrymodel with properties initialized in the
make()method would show an error.
- Fixed a bug (#22008) where the
category=parameter did not work in Channel Form.
- Fixed a bug (#21999) where setting the field group or status group to None when editing a Channel would not stick.
- Fixed a bug (#22777) where the settings forms with date localization settings may show an error under PHP 7.1.
- Fixed a bug (#22768) where rendering an empty file field with a variable pair would replace its
{url}variable with the author’s URL.
- Fixed a bug (#22795) where the saving template partials may show an invalid language key on the button while saving.
- Fixed a bug where selecting a channel when creating a new bookmarklet would not update the channel field dropdown.
- Fixed a bug (#22796) bookmarklets could not set content for more than one custom field via query string manipulation.
- Fixed a bug (#21721) where editing a URL title in an entry to change its case would show a validation error.
- Fixed a bug (#22797) where deleting a quicklink sometimes would not work.
- Fixed a bug (#21590) where custom field variable pairs could not be parsed in Channel Form.
- Fixed a bug (#21492) where the
show=parameter was not working for the
{categories}tag pair in Channel Form.
- Fixed a bug (#22024) where switching to an MSM site in the control panel would not respect the member’s CP homepage setting.
- Fixed a bug (#22798) where the
{entry_date}variable may always show the current date in Channel Form.
- Fixed a bug (#22798) where the the
use_live_url=parameter would not work in Channel Form.
- Fixed a bug on the control panel profile section’s ban members page where a MySQL error occurred when searching banned members.
- Fixed a security issue in the Email module.
- Fixed a bug where Super Admins could not edit Channel Form entries authored by others when
author_only=was used.
- Fixed a potential bug with Channel Form with Site Manager when sites have identically named Channels.
- Fixed a bug where editing the system offline and user message page templates might truncate the closing body and html tags.
- Fixed the template order in the Channel settings Live Look drop-down. Straighten up!
- Fixed a bug where editing the system offline and user message page templates might truncate the closing body and html tags.
- Fixed a bug where bulk email sending from the Communicate page would overzealously try to send to more recipients than existed.
- Fixed the sum of the Batch emails from the Communicate page. (We love you forever, Roman Moroni.)
- Fixed a bug where you could not change an existing Channel Field from File to third-party field types with
filecompatibility.
Version 3.4.4¶
Release Date: October 27, 2016
- Added a search_id parameter to the search module tags to allow non-standard URLs to function properly (see bug #22411).
- Clarified language of the “Allow multiple logins?” Security setting (including changing to “Allow multiple sessions?”).
- Fixed a bug (#21610) where deleting a Forum would show PHP errors.
- Fixed a bug (#21747) where deleting a custom field would show a PHP error in some environments.
- Fixed a bug (#22021) where actions could not be taken on items in the Spam module.
- Fixed a bug (#22026) where the legacy channel entries API was saving the
edit_datein the wrong format.
- Fixed a bug (#22037) where some modules weren’t updating their version numbers upon update.
- Fixed a bug (#22039) where editing a menu set link would change the link’s order in the set.
- Fixed a bug (#22049) where changing the field group of a channel with a saved layout would append new fields to the Categories tab.
- Fixed a bug (#22112) where the translation utility showed the wrong value on the left.
- Fixed a bug (#22383) where deleting and then adding the same template route before saving could not be done.
- Fixed a bug (#22412) where assigned channels on member groups may be bypassed.
- Fixed a bug (#22421) where deleting a channel entry would call
save()on module publish tabs.
- Fixed a bug (#22422) where the {base_path} variable was not being parsed in the Black/White List module.
- Fixed a bug (#22425) where automatic URL title generation for categories did not include the foreign characters array.
- Fixed a bug (#22707) where clicking the Save button after editing a form with a success alert may cause the form to shift and the button not to be clicked.
- Fixed a bug (#22711) where a non-existant language key was used on a control panel member profile form.
- Fixed a bug (#22717) where comment-editing JavaScript would not allow other events to be bound to its links.
- Fixed a bug (#22722) where an admin logging in as another member when “Allow multiple sessions?” is disabled would result in a PHP error.
- Fixed a bug (#22724) where file upload options were not always correct for non-superadmins in the file manager.
- Fixed a bug (#22725) where cloning a Grid column would not carry over checkbox values in some browsers.
- Fixed a bug (#22726) where some fieldtypes may show PHP errors when used in non-channel content types.
- Fixed a bug where Default Category Channel pref was not being respected in the channel entry form.
- Fixed a bug where Member custom fields were not available on the Memberlist member theme template.
- Fixed a bug where PDO was returning the wrong data types for some columns.
- Fixed a bug where channel forms using the site parameter did not display properly in layouts if there were no results.
- Fixed a bug where deleting a category group assigned to a channel that has multiple category groups would cause errors when publishing.
- Fixed a bug where field creation via the Member Importer would not create all necessary columns in the
member_datatable.
- Fixed a bug where invalid
category/category-namesin the URL did not throw
{if no_results}. These requests will now 404 ftw.
- Fixed a bug where simple commerce could display a PHP warning.
- Fixed a bug where the Edit Upload Directory form would not properly reflect overridden path and URL values from the config file.
- Fixed a bug where the
{member_group}global variable was playing hide-and-seek. Found it!
- Fixed a bug where the category filter on the Entry Manager did not respect your category orders. Line up, soldier!
- Fixed a bug with server response times in New Relic transaction reporting for front-end requests.
- Fixed a bug with the Member Importer where member field creation validaton would not work.
- Fixed an obscure bug (#22718) where a MySQL error could occur during installation on some environments.
- Fixed security bug where XSS may be injected by query string on certain control panel pages.
Version 3.4.3¶
Release Date: September 20, 2016
- Security
- Fixed a potential PHP injection issue when redirecing within the CP. (Thanks to the folks at with their static code analyzer RIPS)
- Improved metadata protection in Channel Form submissions.
- Optimized queries on pending/banned member tables.
- Namespaced add-ons now respond to the director’s call. ACTION! (Fixed a bug where ACTION requests to namespaced add-ons failed).
- Fixed a bug (#21855) where layouts could not expand a field that was configured to be hidden.
- Fixed a bug (#22028) where opening a file picker modal in thumbnail view with an empty directory selected would show a PHP error.
- Fixed a bug (#22029) where where the cURL library had an incorrect query string separator.
- Fixed a bug (#22035) where
{base_url}was not parsed in Pages Module URLs.
- Fixed a bug (#22081) where several site variables were not available in conditionals.
- Fixed a bug (#22114) where there was an undefined variable on the Reset Password screen.
- Fixed a bug (#22115) where front-end member registration may not have password validation.
- Fixed a bug in layouts where you could not collapse/uncollapse a field after you moved it without first saving the layout.
- Fixed a bug in the Discussion Forum where the forum order in the front end and back end did not match.
- Fixed a bug where cache files may be unable to be read by EE in certain hosting environments.
- Fixed a bug where some layout fields were being added old skool which caused PHP errors.
- Fixed a bug where the IP to Nation module could not update its IP database on PHP 7.
- Fixed a bug where the
View Alllink on the control panel edit submenu didn’t show when it should have.
- Fixed a Channel Form bug where model hooks would see the wrong author if a default Channel Form author for guest posts was set.
Version 3.4.2¶
Release Date: August 23, 2016
- Security
- Enhanced XSS protection in the Simple Commerce control panel.
- Fixed a potential HTML injection (non-XSS) issue.
- Added new Debugging & Output preference: “Enable Developer Log Alerts?”
- Added
<mark>to Safe HTML Typography and are now allowing its use in Channel Entries
{title}.
- Eliminated some PHP warnings in the Forum template editor if a custom theme had nested folders that were not explicitly supported.
- Fixed a PHP warning on the Forum Template editor if the admin had removed the default theme.
- Fixed a bug where Channel Form fields would not prefill their values on submission error.
- Fixed a bug where Default Category Channel pref was not being respected and added some tests so that it doth not regresseth again.
- Fixed a bug where bulk actions in the forum were playing an endless game of hide-and-seek.
- Fixed a bug where caching a tag with a conditional in it would always generate a cache and never read from it.
- Fixed a bug where changing the commented status via the bulk action dropdown in the control panel affected unselected comments.
- Fixed a bug where partials created from add-ons with disallowed characters might throw a PHP error.
- Fixed a bug where the Email class would not load values from site config unless the developer had manually initialized it.
- Fixed a bug where the file picker did not have an initial sorting applied.
- Fixed a bug where updating a site’s Template Settings would save all partials and variables to disk, not just the current site’s.
- Fixed a bug (#21417) where some HTML Buttons could not be created due to overzealous validation.
- Fixed a bug (#21863) wherre the
{avatar_url}tag was inaccurate when using a default avatar.
- Fixed a bug (#21989) where image manipulations would always save with a default site ID of 1.
- Fixed a bug (#21998) where date fields on the publish form would repopulate with a Unix timestamp after form validation failure.
- Fixed a bug (#22001) where viewing pending members sorted by join date would show an error.
- Fixed a bug (#22005) where the new category form may show encoded HTML entities in the parent category dropdown.
- Fixed a bug (#22014) where control panels under MSM might not follow a member group’s CP Homepage redirect.
- Fixed a bug (#22017, #21945) where toolbar buttons within Grid cells may be removed when manipulating rows.
- Fixed a bug (#22018) where choosing a file in the filepicker could generate multiple click events.
- Fixed a bug (#22019) where the
TemplateGroupmodel may generate duplicate queries in the control panel.
- Developers:
- Added a parameter to
form_dropdown()and
form_multiselect()turn off automatic encoding of display values.
- Added file and line number information to config file deprecation notices.
Version 3.4.1¶
Release Date: August 08, 2016
- Security
- Improved XSS protection in the CP when searching.
- Improved XSS protection in the CP’s table filters.
- Additional obscuring of file system paths when displaying exceptions.
- Improved XSS protection in Markdown typography.
- Long filenames now wrap in their table views in the File Manager and picker.
- Fixed a bug where file modals were blank if no upload directories existed.
- Fixed an issue where the top and bottom buttons on the publish page did not match.
- Fixed an issue where changes to authentication rules could show a confusing form when logging in.
- Fixed a bug (#21931) where the datepicker did not work consistently with non-default date formats.
- Fixed a bug (#21950) where the ChannelSubscription model did not have the correct relationships.
- Fixed a bug (#21940) where some member groups could not see template groups they created.
- Fixed a bug (#21951) where the conditional parser removed too much whitespace.
- Fixed a bug (#21982) where template partials were not parsed when inside other template partials.
- Fixed a bug (#21981) where the “Show news on CP homepage” always showed “no” even when saved as “yes”.
- Fixed a bug (#21983) where sometimes upload destinations didn’t have their {base_path} parsed.
- Fixed a bug where when you edited a status the preview was always grey, instead of your specified color.
- Fixed a bug where non-Super Admins were not presented with a Site switcher in the control panel if there are exactly two Sites.
- Fixed a PHP warning that could occur when publishing an entry with admin email notifications enabled.
- Fixed a bug where add-ons
require()-ing native config files might throw a PHP error.
- Fixed a bug (#21944) where category fields were not available when editing categories on the publish page.
- Fixed a bug (#21864) on the member profile member list page where a MySQL error could occur when using some default sort orders.
- Fixed a bug (#21984) where a PHP error could occur when uploading avatars in the control panel.
- Fixed a bug (#21993) on the default HTML buttons settings page where the buttons were not limited to the current site.
- Fixed a bug (#21922) where there was no way to remove a selected file from a file field in the channel entry form.
- Fixed a bug (#21980) where a select field type would sometimes not validate when it should.
- Fixed a bug where duplicating a channel would carry over its total_records count.
- Fixed a bug where filling in a required File field on the publish form would not clear any associated validation error.
- Fixed a bug (#22010) where deleting rows with invalid cells in a Grid would not clear its validation error.
Version 3.4.0¶
Release Date: July 27, 2016
- Security (big thanks to security researchers at HackerOne for helping us continue to keep ExpressionEngine secure!):
- Improved XSS and CSRF security in the Forum module.
- Improved XSS security in the Member module.
- Improved security by decoding IDN encoded domain names in user-submitted links.
- Improved clickjacking defense by defaulting all requests to SAMEORIGIN framing rules. See the new x_frame_options config override for details and header options.
- Added a menu manager to create custom control panel menus.
- Added a “Maximum number of entries” setting to Channels.
- Added base URL and base path settings to the URL and Path Settings to make building URLs and paths easier when environments change.
- Added
{reverse_count}and
{absolute_reverse_count}variables to the Channel Entries tag, for displaying entry count “countdowns”.
- Added an EllisLab news feed to the homepage.
- Added a permission to enable/disable the news on the CP homepage.
- Added a colorpicker to status highlight colors.
- Added live preview for status color picker.
- Added system overrides
code_block_preand
code_block_postto give additional control over the output of
[code]blocks.
- Added the ability to override the forum theme with a parameter:
{exp:forum theme='my_theme'}.
- When creating and editing Channel entries you now “Save” or “Save & Close” the form.
- Files have regained their ability to be categorized.
- Improved the UI for Template Routes
- The publish form will no longer have an empty category tab, unless you have a Layout that says it should.
- Switching sites in the CP will take you that site’s homepage.
- The File Chooser for Textareas and the RTE injested some ginko biloba and will remember your filters while editing or creating an entry.
- Deprecation notices are back; Super Admins will see an alert in the “admin” sections of the CP.
- Improved search on the edit page. It now includes entry data along with titles.
- Improved template partial parsing time by a factor of ten.
- Simplified Profiler Performance tab, and broke out time spent accessing the database.
- Language packs saved using the translation utility are now saved in their respective system/user/language folder.
- Channel Sets now export and import category fields.
- Removed some items from the config for new installs. Existing installs can safely remove the following preferences if you’re using their default values:
debug:
1
is_system_on:
y
allow_extensions:
y
cache_driver:
file
uri_protocol:
AUTO
charset:
UTF-8
subclass_prefix:
EE_
log_threshold:
0
log_date_format:
Y-m-d H:i:s
rewrite_short_tags:
TRUE
- File Improvements:
- Gave parity between File field type and
{exp:file:entries}variables.
- File fields now have
{directory_id},
{directory_title}, and
{id_path=}.
- The File Entries Tag now has
{extension},
{file_id},
{file_name},
{file_size},
{mime_type},
{modified_date},
{path},
{upload_date}, and
{url}.
- File size variables now have human readable modifiers.
{file_size}display bytes as always:
295903.
{file_size:human}displays an intelligently abbreviated size:
289KB.
{file_size:human_long}displays with the long form of the byte unit:
289 kilobytes.
- Fixed a bug where a File field tag may be unable to parse information about image manipulations for an upload directory belonging to another site.
- Fixed a bug (#21578) where a File field inside a Grid inside Channel Form would not have its data saved.
- Fixed a bug when saving a new Grid row that contained a Relationship field may show an error in rare cases.
- Fixed a bug (#21952) in the relationship field display where entries from other sites would not show up in the selectable options.
- Fixed a bug where radio buttons in sortable tables may lose their state after sorting.
- Fixed a bug (#21918) where parsing Grid fields from multiple content types could show errors in rare cases.
- Fixed a bug where {cp_edit_entry_url} did not specify the site ID.
- Fixed a bug where Channel Form would populate a DateTime object into the POST data for the recent_comment_date field.
- Fixed a bug where fields in a new layout tab could not be reordered until the layout was saved.
- Fixed a bug where Channel Sets only exported and imported the first Category Group of a Channel.
- Fixes a bug where MSM sites didn’t always have the Default Status Group.
- Fixed a pagination bug on the Member Groups page.
- Fixed a bug where MSM site prefs might not be updated for all sites during updates.
- Fixed a bug (#21832) where apostrophes in checkbox, radio and select field values could cause validation errors when selecting those values in the publish form.
- Developers:
- Added a parse_config_variables() global function for parsing {base_url} and {base_path} variables in strings.
- Added a validation rule, limitHtml, for limiting the kinds of HTML tags allowed in a string.
- Added a placeholder key to the field definition for text fields in the shared form view.
- Added the ability to extend native config files.
- Added a cp_custom_menu hook that allows you to create custom menu items. This replaces cp_menu_array from version 2.
- Added a search() method to the model query builder for easy search implementations.
- CP/Alerts without a title, body, and a sub-alert will no longer render.
- Sweet new formatters, via the Format Service. Currently includes attribute prepping and formatting byte sizes. More to come, huzzah!
Version 3.3.4¶
Release Date: July 7, 2016
- Security:
- Fixed potential SQL and XSS injection vulnerabilities in the control panel.
- Added an .htaccess file to the themes folder to allow the control panel font assets to be used across domains and subdomains.
- Publish file modal search now matches the file manager search behavior, searching in file names, file titles and by mime type (addresses bug #21912).
- Fixed a PHP error when sending emails from extension hooks in the Session class.
- Fixed a SQL error introduced in 3.3.3 when using the
orderby="random"parameter with the
{exp:file:entries}tag.
- Fixed a PHP error introduced in 3.3.3 with the
{exp:file:entries}tag in certain circumstances.
- Fixed a bug in the Discussion Forum that prevented errors from being thrown on some invalid post submissions.
- Fixed a PHP error when deleting a channel that contains entries that have comments.
- Fixed a bug (#21630) where multiple channel forms on the same page could result in unparsed variables.
- Fixed a bug (#21934) on non-default MSM sites, category custom field variables are unparsed on frontend.
- Developers:
- Added a public build_message() method as an entrance point if needed within the email_send extension hook.
Version 3.3.3¶.3.2¶
Release Date: May 20, 2016
- Saving entry revisions is now automatic so we removed the “Save Revision” button.
- Updated Date formatting variables to allow day of the week, ISO-8601 year number, timezone identifier, ISO-8601 date, and microseconds. See Date Variable Formatting for details.
- Optimized the create and edit template page to reduce the number of queries needed.
- Fixed a bug (#21227) where the images in the RTE did not have the proper overlay when hovering over them.
- Fixed a bug (#21288) where you may not be able to reliably paste text into an RTE field that had an image in it.
- Fixed a bug (#21870) where the Simple Commerce and Pages modules were missing a link to their settings.
- Fixed a bug where
EXPLAINqueries could not be run in the SQL manager.
- Fixed a bug where relationship data was not deleted completely.
- Fixed a model bug where pivot table relationships were not always reversed correctly.
- Fixed a bug (#21443) where assigning Allowed Channels with MSM would cause other sites to lose their assignments.
- Fixed a bug where checking the Mime Type of a CSS file could return
"text/plain"instead of
"text/css".
- Fixed a bug (#21663) where a raw language string would be returned if an add-on fails to install.
- Fixed a bug (#21731) where status permissions were not being respected.
- Fixed a bug (#21749) where a member group with only edit entry permissions did not have the Edit nav menu.
- Fixed a bug (#21797) where we provided edit and delete icons for categories and then denied access when you tried to use them. Sorry.
- Fixed a bug where add-ons could not specify a settings icon in the header.
- Fixed a bug (#21866) where Markdown
[code]blocks were not rendering correctly.
- Fixed a bug where the default theme could not be installed.
- Fixed a bug where the category parameter on the default theme slideshow could cause an error on some servers.
- Fixed a bug where URLs in an add-on’s README.md file would not mask the CP url.
- Fixed a bug where Channel
{total_entries}was not updated when publishing a new entry.
- Fixed a bug where Channel
{total_entries}was not updated by the Statistics sync utility.
- Fixed a bug where disabled checkboxes sorta looked enabley.
- Fixed a bug where settings were not passed to Extension constructors on the Extensions settings page.
- Fixed a bug (#21860) where update 3.1.0 could throw a PHP error in some situations.
Version 3.3.1¶
Release Date: May 10th, 2016
- NEW: Added additional logging when changing email address and password.
- Eliminated some extra, duplicate, and redundant queries when editing templates that are saved as files.
- Fixed a security bug where logged out users could be shown altered system messages.
- Fixed a bug (#21426) where status colors were not correctly shown on the Edit page.
- Fixed a bug (#21712) where the toggle fieldtype sometimes generated an error when used in Channel Form.
- Fixed a bug (#21713) where the file field on a publish form wouldn’t let go of an old file name when you replaced it. Let it go.
- Fixed a bug (#21775) in the Moblog module where PHP errors could occur when saving an edited moblog and multiple allowed emails were specified.
- Fixed a bug (#21806) where the Channel Form would inadvertently remove embed tags when editing entries.
- Fixed a bug (#21808) when using formatting types other than Markdown that effectively ignored a Channel’s “Render URLs and Email addresses as links?” setting.
- Fixed a bug (#21813) where an PHP error may show when viewing a member profile on older versions of PHP.
- Fixed a bug (#21816) where there was an unrendered language key in the Simple Commerce email templates listing.
- Fixed a bug (#21819) where the new Channel entry notifications were not working.
- Fixed a bug (#21820) where an unordered HTML button proudly declared itself instead of just using its icon.
- Fixed a bug (#21821) where email templates felt there were perfect as-is and didn’t save any edits.
- Fixed a bug (#21824) where dates could display improperly on the Publish and Edit pages.
- Fixed a bug (#21825) with Channel Set exports where exporting some field types could result in a corrupted zip file.
- Fixed a bug (#21833) where the Active Record class may show an error in PHP 7.
- Fixed a bug where a PHP error could occur when uploading files to a file field with a single directory specified.
- Fixed a bug where adding a new row to a grid wouldn’t register any file upload buttons for textareas.
- Fixed a bug where moblog settings did not properly display selected categories.
- Fixed a bug where some relationship fields on the publish form would not scroll.
- Fixed an obscure bug in channel entries where a specifying an invalid month, day and/or year in the parameters or the URI caused a MySQL error.
Version 3.3.0¶
Release Date: April 19, 2016
- NEW: Added Channel Sets.
- NEW: Added the default theme.
- NEW: Added the ability to add language information to a bbcode block (e.g.
[code="php"]).
- NEW:
{logged_in_...}Member variables are now parsed early.
- NEW: Super Admins using “Login as” retain debugging information.
- NEW: Member localization will now “stick” with the site’s preferences unless they have specified localization settings for their own account.
- NEW: Added FontAwesome to the Control Panel.
- NEW: Added a
{site_description}global variable.
- NEW: Added an unordered list button to the predefined HTML buttons.
- NEW: Comments column on control panel entries listing will not show if comments are disabled and no comments are present on the site.
- NEW: Added variables to the following email templates:
- ‘User - Account declined notification’ (
{username})
- ‘User - Account validation notification’ (
{username},
- The RTE fieldtype no longer manipulates the HTML it generates. What you save is what you get.
- Changed the email setting’s SMTP password field and the moblog setting’s email account password fields from plain text to password fields.
- Linked category group and field group names in the control panel now link to their respective category and field listings.
- Optimized relationship parent tag query.
- Updated PHP Markdown to 1.6.0.
- Removed code highlighting in
[code]blocks.
- Removed Glyphicons from the Control Panel.
- Fixed a bug (#21697) where an error may show when an exception is thrown in PHP 7.
- Fixed a bug (#21696) where the Manage Categories toggle was unstyled.
- Fixed a bug (#21667) where the image formatting button on a textarea did not use the file picker.
- Fixed a bug (#21688) where validation errors set via AJAX on Grid fields would sometimes be unresolvable.
- Fixed a bug where channel form could sometimes overwrite fields that were not in the form.
- Fixed a bug (#21644) where the file manager did not load for users with a lot of files.
- Fixed a bug where grid with more than one relationship could not parse all of them.
- Fixed a bug where the RTE fieldtype wasn’t always installed.
- Fixed a bug (#21582) where layouts missing the Categories tab would generate errors on the publish page.
- Fixed a bug (#21733) where layouts missing the Publish tab would generate errors on the publish page.
- Fixed a bug (#21677) where recalcuatling statistics didn’t recalculate the comment counts.
- Fixed a bug (#21682) where the list for duplicating an existing template, when creating a new template, was unsorted.
- Fixed a bug (#21704) where Firefox wouldn’t scroll to top in the CP.
- Fixed a bug (#21705) where saving an entry could trigger a PHP error.
- Fixed a bug (#21710) where the file modal’s table did not sort.
- Fixed a bug (#21619) where
[code]blocks and Markdown codeblocks did not properly add
<pre>tags.
- Fixed a bug where the Channel Form would inadvertently remove add-on tags when editing entries.
- Fixed a MySQL error that would occur on invalid forum feed requests.
- Fixed a stray PHP 7 incompatibility in Channel Form
- Fixed a bug (#21711) where CSS assets were not being delivered in
{path='css/_ee_channel_form_css'}requests.
- Fixed a bug where
layout:globals were parsed in content.
- Fixed a bug in site settings where the HTML button form required a closing tag.
- Fixed a bug (#21699) where a PHP error occurred when editing an entry via the channel form if the instructions or label tags were present.
- Fixed a bug (#21671) where a ‘Disallowed Key Characters’ error occurred when saving the channel_lang.php translation file.
- Fixed a bug (#21700) where a PHP error occurred on the member group page in the control panel when pagination was present.
- Fixed a bug (#21755) where there were unused language keys.
- Fixed a few bugs (#21756, #21757, #21758, #21761, #21760, #21762, #21759, #21774) with duplicate language keys.
- Fixed a bug (#21765) where some language keys had grammar issues.
- Fixed a few bugs (#21766, #21767) where we weren’t using language keys.
- Fixed a bug (#21768) where HTML button names were not being translated.
- Fixed a bug (#21769) where we had a small typo in new member notifications language.
- Fixed a bug (#21770) where a language key wasn’t getting the proper substitution.
- Fixed a bug (#21771) where a language key wasn’t in our language files.
- Fixed some langauge string bugs (#21754 and #21753).
- Fixed a bug (#21707) where some old auto saved entries refused to go away.
- Fixed a bug (#21750) where the File field could show an undefined index error if its data wasn’t pre-cached.
- Fixed a bug where the default CP homepage could not be saved for members other than the logged-in member.
- Fixed a bug (#21683) where URL titles had to be unique site-wide instead of per-Channel.
- Fixed a number of display bugs (#21671) in the translator.
- Fixed a MySQL error when recounting statistics and the Forum was installed (#21780).
- Fixed a bug where the comment form could show despite comments being globally disabled.
- Fixed a bug on the member profile page where the link to the member group form did not show for superadmins.
- Reduced the password reset token’s timeout. (thanks to security researcher Sjibe Kanti)
- Developers:
- NEW: Added
relationships_display_field_optionshook to allow additional filters on the options in the publish field.
- NEW: Added extension hooks for CategoryField, CategoryGroup, ChannelField, ChannelFieldGroup, File, MemberField, MemberGroup, Template, TemplateGroup, TemplateRoute models.
Version 3.2.1¶hook.
Version 3.2.0¶
Release Date: March 8, 2016
- NEW: Added template tags for modified image file dimensions i.e.
{image}{width:small}{/image}.
- NEW: Added a Toggle Fieldtype for all your on/off and yes/no needs.
- NEW: Added URL Field Type
- NEW: Added Email Address Field Type
- The default database engine is now InnoDB
- Added Forum Aliases.
- Added the Forum Publish Tab back in.
- Added global template variable/conditional
is_ajax_request
- Yay: we deprecated the jQuery module! Boo: we made it installable so you can still use it. Really, just use their CDN and include it yourself.
- Added a notice to the Site Manager when the site limit has been reached.
- Changed the file display to use the file’s name for non-images instead of the missing image thumbnail. (Bug #21270)
- Changed the behavior of the “Any …” options in the Relationship settings such that it and the specific options are mutually exclusive, i.e. “Any channel” or a specific channel, but not both. (Bug #21659)
- Fixed a bug (#21250) where sidebar items could not be marked inactive. Now they can.
- Fixed a bug where the Core version tried to use the Spam service.
- Fixed a bug where the comment module could throw a PHP error for guest posts.
- Fixed a bug (#21650) where one could not remove all rows in a Grid field.
- Fixed a bug (#21647) where there could be an undefined variable error on the Publish screen.
- Fixed a bug (#21628) where categories would not maintain their selection on the Publish form when there was a validation error.
- Fixed a bug (#21626) where the path for the passwords dictionary file was pointing to the wrong location.
- Fixed a bug where formatting buttons on textareas would not work on new Grid rows.
- Fixed a bug (#21638) where textareas with a file chooser available would have non-images inserted as an image tag.
- Fixed a bug (#21567) where sites with OPcache enabled can result in a false erorr after a fresh install.
- Fixed a bug (#21555) where empty tabs could not be removed from a layout.
- Fixed a bug (#21545) where email templates could not be edited.
- Fixed a bug (#21655) where template versions could sometimes generate erorrs.
- Fixed a bug (#21656) where Template Revisions were displayed unsorted, rather than sorted by date.
- Fixed a bug (#21565) where channel field text formatting could not update existing entries.
- Fixed a bug (#21103) where installing from https would configure the site for http instead of https.
- Fixed a bug (#21187) where Channel Form would sometimes be a little too strict about required fields.
- Fixed a bug (#21215) where updating a site with template routes from a version before 2.9.3 would generate errors.
- Fixed a bug (#21651) where we had a spelling mistake in an language key.
- Fixed a bug (#21561) where the translation utitliy would truncate some HTML when saving.
- Fixed a bug (#21293) where the translation utility would break the form if the translation contained a quotation mark.
- Fixed a bug (#21648) where the last field in a layout would sometimes refuse to move.
- Fixed a bug (#21587) where removing custom fields that were in a layout could break the layout.
- Fixed a bug (#21487) where enabling versioning after creating a layout would generate errors.
- Fixed a bug (#21329) where sending HTML email via the Communicate utility could add non breaking spaces.
- Fixed a bug (#21318) where partial translations could not be saved.
- Fixed a bug (#21335) where channel form couldn’t tell if an option was checked or not.
- Fixed a bug where Grid column clones were jealous and quietly assumed the identity of the original.
- Fixed a bug where you could not erase the contents of RTE field once it had been saved.
- Fixed a bug where commenting as a Guest generated an error.
- Fixed a bug (#21577) where the RTE would grow when switching from WYSIWYG to Source View.
- Fixed a bug where the front-end email settings page didn’t require a password when you weren’t changing your email address.
- Fixed a bug (#21287) where RTE fields could not be resized.
- Fixed a bug where database errors could sometimes not be displayed.
- Fixed a bug (#21601) where extension settings were only saved to the first method in the database.
- Fixed a bug (#21599) where the no_results conditional on nested relationship tags would have some of the initial characters cut off.
- Fixed a bug (#21584) where you couldn’t properly duplicate the Super Admin member group.
- Fixed a bug (#21627) where the comment form didn’t work when using Session or Session and Cookie front-end session types.
- Developers:
- Added output_show_message hook for modifying the output of front-end system messages.
- Added an
$antipoolparameter to
random_string()in the string helper, to blacklist characters from the alphanumeric-type pools. Uses are for unambiguous strings for humans, i.e. order numbers, coupon codes, etc:
$secret_code = strtoupper(random_string('alnum', 8, '0OoDd1IiLl8Bb5Ss2Zz'));
- The cp_search_index table was removed.
- The VariableColumnModel no longer marks properties as dirty when filling.
Version 3.1.4¶
Release Date: February 26, 2016
- Fixed a CRITICAL bug where saving or deleting comments may cause data loss in certain areas of the associated Channel entries, caused by a change in 3.1.3. Only installations of 3.1.3 were affected.
Version 3.1.3¶
Release Date: February 25, 2016
- Added visual indicators to required grid columns.
- Grid’s data type options now use the same names as the custom field’s type options.
- When editing a grid column’s data type the options are now filtered based on field type compatibility.
- Member listing setting “Sort By” choices now match available columns.
- Made some parameters in some Active Record methods required.
- Our CodeMirror linter had an epiphany and now realizes that installed plugins can have underscores in their tag names.
- Tweaked Performance tab of the Profiler for clearer display.
- Fixed a bug (#21457) where unchecked checkboxes in a publish form didn’t stay unchecked.
- Fixed a bug (#21558) where some Pages module variables were empty (and potentially some other items if retrieved with
config_item()).
- Fixed a bug (#21566) where the beforeSort and afterSort Grid publish form events were not working.
- Fixed a bug (#21569) where categories of the same name thought they were all selected when only some of them were.
- Fixed a bug (#21581) where a MySQL error occured on the publish page if no member groups were included in the author list.
- Fixed a bug (#21593) where a front-end logout link may show a warning in PHP 7.
- Fixed a bug (#21594) where number input types were not bound to AJAX form validation and had no styling.
- Fixed a bug (#21595) where categories created under another MSM site could not be assigned to an entry.
- Fixed a bug (#21603) where Grid’s JavaScript may try to manipulate table elements that are part of custom fieldtype markup.
- Fixed a bug (#21604) where relationships inside grid fields did not work consistently on MSM sites.
- Fixed a bug (#21605) where the documentation link for the “Suspend threshold” setting was broken.
- Fixed a bug (#21606) where the units used for the Lockout Time setting were not specified in the field description.
- Fixed a bug (#21609) where errors may appear when downloading a new blacklist under PHP 7.
- Fixed bugs (#21612 & #21616) where entry comment counts where not updated when adding or deleting comments.
- Fixed a bug (#21614) where one could not delete the last image manipulation for an upload directory.
- Fixed a bug (#21615) where there were a few misspellings of “entries” in the CP.
- Fixed a bug where Relationship fields could not be filtered when using session IDs for control panel sessions.
- Fixed a bug where the header search box did not repopulate correctly.
- Fixed a bug where a control panel search in the channel section could throw a PHP error.
- Fixed a bug where some default avatars were no longer displayed on the frontend.
- Fixed a bug where accepting the core file change notice resulted in a 404.
- Fixed a bug where custom fields could use reserved words as their short name.
- Fixed a bug where a Super Admin could delete his/her own account.
- Fixed a bug where installing an add-on with a publish tab would break existing publish form layouts.
- Fixed a bug where under the right conditions a member group that should have permissions to a forum doesn’t.
- Fixed a bug where glob() could return FALSE and cause all manner of errors in the Add-On Manager.
- Fixed a bug where saving a template did not clear any of the caches.
- Fixed a bug where the Revisions tab on the publish entry form only showed two versions instead of all your versions.
- Fixed a bug where the profiler did not display the URI of the current page call.
- Fixed a bug on the Superadmin group edit page, where the checkboxes for including in the author list and member list were incorrect.
- Fixed a bug where the confirmation notice would not be shown after deleting a large number of entries.
Version 3.1.2¶
Release Date: January 28, 2016
- Fixed a bug (#21408) where the Show File Chooser checkbox would not save for text input fields.
- Fixed a bug (#21488) where updating your member password could result in a PHP error.
- Fixed a bug (#21493) where a “more info” link in the Security & Privacy settings 404d.
- Fixed a bug (#21498) where using dynamic_parameters resulted in a PHP error.
- Fixed a bug (#21505) where the template creation form would not have its submit buttons re-enabled after a validation error.
- Fixed a bug (#21508) where form validation messages were not presented properly when editing a member’s profile.
- Fixed a bug (#21515) where the file upload modal didn’t work when opened from the Rich Text Editor or the Textarea fields.
- Fixed a bug (#21520) where the installer did not use the system config override for theme URL.
- Fixed a bug (#21521) where extension settings were not wrapped in the proper markup.
- Fixed a bug (#21523) where member groups listing in channel layouts table was missing a space.
- Fixed a bug (#21526) where an error would appear when saving a category field.
- Fixed a bug (#21532) where accessing some files wrongly accused you of attempting to access files outside of a directory.
- Fixed a bug (#21537) where PHP 5.3 didn’t like something the Pages module was doing and complained loudly.
- Fixed a bug (#21546) where one could not delete more than one category at a time via the category manager.
- Fixed a bug where the moblog settings page could run out of memory on large sites.
- Fixed a bug where upload_directory config overrides weren’t overriding on error display in the File Manager
- Fixed a bug where relationship parsing could result in conditional errors.
- Fixed a bug where channel form did not work without a url title field.
- Fixed a bug in channel form where the validation parameters could be ignored.
- Fixed a bug where deleting a field group didn’t delete its fields.
- Fixed a bug where Site filters never showed.
- Fixed a bug where uploading an avatar could result in an error about unlinking a directory.
- Fixed a bug where the installer incorrectly showed errors when moving avatars.
- Fixed a bug in the Channel form where non-superadmins did not always have access to all of their allowed channels.
- Added a warning to the File Manager when the upload directory you are browsing at is not on the file system.
Version 3.1.1¶
Release Date: January 20, 2016
- Fixed a bug (#21460) where interacting with a Relationship field’s filter inside a new Grid row would cause an error on entry save.
- Fixed a bug where the contact form could throw a PHP error.
- Fixed a bug (#21507) where creating template groups with save as files would throw PHP errors.
- Fixed a bug (#21512) where using the filepicker in the publish form could result in an “Invalid selection” error.
- Fixed a bug where the filepicker for file fields forgot about the default modal view setting.
- Fixed a bug (#21511) where the status filter on the Entry Manager ignored your selected channel.
- Fixed a bug where Template Variables would not automatically sync from files.
- Fixed a bug where the Metaweblog API errored when attempting to send or receive data.
Version 3.1.0¶
Release Date: January 18, 2016
- Compatible with PHP 7 and MySQL 5.7
- Template partials and Template variables can now be saved as files.
- Added the ability to manage categories from the Channel entry publish form.
- CodeMirror textareas (think Templates) are now resizable.
- Channel entries now default sort by entry date with the newest at the top.
- New member groups default to allowing online website access.
- Updated language in the installer to identify the directory that needs to be deleted if we can’t automatically rename the installer directory.
- Template groups can be reordered in the sidebar again.
- Removed duplicate queries when displaying multiple relationship fields on the publish form.
- Changed File listing to sort by date by default.
- Changed Add-on listings so the add-on name always links to the module control panel or settings if they exist.
- Changed wording of File field button on Publish page.
- Fixed a bug where the Filepicker could run out of memory.
- Fixed a bug where
load_package_jsdid not work on fieldtype publish pages.
- Fixed a bug where validation did not work consistently on some numeric types.
- Fixed a bug (#21255) where the “Assign category parents?” setting had no effect.
- Fixed a bug where the JavaScript for the Rich Tech Editor could not be loaded on the front-end.
- Fixed a bug (#21118) where custom member fields could not be populated.
- Fixed a bug (#21309) where custom member fields could not be rendered in a template.
- Fixed a bug where a PHP error would appear in the control panel if the cp_css_end hook was active.
- Fixed a bug where using the logged_out_member_id= parameter on Channel Form would throw an exception for logged-out users.
- Fixed a bug where duplicating a template group would not reset the hit counts for those templates or copy template permissions.
- Fixed a bug where new installs may be tracking template hits despite the setting appearing disabled.
- Fixed a bug (#21157) where files sizes could not be less than 1MB.
- Fixed a bug where bulk action checkboxes failed to work in the Entry Manager after searching.
- Fixed a bug (#21104) where add-ons with mutliple fieldtypes couldn’t use their fieldtypes.
- Fixed a bug where the installer wouldn’t automatically rename if you still had the mailing list export in your cache.
- Fixed a bug (#21458) where file uploads did not work in the Channel form.
- Fixed a bug (#21442) in the Channel form where PHP errors occurred when editing an entry with a file.
- Fixed a bug in the Channel form where PHP errors could occur when submitting an entry with no category assigned.
- Fixed a bug where CAPTCHA was not working properly on the Channel form.
- Fixed a bug where ENTRY_ID was not properly replaced on return after submitting the Channel form.
- Fixed a bug where the default status was not being used by the Channel form.
- Fixed a bug where new sites could not be created via the Site Manager.
- Fixed a bug (#21491) where the Grid model’s cache could not be cleared on subsequent data queries.
- Fixed a bug (#21464) where removing a file didn’t remove it’s manipulated copies. It’s hard saying good-bye.
- Fixed a bug (#21482) where templates were jealous and refused to show you their previous revisions.
- Fixed a bug (#21472) where checkboxes, radio buttons, and multiselect fieldtypes didn’t pay attention when given their menu options on create.
- Fixed a bug where adding category groups to a channel that had a layout wouldn’t let you move that category group in the layout.
- Fixed a bug (#21490) where “Populate the menu from another channel field” option in Channel Fields forgot which field you wanted to use.
- Fixed some language keys.
- Fixed a PHP warning when editing the Developer Forum theme templates.
- Fixed a bug where a duplicated Grid column would create two copies when duplicated.
- Fixed a Markdown bug with URLs that contain spaces when using Safe HTML.
- Fixed a bug (#21462) for PHP 5.3 which would lead to a fatal
Using $this when not in object context...error. Time to upgrade PHP!
- Fixed a bug where stop word removal in the search module was not UTF-8 compatible. Zaro Ağa is no longer Zaro Ğ.
- Fixed an obscure URI detection bug that could lead to duplicate content duplicate content.
- Fixed a bug in Template Routes where it was ignoring the “Require all Segments” setting.
- Renamed Template Route’s “Require all Segments” setting to “Require all Variables” to match its behavior.
- Developers:
- Changed the event emitter to trigger subscriber events before manually bound ones
- Model events will no longer trigger if the described event does not take place (no
onAfterSaveif save is called on an unchanged model)
- Added
less_thanand
greater_thanvalidation rules
string_overridekey in publish form tab definitions works again.
- Fixed a bug where asking a model query to return columns that didn’t include the primary key would only return one result.
- Class names can now be set on fieldsets via the shared form attributes array.
- Fixed a bug in the legacy Addons library where incorrect paths would be returned from the get_installed() method.
- Fixed a bug where alerts that were deferred would not carry over their manually-set close/cannot close setting.
- Date fields with the date picker bound to them can set a custom date format via a data-date-format parameter on the text input.
- The date picker can be bound to a text input using EE.cp.datePicker.bind(element).
- Added comment_entries_query_result hook for modifying the query result set for {exp:comment:entries}.
- Added comment_entries_comment_ids_query hook for modifying the query that selects the IDs for comments to display in {exp:comment:entries}.
- Added the ability for Folder List sidebars to be reordered.
- Added a pause and resume method to the form validation JS.
- Added: Channel Fields can now declare their compatibility type allowing editing of the type itself (i.e. RTE to Textarea).
- Added a number of hooks to the following models:
- Channel Entry
- Member
- Category
- Comment
Version 3.0.6¶
Release Date: December 17, 2015
- Fixed a bug (#21240) where some templates rendered with errors relating to “protect_javascript”.
- Fixed a bug (#21310) where Channel Layouts did not allow you to reposition fields that were added after the layout was created.
- Fixed a bug (#21400) where the Contact Form generated errors.
- Fixed a bug (#21400) where the Contact Form returned a white screen when the Spam module was enabled.
- Fixed a bug (#21412) where some categories appeared on the Publish tab.
- Fixed a bug (#21420) where the Relationship field could no longer organize its related items after searching.
- Fixed a bug (#21436) where RTEs were named inconsistently as fields vs. Grid columns.
- Fixed a bug where some elseif branches in template conditionals were not pruned correctly.
- Fixed a bug where searching withing a Relationship field would unsort your related entries.
- Fixed a bug where publish forms with large Relationship fields could overflow the POST data and result in data loss.
- Fixed a bug where new rows added to a Grid with a Relationship column could have pre-populated Relationship fields.
- Fixed a bug where filtering or searching a Relationship inside a Grid caused that Relationship to ignore the selection.
- Fixed a bug with some overzealous Markdown parsing.
- Fixed a bug where the Member module would not be installed when upgrading a Core installation to Standard.
- Fixed the
{cp_edit_entry_url}variable.
- Fixed a bug where forum previews did not fall back to using the default index template if running the forums through the templates.
- Adjusted sub menus to scroll when they are long.
- Improved New Relic transaction reporting.
- Pre-release versions now include a visual indication that they’re pre-release and also include the version identifier (e.g.
dp.4) in the extended version information.
- The installer has been calmed down a bit and won’t skip showing you error messages when they exist.
- Added a check for the required PHP Fileinfo extension to the installer.
- Added a feature (#21418): duplicating a Template did not duplicate its allowed member groups.
- Added a feature (#21427): the Edit Manager’s category filter is now populated based on the channel filter.
- Added a feature: comments can be formatted with any formatter you have installed. EE, we have Markdown!
Version 3.0.5¶
Release Date: December 2, 2015
- Fixed a bug (#21338) where categories with an ampersand in the title would not maintain its selection state on the entry publish form.
- Fixed a bug (#21300) where the RTE’s image tool may place the selected image in another RTE when there are multiple on a publish form.
- Fixed a bug where a PHP error would appear in the control panel if the
cp_css_endhook was active.
- Fixed a bug where some Channel entry date variables would not work in conditionals without having brackets around them.
- Fixed a bug (#21378) where the
cp_css_endhook was never fired.
- Fixed a bug (#21394) where an incorrect language key was used for the working state of some buttons in the Members section.
- Fixed a bug (#21395) where a PHP error may appear on some actions dealing with file thumbnails.
- Fixed a bug (#21389) where some OGV files would not be accepted for upload.
- Fixed a bug (#21388) where validation for URL titles in Channel entries would incorrectly flag periods as not allowed.
- Fixed a bug where global template partials could not be edited.
- Fixed a bug where saving entries did not clear caches if that setting was enabled.
- Fixed a bug where the default homepage could be set to the publish page of no channel.
- Fixed a bug where only super admins could edit status groups.
- Fixed a bug where form success messages were removed too eagerly.
- Fixed a bug where modals were shy and did not scroll into view when using Firefox.
- Fixed a bug (#21380) where logging in as another member from the control panel would show a PHP error.
- Fixed a bug where channel layouts did not play nicely with the profiler.
- Fixed a bug (#21387, #21273) where the File module was not installed.
- Fixed a bug (#21373) where two file fields in one Channel would not work on the Publish page.
- Fixed a bug (#21344) where the file modal would not restrict you to the allowed directory when switching filters.
- Fixing a bug where no notice was shown when deleting a newly created publish layout tab with a field in it.
- Fixed a bug (#21406) where the “view” link in the CP for your MSM site did not open in a new tab.
- Fixed a bug (#21407) where extending the Category class revealed a PHP Runtime error.
- Fixed a bug (#21342) where CSV exports were really Comma-and-Space Separated Values.
Version 3.0.4¶
Release Date: November 18, 2015
- Fixed a bug that allowed .codemirror to stand on top of .sub-menu
- Fixed a bug that prevented grid column widths from affecting the publish UI. (note: column widths will not affect grid columns with RTE, Relationships or Textarea fields)
- Fixed a bug where run-on sentences made the RTE puff up with pride inside grid fields, we pulled him aside and set him straight.
- Fixed a bug (#21099) where line breaks in member signatures were being converted to literal
\n. Literally.
- Fixed a bug (#21282) where publish tabs pulled a bait and switch and saved their defaults instead of your data. They are looking at hours of community service.
- Fixed a bug (#21289) where some JavaScript events didn’t happen.
- Fixed a bug (#21295) where clicking, instead of dragging, on the move icon in Channel Layouts refreshed the page.
- Fixed a bug (#21305) where the button text on a Channel entry publish form would not be reset after a validation error when revisions were enabled.
- Fixed a bug (#21307) where LocalPath::__get generated PHP errors.
- Fixed a bug (#21308) where listing member groups couldn’t handle large numbers of members.
- Fixed a bug (#21313) where submitting forms or clicking links would occasionally result in a blank page.
- Fixed a bug (#21320) where a PHP error would appear when using the {member_search_path} variable inside an Channel Entries tag pair.
- Fixed a bug (#21321) where empty relationship fields sometimes generated errors. Sometimes you just need a little alone time.
- Fixed a bug (#21325) where certain add-ons refused to acknowledge their new version number after they were updated.
- Fixed a bug (#21326) where the template manager was insensitive toward case sensitive file systems and you could not edit Forum Templates.
- Fixed a bug (#21328) where we still referenced the constant SYSTEM. It’s now SYSPATH.
- Fixed a bug (#21332) where some template paths had double slashes (//) when saving as files.
- Fixed a bug (#21334) where template groups which were not the default template group bullied the default template group into renouncing its defaultness.
- Fixed a bug where categories could not be assigned via Channel Form.
- Fixed a bug where you couldn’t Communicate if you had a large number of members.
- Fixed a bug where the CP complained with esoteric errors when you had enough members for pagination.
- Fixed a bug where membership was elitist and pending members could not be approved.
- Fixed a bug where the Forums fibbed about the Upload Directory being a URL when really it’s a path.
- Fixed a bug where removing the Forum theme named “default” prevented the Template Manager from finding any Forum themes.
- Fixed a bug where some buttons were roguishly displaying a raw language key, rather than actual language data.
- Fixed a bug (#21283) where upload directory synchronization may not apply image manipulations to some files.
- Fixed a bug (#21259) in the Email mdoule where PHP errors were thrown after sending emails.
- Fixed a bug (#21274) where a member group with file access couldn’t open the file picker.
- Fixed a bug where avatar images where showing up in the file picker.
- Fixed a bug where you couldn’t upload images if the file picker only had one directory to choose from.
- Added site-wide yes/no settings for notifying pending members when they are approved or denied.
Version 3.0.3¶
Release Date: November 9, 2015
- Fixed a bug (#21272) where default field formatting was not respected when publishing. Chastised the offending code.
- Fixed a bug (#21286) where there was a syntax error in the file picker on lower versions of PHP.
- Fixed a bug (#21296) where new templates were shy and wouldn’t let anyone but Super Admins view them.
- Fixed a bug (#21299) where a Grid-compatible fieldtype whose markup contained a table would make the Grid field behave incorrectly.
- Fixed a bug (#21301) where there was only one default template group per install, not per site.
- Fixed a bug (#21314) where the Discussion Forum front end was 404’ing. Where did it go?
- Fixed a bug with Discussion Forum theme image URLs
- Fixed a bug where some site settings did not save correctly.
- Added the SMTP port to the Outgoing Email settings page.
Version 3.0.2¶
Release Date: November 2, 2015
- Fixed a bug (#21214) where ExpressionEngine Core had Phantom Template Routes Syndrome which was causing PHP errors.
- Fixed a bug (#21217) where the “owned by” link in the License & Registration page resulted in a 404.
- Fixed a bug (#21222) where the CP was referencing “default.png” which retired and is on vacation in the south of France.
- Fixed a bug (#21223) where clicking on the sort handle in grid settings refreshed the page.
- Fixed a bug (#21225) where editing an entry with a file in a grid column could result in a PHP error.
- Fixed a bug (#21226) where field groups refused to be assigned to any site but your first one.
- Fixed a bug (#21228) where files could be uploaded to any upload destination via the publish form.
- Fixed a bug (#21236) where the Black/White List add-on generated errors when trying to download the EE Blacklist.
- Fixed a bug (#21239) where the IP to Nation add-on wouldn’t let you unban all countries once you’d banned at least one.
- Fixed a bug (#21244 & #21198 & #21193) where field settings had a case of amnesia.
- Fixed a bug (#21248) where choosing a thumbnail in the filepicker did nothing.
- Fixed a bug (#21249) where the path of saved translations was incorrect.
- Fixed a bug (#21251) where creating an entry didn’t set an edit_date.
- Fixed a bug (#21252) where adding a custom member field could result in an exception.
- Fixed a bug (#21253) where {edit_date} formatted dates incorrectly.
- Fixed a bug (#21264) where updating a member would sometimes cause PHP notices.
- Fixed a bug (#21266) where new channel entries ignored the Channel Settings for default status, category, entry title, and url title prefix.
- Fixed a bug (#21275) where under the right conditions a required custom field could be hidden on the Publish page.
- Fixed a bug (#21276) where categories had the option of setting themselves as their own parent; it was a genealogical nightmare.
- Fixed several bugs where certain relationship template tag combinations would result in a PHP error. You should see the therapy bill.
- Fixed a bug where some model validation errors tried to convert an array to a string.
- Fixed a bug where new sites could not be created via the Site Manager.
- Fixed a bug where PHP 5.3 objected to an array access in the Relationship fieldtype on the publish page.
- Fixed a bug where saving a custom member field wanted you to “Save Layout”.
- Fixed a bug where long folder list names were overlapping the toolbars.
- Fixed a bug where remove tools would appear without a left border.
- Added blockquote support to in app add on docs.
- Changed bg color for login screens.
Version 3.0.1¶
Release Date: October 26, 2015
- Fixed a bug (#21191) where creating a layout for a channel without categories misbehaved.
- Fixed a bug (#21191) where moving a field into a new tab caused it’s hidden tool to malfunction.
- Fixed a bug (#21196) where Core would report a PHP Notice when editing the profile of a member.
- Fixed a bug (#21199) where 404 pages were not seting a 404 header.
- Fixed a bug (#21199) where the “+ New Upload Directory” link resulted in a 404.
- Fixed a bug (#21204) where certain versions of PHP could not determine empty of a function.
- Fixed a bug (#21205) where the Filepicker wouldn’t play nice with Core.
- Fixed a bug (#21206) where disabling comments still displayed comment data on the Overview page.
- Fixed a bug (#21213) where turning on “Save Templates as Files” was a little overprotective and rewrote the index template with “Directory access is forbidden.”
- Fixed a bug (#21218) where Quick Links were permanent.
- Fixed a bug (#21219) where the template manager was too eager about keeping templates in sync across all sites instead of the current site.
- Fixed a bug (#21220) where moving a required field to a new tab removed the required class.
- Fixed a bug (#21221) where accessing the templates model during a session_start hook threw an exception.
- Fixed a bug (#21224) where PHP would sometimes generate a warning when it tried to delete a file.
- Fixed a bug (#21231) where members were being denied access to add-ons they had access to.
- Fixed a bug (#21233) where an empty line in the spam module caused PHP errors.
- Fixed a bug (#21233) where running apc_delete_file sometimes generated a warning.
- Fixed a bug (#21235) where static template route segments were not being included when using {route=…}
- Fixed a bug where creating a second layout for a channel would result in an Exception.
- Fixed a bug where adding and saving an empty tab to a channel layout prevented further editing of the tab.
- Fixed a bug where alerts were not being displayed while creating a layout and preforming unallowed actions.
- Fixed a bug where a required field could be dropped into a hidden tab.
- Fixed a bug where dismissing alerts on the Create/Edit Form Layout page refreshed the page.
- Fixed a bug where the thumbnail view of the filepicker was not responsive.
- Add-ons are no longer “Removed”, they are “Uninstalled”.
- Fixed a bug where ‘yes’ and ‘no’ weren’t localizable. Lo siento.
- Removed CSS that forced capitalization on .choice
Version 3.0.0¶
Release Date: October 13, 2015
Control Panel
General
- Responsive design is a pleasure on mobile devices.
- 100% image free, fast and beautiful on regular and high density displays
- Inline error messages consistently used on all forms.
- The control panel navigation and logic is now based on the idea of Content Creators and Site Builders, with navigation related to content creators on the left and site builders on the right.
- Many application defaults have been modified to reflect how people most often use ExpressionEngine.
- Control Panel landing pages are customizable per member group, or even per member
- In-app links to the documentation, support, and bug tracker are visible to member groups of your choice.
- Improved contextual search in the control panel.
- Uses a consistent visual language across the board.
- Enabling/disabling CAPTCHA has been consolidated to a single site-wide setting.
- Unified Upload Directories: Everything that used to be a special folder (Member photos, avatars, etc..) is now available in the File Manager and can use the usual file manipulations and other upload preferences.
- Smart interactions (for example, if you have no channels, then clicking Create will take you to the channel manager to make one).
- Bulk actions don’t clutter the UI, they onlyappear only when needed.
- The new style guide allows both 1st and 3rd party to build awesome UX.
- The new design will allow simple iterative niceties in the future, such as adding some minimal color and branding for your clients.
- Comments are no longer a separate module. Comments can be accessed from the Overview page.
- Accessories no longer exist.
- Quicklinks and custom tabs were consolidated into only Quicklinks.
- Table zebra-striping JS has been removed. Zebra-striping is handled automatically by the CSS.
- Pre-populating the Name and URL fields of quicklinks when the ‘+ New Link’ button is clicked.
- Added a default modal view setting to upload destinations.
Overview Page
- The Home Page is now the overview page.
- Completely rewritten to show a quick overview of your content, including recent comments, member counts and latest entry information.
Create
- Content -> Publish has moved to the top level Create tab.
- Improved category create modal.
- The Publish Layout manager has moved to its own page in the Channel Manager.
- Titles can now have different labels, set in the Channel Manager.
- Improved behavior of entry filtering in Relationship fields on the publish form so it searches all entries.
Edit
- Content -> Edit has moved to the top level Edit tab.
- The search has live filtering, and you can now bookmark the results directly.
Files
- Content -> Files has moved to the top level Edit tab.
- Member Group permissions are now more granular.
Developer Tools
- Channel Manager
- Admin -> Channel Administration is now a subsection under developer tools. All Channel, Status, Category and Field settings are accessed here.
- Channel layouts have a dedicated form for managing the publish/edit layouts.
- Categories have drag and drop sorting and nesting.
- Template Manager
- Moved from Design -> Templates -> Template Manager
- Snippets were renamed Template Partials
- Global variables were renamed Template Variables
- Synchronization page removed as this is now fully automated.
- Consistency in the display of any System templates (Email, Members, Forums, etc.).
- Site Manager
- Access to the manager moved from the site title dropdown.
- Removed the ability to duplicate existing sites.
- Add-On Manager
- Add-ons are no longer a top level menu tab.
- Add-ons are all on one page.
- Third party plugins are grouped together.
- Plugins must now be installed as part of the move toward more consistent behavior.
- Built-in non-optional add-ons are hidden from the table
- Utilities
- Consolidated several Tools sections: Communicate, Utilities and Data.
- Extension debugging section added here to allow disabling of individual extensions.
- Logs
- Moved from Tools -> Logs
Settings
- The new Settings page consolidates a number of settings that were scattered throughout the version 2 control panel. Notably the Global Template, Member message and avatar* and Comment preferences can be found here. That’s in addition to the other preferences that move over from the version 2 Admin tab.
Multiple Site Manager
- Now included with ExpressionEngine.
- All ExpressionEngine licenses come with one site and you only pay for additional sites, not the ability to add additional sites.
- When you upgrade your ExpressionEngine license, you can merge in a Multiple Site Manager license to add sites to that license.
Discussion Forums
- Now included with ExpressionEngine.
Spam Module
- Unified anti-spam service for first and third party code.
- Comes pre-trained for common spam, but can be further trained your site’s specific content.
- No subscription needed and all data remains on your site.
- Training data is exportable for sharing with others and future site builds.
Installer
- One-page installation.
- Updating is much easier thanks to the new user servicable directory. Just replace
system/eeand
themes/eeand update.
- Third-party add-ons are no longer updated during the EE update.
General Changes
- Removed Referrer module.
- Removed Mailing List module.
- Removed Wiki module.
- Template routes can now be set in the config file.
- Improved template route parsing.
- Improved Profiler and Debugging.
- Screen Names no longer have to be unique.
- Updated Markdown Extra to v1.5.0.
- Changed password maximum length to 72 characters.
- Added
{if no_results}to
{categories}tag pair in
{exp:channel:entries}loop
- Added
{if no_results}to
{exp:channel:categories}
- A custom database port can be specified in the database configuration array
Developers
- All new Model Service which replaces our APIs.
- Added a Dependency Injection Container.
- Channel fields, Member fields, and Category fields now all use the same API
- New FilePicker service for displaying file browser modals
- Use the require_captcha setting to determine whether to require CAPTCHA or not for your front-end forms.
- Module tab API has changed. See tab.pages.php for a working example. In short, the methods are now display($channel_id, $entry_id), validate($entry, $data), save($entry, $data), delete($entry_ids).
- Deleted:
Api_channel_entries::send_pings()
DB_Cache::delete()
Filemanager::frontend_filebrowser()
Functions::clear_spam_hashes()
Functions::set_cookie()
Member_model::get_localization_default()
- File helper’s get_mime_by_extension()
- Magpie plugin
- Version helper
- Channels-specific pagination hooks
- SafeCracker hooks
edit_template_starthook
update_template_endhook
- Deprecated:
cp_url()helper method, use
ee('CP/URL')instead.
- Extension’s
universal_call(), use
call()instead. | https://docs.expressionengine.com/v3/about/changelog.html | 2018-02-17T23:04:17 | CC-MAIN-2018-09 | 1518891808539.63 | [] | docs.expressionengine.com |
Create knowledge from an incident or problem To create knowledge from an incident or problem, select the Knowledge check box on the incident or problem form and close the incident or problem record. About this task TheSelect a knowledge article categoryMove a knowledge articleImport a Word document to a knowledge baseRelated ConceptsRetire a knowledge article | https://docs.servicenow.com/bundle/geneva-servicenow-platform/page/product/knowledge_management/task/t_ApproveKnowledgeSubmission.html | 2018-02-17T23:41:00 | CC-MAIN-2018-09 | 1518891808539.63 | [] | docs.servicenow.com |
Scalability
Because TCP optimization is resource intensive, a single Citrix ADC appliance, even a high end –appliance, might not be able to sustain high Gi-LAN throughputs. To expand the capacity of your network, you can deploy Citrix ADC appliances in an N+1 cluster formation. In a cluster deployment, the Citrix ADC appliances work together as a single system image. The client traffic is distributed across the cluster nodes with the help of external switch device.
TopologyTopology
Figure 1 is an example of a cluster consisting of four T1300-40G nodes.
The setup shown in Figure 1 has the following properties:
- All cluster nodes belong to the same network (also known as an L2 cluster).
- Data plane and backplane traffic are handled by different switches.
- Assuming Gi-LAN throughput is 200 Gbps and that a T1300-40G appliance can sustain 80Gbps of throughput, we need three T1300-40G appliances. To provide redundancy in case of single cluster node failure, we deploy four appliances in total.
- Each node will receive up to 67Gbps of traffic (50Gbps in normal operating conditions and 67Gbps in case of single cluster node failure), so it needs 2x40Gbps connections to the upstream switch. To provide redundancy in case of switch failure, we deploy a couple of upstream switches and double the number of connections.
- Cluster Link Aggregation (CLAG) is used to distribute traffic across cluster nodes. A single CLAG handles both client and server traffic. Link Redundancy is enabled on the CLAG, so only one “subchannel” is selected at any given time and handles the traffic. If some link fails or throughput falls below specified threshold, the other subchannel is selected.
- The upstream switch performs symmetric port-channel load balancing (for example, source-dest-ip-only algorithm of Cisco IOS 7.0(8) N1(1)) so that forward and reverse traffic flows are handled by the same cluster node. This property is desirable because it eliminates packet reordering, which would degrade TCP performance.
- Fifty percent of data traffic is expected to be steered to backplane, which means each node will steer up to 34Gbps to other cluster nodes (25Gbps in normal operating conditions and 34Gbps in case of single cluster node failure). Thus, each node needs at least 4x10G connections to the backplane switch. To provide redundancy in case of switch failure, we deploy a couple of backplane switches and double the number of connections. Link redundancy is not currently supported for backplane, so Cisco VPC or equivalent technology is desired to achieve switch-level redundancy.
- MTU size of steered packets is 1578 bytes, so backplane switches must support an MTU more than 1500 bytes.
Note: The design depicted in Figure 1 is also applicable to T1120 and T1310 appliances. For T1310 we would use 40GbE interfaces for the backplane connections, since it lacks 10GbE ports.
Note: While this document uses Cisco VPC as an example, if working with non-Cisco switches alternate equivalent solutions could be used, such as Juniper’s MLAG.
Note: While other topologies such as ECMP instead of CLAG are possible, they are not currently supported for this particular use case.
Configuring TCP Optimization in a Citrix ADC T1000 ClusterConfiguring TCP Optimization in a Citrix ADC T1000 Cluster
After physical installation, physical connectivity, software installation, and licensing are completed, you can proceed with the actual cluster configuration. The configurations described below apply to the cluster depicted in Figure 1.
Note: For more information about cluster configuration, see “Setting up a Citrix ADC cluster.”
Assume that the four T1300 nodes in Figure 1 have the following NSIP addresses:
Four T1300 nodes with NSIP address:
T1300-40-1: 10.102.29.60 T1300-40-2: 10.102.29.70 T1300-40-3: 10.102.29.80 T1300-40-4: 10.102.29.90
The cluster will be managed through the cluster IP (CLIP) address, which is assumed to be 10.78.16.61.
Setting Up the ClusterSetting Up the Cluster
To begin configuring the cluster shown in Figure 1, log on to the first appliance that you want to add to the cluster (for example, T1300-40-1) and do the following.
- At the command prompt, enter the following commands:
Command:
> add cluster instance 1 > add cluster node 0 10.102.29.60 -state ACTIVE > add ns ip 10.102.29.61 255.255.255.255 -type clip > enable cluster instance 1 > save ns config > reboot –warm
2. After the appliance restarts, connect to the Cluster IP (CLIP) address and add the rest of the nodes to the cluster:
Command:
> add cluster node 1 10.102.29.70 -state ACTIVE > add cluster node 2 10.102.29.80 -state ACTIVE > add cluster node 3 10.102.29.90 –state ACTIVE > save ns config
3. Connect to the NSIP address of each of the newly added nodes and join the cluster:
Command:
> join cluster -clip 10.102.29.61 -password nsroot > save ns config > reboot –warm
4. After the nodes restart, proceed with backplane configuration. On the cluster IP address, enter the following commands to create an LACP channel for the backplane link of each cluster node:
Command:
> set interface 0/10/[1-8] –lacpkey 1 –lacpmode ACTIVE > set interface 1/10/[1-8] –lacpkey 2 –lacpmode ACTIVE > set interface 2/10/[1-8] –lacpkey 3 –lacpmode ACTIVE > set interface 3/10/[1-8] –lacpkey 4 –lacpmode ACTIVE
5. Similarly, configure dynamic LA and VPC on the backplane switches. Make sure the MTU of the backplane switch interfaces is at least 1578 bytes.
6. Verify the channels are operational:
Command:
> show channel 0/LA/1 > show channel 1/LA/2 > show channel 2/LA/3 > show channel 3/LA/4
7. Configure the cluster node backplane interfaces.
Command:
> set cluster node 0 -backplane 0/LA/1 > set cluster node 1 -backplane 1/LA/2 > set cluster node 2 -backplane 2/LA/3 > set cluster node 3 –backplane 3/LA/4
8. Check the cluster status and verify that the cluster is operational:
> show cluster instance > show cluster node
For more information on cluster setup, see “Setting up aCitrix ADC cluster”
Distributing Traffic Across Cluster NodesDistributing Traffic Across Cluster Nodes
After you have formed theCitrix ADC cluster, deploy Cluster Link Aggregation (CLAG) to distribute traffic across cluster nodes. A single CLAG link will handle both client and server traffic.
On the cluster IP address, execute the following commands to create the Cluster Link Aggregation (CLAG) group shown in Figure 1:
Command:
> set interface 0/40/[1-4] -lacpMode active -lacpKey 5 -lagType Cluster > set interface 1/40/[1-4] -lacpMode active -lacpKey 5 -lagType Cluster > set interface 2/40/[1-4] -lacpMode active -lacpKey 5 -lagType Cluster > set interface 3/40/[1-4] -lacpMode active -lacpKey 5 -lagType Cluster
Configure dynamic link aggregation on the external switches.
Then, enable Link Redundancy as follows:
Code:
> set channel CLA/1 -linkRedundancy ON -lrMinThroughput 240000
Finally, check the channel status by entering:
Command:
> show channel CLA/1
The channel should be UP and the actual throughput should be 320000.
For more information about cluster link aggregation, see the following topics:
Because we will be using MAC-based forwarding (MBF), configure a linkset and bind it to the CLAG group as follows:
Command:
> add linkset LS/1 > bind linkset LS/1 -ifnum CLA/1
More information about linksets, see the following topics:
Configuring VLAN and IP AddressesConfiguring VLAN and IP Addresses
We will be using striped IP configuration, which means that IP addresses are active on all nodes (default setting). See “Striped, Partially Striped, and Spotted Configurations” for more information about this topic.
- Add the ingress and egress SNIPs:
Command:
> add ns ip 172.16.30.254 255.255.255.0 –type SNIP > add ns ip 172.16.31.254 255.255.255.0 –type SNIP > add ns ip6 fd00:172:16:30::254/112 –type SNIP > add ns ip6 fd00:172:16:31::254/112 –type SNIP
2. Add the corresponding ingress and egress VLANs:
Command:
> add vlan 30 -aliasName wireless > add vlan 31 -aliasName internet
3. Bind VLANs with IPs and linkset:
Command:
> bind vlan 31 -ifnum LS/1 -tagged > bind vlan 30 -ifnum LS/1 -tagged > bind vlan 30 -IPAddress 172.16.30.254 255.255.255.0 > bind vlan 31 -IPAddress 172.16.31.254 255.255.255.0 > bind vlan 30 -IPAddress fd00:172:16:30::254/112 > bind vlan 31 -IPAddress fd00:172:16:31::254/112
More ingress and egress VLANs can be added if needed.
Configuring TCP OptimizationConfiguring TCP Optimization
At this point, we have applied all cluster specific commands. To complete the configuration, follow the steps described in “[TCP optimization configuration]/en-us/citrix-adc/12-1/citrix-adc-support-for-telecom-service-providers/NS_TCP_optimization/NS_TCP_opt_config.html)”.
Configuring Dynamic RoutingConfiguring Dynamic Routing
A Citrix ADC cluster can be integrated into the dynamic routing environment of the customer’s network. Following is an example of dynamic routing configuration using BGP routing protocol (OSPF is also supported).
1. From the CLIP address, enable BGP and dynamic routing on ingress and egress IP addresses:
Command:
> enable ns feature bgp > set ns ip 172.16.30.254 –dynamicRouting ENABLED > set ns ip 172.16.31.254 –dynamicRouting ENABLED
2. Open vtysh and configure BGP for the egress side:
Code:
> shell root@ns# vtysh ns# configure terminal ns(config)# router bgp 65531 ns(config-router)# network 10.0.0.0/24 ns(config-router)# neighbor 172.16.31.100 remote-as 65530 ns(config-router)# neighbor 172.16.31.100 update-source 172.16.31.254 ns(config-router)# exit ns(config)# ns route-install propagate ns(config)# ns route-install default ns(config)# ns route-install bgp ns(config)# exit
3. Configure the egress-side BGP peer to advertise the default route to the Citrix ADC cluster. For example:
Command:
router bgp 65530 bgp router-id 172.16.31.100 network 0.0.0.0/0 neighbor 172.16.31.254 remote-as 65531
4. Follow similar steps to configure the ingress side.
5. From vtysh verify that configuration is propagated to all cluster nodes, by entering:
Command:
ns# show running-config
6. Finally, log on to NSIP address of each cluster node and verify routes advertised from BGP peer:
Command:
> show route | grep BGP | https://docs.citrix.com/en-us/citrix-adc/12-1/citrix-adc-support-for-telecom-service-providers/NS_TCP_optimization/Scalability.html | 2019-03-18T20:53:05 | CC-MAIN-2019-13 | 1552912201672.12 | [array(['/en-us/citrix-adc/media/t1300-40-cluster.png', 'localized image'],
dtype=object) ] | docs.citrix.com |
Include emails for backup on Linux
inSync Cloud Editions:
Elite Plus
Elite
Enterprise
Business
Include emails for backup on Linux
To backup emails from Linux
- On the inSync Master Management Console menu bar, click Profiles.
- Click the profile for which you want to include emails for backup on Linux.
- Click the Devices tab, click Laptops & Desktops > Edit. The Edit Device Backup Configuration window appears.
- Click the Linux tab.
- Select the Email check box.
- In the Email client to backup list, select the email client that you want to back up.
- Provide the appropriate information for each field.
- Click Save. | https://docs.druva.com/001_inSync_Cloud/Cloud/020_Backup_and_Restore/020_Backup_and_Restore/020_Configure_folders_for_backup_on_user_laptops/040_Include_emails_for_backup/003_Include_emails_for_backup_on_Linux | 2019-03-18T20:27:06 | CC-MAIN-2019-13 | 1552912201672.12 | [array(['https://docs.druva.com/@api/deki/files/3644/tick.png?revision=2',
'File:/tick.png'], dtype=object)
array(['https://docs.druva.com/@api/deki/files/3644/tick.png?revision=2',
'File:/tick.png'], dtype=object)
array(['https://docs.druva.com/@api/deki/files/3644/tick.png?revision=2',
'File:/cross.png'], dtype=object)
array(['https://docs.druva.com/@api/deki/files/3644/tick.png?revision=2',
'File:/tick.png'], dtype=object) ] | docs.druva.com |
Contents
Chat Messages in Queues
When a chat server terminates unexpectedly or the server goes offline, the chats that were hosted on that chat server are terminated at the client end. However the chats remain in the system and continue to route to Workspace Desktop Edition (previously Interaction Workspace (IWS)).
IWS presents the chat, but displays a message that it cannot connect to the chat server.
When the agent can eventually mark the chat as done, IWS closes the chat in the agent IWS session, but it routes again, landing on any available agent IWS. This can occur for up to an hour.
The following is an example log entry:
14-03-28 12:17:10.138 [ChannelDefault] WARN ESDK - Channel tcp://ctizgesmipr002:4125/ closed 14-03-28 12:17:10.139 [ChannelDefault] WARN ESDK - Channel closing [Name] ChatSessionChannel.Id001_90f30c5c-63c4-438b-a1b7-72c2dd7a8fc9 [Uri] tcp://ctizgesmipr002:4125/ has 1 requests pending. They are lost 14-03-28 12:17:10.139 [ChannelDefault] DEBUG ESDK - Chat strategy 'ResyncStrategy' Processing msg [Name] undefined <check channel evenr> [EndPoint] tcp://ctizgesmipr002:4125/ 14-03-28 12:17:10.141 [ChannelDefault] DEBUG ESDK - Chat strategy 'ResyncStrategy' Found 1 related channel for Event undefined <check channel event> 14-03-28 12:17:10.147 [ChannelDefault] WARN edia.InteractionChat - Protocol Closed message:'Genesyslab.Platform.Commons.Protocols.ProtocolException: Exception occured during channel opening ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 172.203.217.149:4125 at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult) at Genesyslab.Platform.Commons.Connection.CommonConnection.AsyncConnect(IAsyncResult res) — End of inner exception stack trace ---' Previous Channel State:'Opening, [InteractionChat: Id001/0006Ka9HFHRR0T2B]'
Resolution
Use the workflow diagram to stop chat interactions from being routed to an agent. The workflow must determine if a chat session is still accessible before sending the interaction to an agent. One of the possible solutions could be to use "dummy" chat ESP messages. If such a message could not be delivered to Chat Server (see below details about errors), this will indicate not to route the interaction to the agent (and so the interaction could be stopped in workflow). The workflow could make several attempts (in the case where chat High Availability mode will be enabled) before finally stopping the attempt to route.
In order to hide these dummy messages from chat parties, the following could be done:
- Use some special keywords in the message and modify the web chat application not to show those to the customer. Agent still will be seeing them.
- Use the "Visibility" parameter of the chat ESP message request. It could have values ALL (default), INT (only agents) or VIP (only supervisors). Setting Visibility=VIP will hide the message from customer and agent (only supervisor will see those and it will be saved in final transcript in Universal Contact Server).
Errors (in the Interaction Server log) when trying to deliver chat ESP message are as follows:
If ChatServer is not running (was not restarted)
00:04:08.485 Trc 24112 Cannot find appropriate 3rd-party server: name: [any], type: ChatServer 00:04:08.485 Trc 24102 Sending to Universal Routing Server: URServer: 'EventError' (52) message: … AttributeErrorCode [int] = 1 AttributeErrorMessage [str] = "Not found by type" …
After ChatServer was restarted and running
00:18:32.532 Trc 26015 Received message 'ExternalServiceFault' ('502') from client 'ChatServer' - Third party server:0:920, message attributes: attr_envelope [list, size (unpacked)=488] = 'Parameters' [list] = (size=80) 'FaultCode' [str] = "100" 'FaultString' [str] = "interaction with specified id was not found" 'Service' [str] = "Chat" 'Method' [str] = “Message""
Feedback
Comment on this article: | https://docs.genesys.com/Documentation/Composer/latest/Help/ChatMessagesinQueues | 2019-03-18T19:37:52 | CC-MAIN-2019-13 | 1552912201672.12 | [] | docs.genesys.com |
Contents Performance Analytics and Reporting Previous Topic Next Topic Collect historical data Subscribe Log in to subscribe to topics and get notified when content changes. ... SAVE AS PDF Selected Topic Topic & Subtopics All Topics in Contents Share Collect historical data Run a historical data collection job to collect scores and snapshots for existing records. Before you begin Role required: pa_data_collector or admin About this taskWhen collecting data for the first time, such as for a new indicator, run historical data collection once to generate scores and snapshots for existing records. Procedure Navigate to Performance Analytics > Data Collector > Jobs. Select a historical data collection job, such as [PA Change] Historic Data Collection. In the Collection parameters section, configure the date range to collect data from using one of the following methods. OptionDescription Fixed date range In the Operator field, select Fixed. Specify the date range to collect data from using the Fixed start and Fixed end fields. Relative to the current date In the Operator field, select Relative. Specify the relative date range to collect data from using the Relative start, Relative end, Relative start interval, and Relative end interval fields. Click Execute Now. What to do next After collecting historical data, use a scheduled data collection job to collect new scores regularly. On this page Send Feedback Previous Topic Next Topic | https://docs.servicenow.com/bundle/istanbul-performance-analytics-and-reporting/page/use/performance-analytics/task/t_RunHistoricalDataCollection.html | 2019-03-18T20:17:56 | CC-MAIN-2019-13 | 1552912201672.12 | [] | docs.servicenow.com |
TOC & Recently Viewed
Recently Viewed Topics
Certificate Management
In this section, custom certificates for PVS can be installed or removed. These certificates are used to access the PVS Web interface with a proper CA certificate. The top section contains a browse dialog for the Server Certificate and Server Key File and optionally the Intermediate and Custom Root CA Certificates that are used for PVS web user interface browser access, while the bottom section (CA Certificate) is used for client to PVS server certificate-based communications. | https://docs.tenable.com/appliance/4_6/Content/4.6.0_GuideTopics/PVSCertificateManagement.htm | 2019-03-18T19:52:15 | CC-MAIN-2019-13 | 1552912201672.12 | [] | docs.tenable.com |
- NAME
- DESCRIPTION
- METHODS
- CAVEATS
- INTERNALS
- SEE ALSO
- AUTHOR
NAME
Set::Infinite::Basic - Sets of intervals 6 =head1 SYNOPSIS
use Set::Infinite::Basic; $set = Set::Infinite::Basic->new(1,2); # [1..2] print $set->union(5,6); # [1..2],[5..6]
DESCRIPTION
Set::Infinite::Basic is a Set Theory module for infinite sets.
It works on reals, integers, and objects.
This module does not support recurrences. Recurrences are implemented in Set::Infinite.
METHODS
empty_set
Creates an empty_set.
If called from an existing set, the empty set inherits the "type" and "density" characteristics.
universal_set
Creates a set containing "all" possible elements.
If called from an existing set, the universal set inherits the "type" and "density" characteristics.
until
Extends a set until another:
0,5,7 -> until 2,6,10
gives
[0..2), [5..6), [7..10)
Note: this function is still experimental.
copy
clone
Makes a new object from the object's data.
Mode functions:
$set = $set->real; $set = $set->integer;
Logic functions:
$logic = $set->intersects($b); $logic = $set->contains($b); $logic = $set->is_null; # also called "is_empty"
Set functions:
$set = $set->union($b); $set = $set->intersection($b); $set = $set->complement; $set = $set->complement($b); # can also be called "minus" or "difference" $set = $set->symmetric_difference( $b ); $set = $set->span; result is (min .. max)
Scalar functions:
$i = $set->min; $i = $set->max; $i = $set->size; $i = $set->count; # number of spans
Overloaded Perl functions:
print sort, <=>
Global functions:
Internal functions:
$set->fixtype; $set->numeric;
CAVEATS
.
INTERNALS;
SEE ALSO
Set::Infinite
AUTHOR
Flavio S. Glock <[email protected]> | http://docs.activestate.com/activeperl/5.22/perl/lib/Set/Infinite/Basic.html | 2019-03-18T20:27:26 | CC-MAIN-2019-13 | 1552912201672.12 | [] | docs.activestate.com |
Recently Viewed Topics
You can select one of the following enforcement actions for a policy in Tenable.io Container Security:
Use this action if you want to query Tenable.io Container Security for the policy compliance status of scanned container images.
If a scan of a container image identifies the condition specified in the policy, any API queries for the policy compliance status of the container image receive a false response (security test failed). For more information, see the description of the /policycompliance endpoint in the Tenable.io Container Security API guide.
This action is useful if you integrate Tenable.io Container Security with your CI/CD pipeline. For example, you can configure Jenkins to mark a build unstable if a container receives a failed compliance status from Tenable.io Container Security.
Use this action if you want to block pulls from the Tenable.io Container Security registry of any container image where a scan has identified the condition specified in the policy. For more information, see Pull from the Registry.. | https://docs.tenable.com/cloud/Content/ContainerSecurity/PolicyEnforcementSettings.htm | 2019-03-18T19:54:46 | CC-MAIN-2019-13 | 1552912201672.12 | [] | docs.tenable.com |
.
Once you activated the theme those locations will be created automatically so you can jump over the creating a new menu part but if you have a menu already created you must assign it to the location inside the Manage Locations tab.
Managing Navigation Menus
- Go to Appearance ▸ Menus and select a menu that you want to edit.
- Use the left panel of the page to add a new navigation item into the menu.
- Custom post types such as Product Showcase, Team, Testimonial, WooCommerce Products will not be visible in the available item list as default. You must activate them via the screen options. Please check these two screenshots;
Menu items are dragged and dropped into the menu containers. Try some of the WordPress menu tutorials on youtube.com as they explain all.
WordPress 3.0 menu system
WordPress 3.0 menu custom links
Editing Menu Items
Once you have these fields visible in the menu item you can
- Extend a menu item and click the CSS Classes field then a list of available icons will appear that allows you select and set an icon to the menu item. To add icons to a menu items make sure in the in the screen options you have enabled the CSS Classes.
- Add a sub text to the description field to display below the menu item’s label text. To add a description text to a menu items make sure in the in the screen options you have enabled the Description.
- Select Multi-Column Menu option to split the sub menus into columns.
Mobile Navigation
Be aware that the mobile navigation is different then the one you see in your computer while resizing the browser window. Mobile menu will be looking different then the desktop version and some of those setting will not be visible in the mobile view such as icons. If you want to have different menu than the main menu only for the mobile screens you can use the “Mobile Navigation” menu location. | http://docs.rtthemes.com/document/navigations-2/ | 2019-03-18T19:41:54 | CC-MAIN-2019-13 | 1552912201672.12 | [] | docs.rtthemes.com |
Case Data options
case-data.float-separator
- Default Value: ""
- Valid Values: A valid float separator. Typical float separators are: '.' (period), ',' (comma), and '\' (backslash).
- Changes take effect: Immediately.
- Description: Specifies the float separator that is used for Case data. This option should be used when the decimal symbol in the regional settings of the agent workstation is different from the one in the attached data.
This page was last modified on October 26, 2018, at 07:33.
Feedback
Comment on this article: | https://docs.genesys.com/Documentation/IW/latest/Dep/CaseDataOptions | 2019-03-18T20:06:53 | CC-MAIN-2019-13 | 1552912201672.12 | [] | docs.genesys.com |
8.5.000.36
Stat Server Release Notes
Helpful Links
Releases Info
Product Documentation
Stat Server, Real-Time Metrics Engine
Genesys Products
What's New
This release includes only resolved issues.
Resolved Issues
This release contains the following resolved issue:
This release corrects the issue with intermittent inability of URS to reconnect to Stat Server, running on Windows, after Stat Server switchover. Previously, in such scenarios, URS could fail to connect to Stat Server. (SS-6444)
Upgrade Notes
No special procedure is required to upgrade to release 8.5.000.36.
This page was last modified on September 11, 2015, at 11:38.
Feedback
Comment on this article: | https://docs.genesys.com/Documentation/RN/latest/stat-svr85rn/stat-svr8500036 | 2019-03-18T19:20:04 | CC-MAIN-2019-13 | 1552912201672.12 | [] | docs.genesys.com |
Enable manage.include.files for Yarn
Using Ambari Web, enable automated host participation by adding manage.include.files properties to the YARN configuation.
- Using Ambari Web, browse to .
- In the Advanced yarn-site configuration section, add the manage.include.files=true property.
- In the Custom yarn-site configuration section, ensure that the yarn.resourcemanager.nodes.include-pathproperty appears and that it is set to a valid location of the YARN Resource Manager on the filesystem .yarn.resourcemanager.nodes.include-path=/etc/hadoop/conf/yarn.include
- Restart services, as prompted by Ambari. | https://docs.hortonworks.com/HDPDocuments/Ambari-2.7.1.0/administering-ambari/content/amb_enable_manageincludefiles_yarn.html | 2019-03-18T20:30:08 | CC-MAIN-2019-13 | 1552912201672.12 | [] | docs.hortonworks.com |
Delete checklist or a template On this page Send Feedback Previous Topic Next Topic | https://docs.servicenow.com/bundle/istanbul-platform-user-interface/page/use/using-forms/task/t_ActivateChecklists.html | 2019-03-18T20:15:06 | CC-MAIN-2019-13 | 1552912201672.12 | [] | docs.servicenow.com |
Inverting a Colour Selection
When you need to select all colour swatches but one, or select only a few swatches here and there, it might be faster to select the only colour you do not need in order to select and invert the selection.
- In the Colour view, select the colour swatch you DO NOT want to have in your final selection.
- Do one of the following: | https://docs.toonboom.com/help/harmony-12-2/essentials/ink-paint/invert-colour-selection.html | 2019-03-18T19:30:55 | CC-MAIN-2019-13 | 1552912201672.12 | [array(['../Skins/Default/Stylesheets/Images/transparent.gif', 'Closed'],
dtype=object)
array(['../Resources/Images/HAR/Trad_Anim/005_Ink_Paint/har11_select_colour3.png',
None], dtype=object) ] | docs.toonboom.com |
Enable logging for an encryption rule to record information about the packets it processes. All sessions matching the rule will be logged.
About this task
Logging is disabled by default. On ESXi hosts, logs are stored in the /var/run/log/dnepktlogs.log file. Depending on the number of rules, a typical encryption rule section might generate large amounts of log information, which can affect performance.
Procedure
- From your browser, log in to an NSX Manager at.
- Select Encryption from the navigation panel.
- Click the Rules tab if it is not already selected.
- Click the rule for which you want to enable or disable logging.
- Click the Actions menu and select or .
- Click Save.
- Click Save again to confirm. | https://docs.vmware.com/en/VMware-NSX-T/2.0/com.vmware.nsxt.admin.doc/GUID-77F131C2-7678-475C-A039-E383108FCA93.html | 2019-03-18T19:37:44 | CC-MAIN-2019-13 | 1552912201672.12 | [] | docs.vmware.com |
This specification defines a vocabulary and resource shapes for the Change Management domain.
TC members should send comments on this specification to the TC’s email list. Others should send comments to the TC’s public comment list [email protected], after subscribing to it by following the instructions at the “Send A Comment” button on the TC’s web page at.
This specification2]
OSLC Change Management Version 3.0. Part 2: Vocabulary. Edited by Jim Amsden, Samuel Padgett, and Steve Speicher. 24 August 2018. OASIS Committee Specification a vocabulary and resource shapes for common Change Management resources. The intent is to define resources needed to support common integration scenarios and not to provide a comprehensive definition of a Change Request. The resource formats may not match exactly the native models supported by change addition to the namespace URIs and namespace prefixes
oslc,
rdf,
dcterms and
foaf defined in the OSLC Core specification, OSLC CM defines the namespace URI of with a namespace prefix of
oslc_cm
This specification also uses these namespace prefix definitions:[OSLCRM][OSLCQM]
This specification defines the ChangeRequest superclass, and a number of specific, commonly occurring subclasses, properties and values. Servers may define additional ChangeRequest subclasses and provide additional properties as needed.
The namespace URI for this vocabulary is:
All vocabulary URIs defined in the OSLC Change Management (CM) namespace.
ChangeNotice, ChangeRequest, Defect, Enhancement, Priority, ReviewTask, Severity, State, Task
affectedByDefect, affectsPlanItem, affectsRequirement, affectsTestResult, authorizer, blocksTestExecutionRecord, closeDate, implementsRequirement, parent, priority, relatedChangeRequest, relatedTestCase, relatedTestExecutionRecord, relatedTestPlan, relatedTestScript, severity, state, status, testedByTestCase, tracksChangeSet, tracksRequirement
ChangeNotice is an RDFS class.
Represents an assignment notification of a change request. May be used also to bestow authority onto the assigned user to effect the changes.
ChangeRequest is an RDFS class.
The CM Change Request resource.
Defect is an RDFS class.
A software or product defect.
Enhancement is an RDFS class.
A request for new functionality.
Priority is an RDFS class.
Defines the possible oslc_cm:priority property values.
ReviewTask is an RDFS class.
A request to make a change and review the change.
Severity is an RDFS class.
Defines the possible oslc_cm:severity property values.
State is an RDFS class.
Defines the possible oslc_cm:state property values.
Task is an RDFS class.
An executable and trackable activity.
affectedByDefect is an RDF property.
Change request is affected by a reported defect. It is likely that the target resource will be an oslc_cm:Defect.
affectsPlanItem is an RDF property.
Change request affects a plan item. It is likely that the target resource will be an oslc_cm:ChangeRequest.
affectsRequirement is an RDF property.
The ChangeRequest affects a Requirement. It is likely that the target resource will be an oslc_rm:Requirement.
affectsTestResult is an RDF property.
Associated resource that is affected by this Change Request. It is likely that the target resource will be an oslc_qm:TestResult.
blocksTestExecutionRecord is an RDF property.
Associated resource that is blocked by this Change Request. It is likely that the target resource will be an oslc_qm:TestExecutionRecord.
closeDate is an RDF property.
The date at which no further activity or work is intended to be conducted.
implementsRequirement is an RDF property.
The ChangeRequest implements the associated Requirement. It is likely that the target resource will be an oslc_rm:Requirement.
parent is an RDF property.
The related parent change requests of the subject change request.
priority is an RDF property.
Used to indicate the relative importance of ChangeRequests. It is likely that the target resource will be an oslc_cm:Priority.
relatedTestCase is an RDF property.
Related test case resource. It is likely that the target resource will be an oslc_qm:TestCase.
relatedTestExecutionRecord is an RDF property.
Related to a test execution resource. It is likely that the target resource will be an oslc_qm:TestExecutionRecord.
relatedTestPlan is an RDF property.
Related test plan resource. It is likely that the target resource will be an oslc_qm:TestPlan.
relatedTestScript is an RDF property.
Related test script resource. It is likely that the target resource will be an oslc_qm:TestScript.
severity is an RDF property.
Used to indicate the severity or potential impact of a defect. It is likely that the target resource will be an oslc_cm:Severity.
state is an RDF property.
Used to indicate the status of the change request.
status is an RDF property.
Used to indicate the status of the change request based on values defined by the service provider. Most often a read-only property. It is likely that the target resource will be a string corresponding to an oslc_cm:State value.
testedByTestCase is an RDF property.
Test case by which this change request is tested. It is likely that the target resource will be an oslc_qm:TestCase.
tracksChangeSet is an RDF property.
Tracks a change set resource. It is likely that the target resource will be an oslc_config:ChangeSet.
tracksRequirement is an RDF property.
Tracks the associated Requirement or Requirement ChangeSet resources. It is likely that the target resource will be an oslc_rm:Requirement.
Property value types that are not defined in the following sections, are defined in OSLC Core - Defining OSLC Properties
Naming convention for relationship properties follows this pattern:
The Change Request resource properties are not limited to the ones defined in this specification, service providers may provide additional properties. It is recommended that any additional properties exist in their own unique namespace and not use the namespaces defined in these specifications.
ChangeRequest
ChangeNotice
A software or product defect. Used by Quality Management tools to report defects in testing.
Defect
Enhancement
ReviewTask
Task
Defines a set of standard values for property oslc_cm:status.
State
Priority
Severity
NEEDS UPDATE: Improve descriptions.
Priority and severity example:
@prefix ex: <> . @prefix oslc: <> . @prefix oslc_cm: <> . @prefix rdfs: <> . @prefix dcterms: <> . @prefix skos: <> . <> a oslc_cm:Defect ; dcterms:identifier "00002314" ; oslc:shortTitle "Bug 2314" ; dcterms:title "Invalid installation instructions" ; oslc_cm:priority oslc_cm:High ; oslc_cm:severity <> . <> a oslc_cm:Severity; dcterms:title "Severe - HOT" ; skos:narrower oslc_cm:Critical ; ex:icon <>.
This section is non-normative. | http://docs.oasis-open.org/oslc-domains/cm/v3.0/cm-v3.0-part2-change-mgt-vocab.html | 2019-03-18T19:48:46 | CC-MAIN-2019-13 | 1552912201672.12 | [] | docs.oasis-open.org |
. 4 (1985)
Up
Up
74 Op. Att'y Gen. 4, 4 (1985)
Public Records;
Prosecutors' case files are not subject to access under the public records laws. OAG 2-85
January 10, 1985
74 Op. Att'y Gen. 4, 4 (1985)
Bartley G. Mauch
,
District Attorney
Sauk County
74 Op. Att'y Gen. 4, 4-5 (1985)
In your letter of November 17, 1983, you express concern about access by the public to investigative reports in the prosecutor's office relating to alleged matricide and two counts of sororicide. In effect, your letter asks for my opinion as to the extent to which prosecutors' files are subject to inspection under the public records law.
74 Op. Att'y Gen. 4, 5 (1985)
Section 19.35(1)(a), Stats., states:
74 Op. Att'y Gen. 4, 5 (1985).
74 Op. Att'y Gen. 4, 5 (1985)
As stated in one of our recent opinions, 73 Op. Att'y Gen. 20-21 (1984) at 1-2:
74 Op. Att'y Gen. 4, 5 (1985)
This provision recognizes three possible bases for denying access to public records: (1) express statutory exemptions; (2) exemptions under the open meetings law if the requisite demonstration is made; and (3) common law principles. The crux of the common law on public records is the "balancing test" which provides that the custod).
74 Op. Att'y Gen. 4, 5 (1985)
The common law also recognized some limitations on the public's right of access to public records.
International Union v. Gooding
, 251 Wis. 362, 372, 29 N.W.2d 730 (1947).
74 Op. Att'y Gen. 4, 5 (1985)
A.
Express statutory exemptions
.
74 Op. Att'y Gen. 4, 5 (1985)
Section 19.36(1), Stats., provides:
74 Op. Att'y Gen. 4, 5-6 (1985)).
74 Op. Att'y Gen. 4 (1985)
There is no statute specifically exempting prosecutors' files from disclosure. Therefore, section 19.36(1) is not available as a basis for generally denying access to such records under the public records law.
74 Op. Att'y Gen. 4, 6 (1985)
Section 19.36(2) establishes a categorical exemption for "investigative information obtained for law enforcement purposes..." if secrecy is required by federal law or regulations or as a condition to receipt of aids by this state. I am not aware of any federal law that would trigger the application of this subsection.
74 Op. Att'y Gen. 4, 6 (1985)
B.
Exemptions under the open meetings law
.
74 Op. Att'y Gen. 4, 6 (1985)
It is probable that most papers in a prosecutor's file arguably fall within the purview of the exemptions to the open meetings law set forth in section 19.85(1)(d), (f) and (g). They authorize a closed meeting for the purpose of:
74 Op. Att'y Gen. 4, 6 (1985)
(d)
Considering specific applications of probation or parole, or considering strategy for crime detection or prevention.
74 Op. Att'y Gen. 4, 6 (1985)
....
74 Op. Att'y Gen. 4, 6 .
74 Op. Att'y Gen. 4, 6 (1985)
(g)
Conferring with legal counsel for the governmental body who is rendering oral or written advice concerning strategy to be adopted by the body with respect to litigation in which it is or is likely to become involved.
74 Op. Att'y Gen. 4, 6 (1985)
However, the fact that a record falls within the purview of an exemption to the open meetings law is not determinative. Section 19.35(1)(a) requires in addition that the custodian make "a specific demonstration that there is a need to restrict public access at the time that the request to inspect or copy the record is made."
74 Op. Att'y Gen. 4, 6 (1985)
We have recently interpreted this statute as follows:
74 Op. Att'y Gen. 4, 6-7 (1985)
The statute recognizes that in the exemption provisions the Legislature has identified categories of sensitive information, but the Legislature has not mandated that all such information be withheld all the time. In my opinion the exemptions under section 19.85 may not be used as the basis for general blanket exceptions under the public records law. When exemptions to the open meetings law are relied on, section 19.35(1)(a) requires a case-by-case determination with respect to each request as of the time of the request. Any blanket custodial policy would be contrary to this requirement.
74 Op. Att'y Gen. 4, 7 (1985)
73 Op. Att'y Gen. 20 (1984) at 3.
74 Op. Att'y Gen. 4, 7 (1985)
C.
Common law principles
.
74 Op. Att'y Gen. 4, 7 (1985)
Discussing the earlier
Gooding
case which construed the first general public record statute enacted in 1917, the supreme court stated the following in
State ex rel. Youmans v. Owens
, 28 Wis. 2d 672, 680-81, 137 N.W.2d 470, 139 N.W.2d 241 (1965):
74 Op. Att'y Gen. 4, 7 (1985)
However, merely because the papers sought to be inspected, although not required by law to be filed or kept by defendant, were in his lawful possession, did not automatically entitle petitioner to inspect them. The inspection provisions of sec. 18.01(1) and (2), Stats., were contained in a revisor's bill and prior to that enactment there existed no statute which attempted to spell out the rights of members of the public to inspect public records. The revisor's notes to sub. (2) of sec. 18.01 stated that this subsection "is believed to give expression to the general implied right of the public to consult public records." The court in the
Gooding Case
quoted this statement and then declared:
74 Op. Att'y Gen. 4, 7 (1985)
"In view of the presumption that a revisor's bill is not intended to change the law we conclude that this is the scope of the section. While it is possible to contend that the words are so clear as not to be subject to construction
we are of the view that the common-law right of the public to examine records and papers in the hands of an officer has not been extended
.
74 Op. Att'y Gen. 4, 7-8 (1985)
"We shall not go into the scope of the common-law right exhaustively or attempt to document our observations upon it. list could be expanded but the foregoing is enough to illustrate that in certain situations a paper may in the public interest be withheld from public inspection.
Whatever limitations existed at common law still exist under sec. 18.01(2), Stats.
"
74 Op. Att'y Gen. 4, 8 (1985)
An authoritative statement of the common-law right of inspection of public documents is that made by the Vermont court in
Clement v. Graham
as follows:
74 Op. Att'y Gen. 4, 8 (1985)
"We think it may be safely said that at common law, when not detrimental to the public interest, the right to inspect public records and public documents exists with all persons who have a sufficient interest in the subject-matter thereof to answer the requirements of the law governing that question."
74 Op. Att'y Gen. 4, 8 (1985)
Thus the right to inspect public documents and records at common law is not absolute. There may be situations where the harm done to the public interest may outweigh the right of a member of the public to have access to particular public records or documents. Thus, the one must be balanced against the other in determining whether to permit inspection.
74 Op. Att'y Gen. 4, 8 (1985)
The preservation of common law limitations is codified in the most recently enacted public records statutes. Section 19.35(1)(a) reads in part: "RIGHT TO INSPECTION. (a) Except as otherwise provided by law, any requester has a right to inspect any record. Substantive common law principles construing the right to inspect, copy or receive copies of records shall remain in effect."
74 Op. Att'y Gen. 4, 8 (1985)
As noted by the court in
Youmans
above, one example of a common law limitation is documentary evidence in the hands of a district attorney. 28 Wis. 2d at 680. Also,
Gooding
, 251 Wis. at 372. This limitation on the public records law was also acknowledged at 68 Op. Att'y Gen. 17, 19 (1979), although that opinion dealt with the issue of preservation of public records and not access. As examples of public records that needed to be preserved, the opinion cited "statements of witnesses, reports of scientific testing, charging documents, transcripts, motions with supporting affidavits and legal memoranda and written decisions of the court." The opinion continued:
74 Op. Att'y Gen. 4, 8-9 (1985)
In identifying these documents as public records I do not mean to intimate that they necessarily are open to public inspection. It long has been the rule that documentary evidence in the files of a district attorney constitutes an exception to the rule permitting citizens to inspect papers in the possession of public officials.
74 Op. Att'y Gen. 4, 9 (1985)
The phrase "documentary evidence" could be interpreted in the very narrow evidentiary sense,
i.e.
, a document that may be admissible as evidence at trial.
See
ch. 889, Stats. Or it could be interpreted in a broader sense to cover the papers in the file which constitute the physical information available to the prosecutor or papers created by the prosecutor. The former interpretation seems too narrow. The latter would be broad enough to be coextensive with the definition of "record" in section 19.32(2).
74 Op. Att'y Gen. 4, 9 (1985)
I think the answer is best arrived at somewhat indirectly by evaluating the rights of a defendant with respect to the prosecutor's file.
74 Op. Att'y Gen. 4, 9 (1985)
One commentator found that:
74 Op. Att'y Gen. 4, 9 (1985)
Wisconsin has consistently held to the common law doctrine that the defendant is not entitled to inspect the evidence and other information which the prosecution has gathered. The statement of the supreme court whenever the issue was raised has been, "One accused of crime enjoys no right to an inspection of evidence relied upon by the public authorities for his conviction."
74 Op. Att'y Gen. 4, 9 (1985)
49 Marq. L. Rev. 736, 746 (1965-66), with the following footnote to the quoted material:
74 Op. Att'y Gen. 4, 9 (1985)
State
ex rel.
Spencer v. Freedy, 198 Wis. 388, 392; 223 N.W. 861, 862 (1929). This same statement is repeated in State
ex rel.
Schroeder v. Page, 206 Wis. 611, 240 N.W. 173 (1932); Steensland v. Hoppmann, 213 Wis. 593, 252 N.W. 146 (1934); State v. Herman, 219 Wis. 267, 262 N.W. 718 (1935). A similar statement is found in Santry v. State, 67 Wis. 65, 30 N.W. 226 (1886).
74 Op. Att'y Gen. 4, 9 (1985)
Now we could add
State v. Miller
, 35 Wis. 2d 454, 474, 151 N.W.2d 157 (1967).
74 Op. Att'y Gen. 4, 9 (1985)
The commentator found Wisconsin to be a conservative adherent to this common law restriction (49 Marq. L. Rev. at 749) and supposed that any statutory departure would be strictly construed (49 Marq. L. Rev. at 748).
74 Op. Att'y Gen. 4, 9-10 (1985)
The United States Supreme Court has created a qualification to this general rule. It requires prosecutors to divulge evidence that is material either to guilt or to punishment as a matter of constitutional "due process."
Brady v. State of Maryland
, 373 U.S. 83, 86 (1963). However, even so, in this state the defense does not have access to the prosecutor's file prior to the preliminary examination unless it can show a particularized need.
Matter of State ex rel. Lynch v. County Ct.
, 82 Wis. 2d 454, 468, 262 N.W.2d 773 (1978). The prosecutor may deny inspection, and if it is eventually established that evidence was wrongfully withheld, the remedy is a new trial. 82 Wis. 2d at 468.
74 Op. Att'y Gen. 4, 10 (1985)
In my opinion, logic compels the conclusion that if at common law a defendant could not have access to a prosecutor's file in his own case prior to trial, neither could the general public. Certainly the defendant's interest in his own file exceeds that of the general public. The defendant's interest is to know the accusations and evidence for and against him so he can evaluate his exposure and prepare his defense. Yet the defendant was denied access under the common law. It would be perverse to then allow access by everyone but the defendant by way of the public records law. Also it is obvious that the clear limitations on discovery could be circumvented easily if the same information could be obtained by the defendant by way of a public records request.
74 Op. Att'y Gen. 4, 10 (1985)
In my opinion, this logic amplifies the meaning of the more general statements at common law acknowledging limitations on access to documentary evidence in prosecutors' files. I believe that at common law any right of access under the public records law could not surpass the defendant's rights to discovery. Given the very limited purposes for which and circumstances under which a defendant could have any discovery of a prosecutor's file under common law, it must follow that the common law limitations on access are a complete bar to access to the prosecutor's file.
74 Op. Att'y Gen. 4, 10 (1985)
This issue has been considered with mixed results in the appellate courts of New York. One view is that material that is exempt from discovery in the context of litigation is exempt from disclosure under their public records law. A leading case is
Westchester Rockland, Etc. v. Mosczydlowski
, 396 N.Y.S.2d 857, 58 A.D.2d 234 (1977). Contrapuntal is the decision in
Lawler, Matusky & Skelly Engineers v. Abrams
, 443 N.Y.S.2d 973, 111 Misc. 2d 356 (1981).
74 Op. Att'y Gen. 4, 10-11 (1985)
In my opinion the logic in favor of transferring common law limitations on discovery in criminal cases to the public records law is more persuasive. Therefore, it is my opinion that there is a general common law limitation against access to prosecutor's files prior to completion of a trial.
74 Op. Att'y Gen. 4, 11 (1985)
The overriding interests that justify this limitation on the public's general "right to know" will often coincide with the interests recognized as justifying the secrecy of John Doe proceedings, to wit:
74 Op. Att'y Gen. 4, 11 (1985)
(1)
keeping a John Doe target from fleeing, or an arrested defendant from knowledge which might cause him to flee;
74 Op. Att'y Gen. 4, 11 (1985)
(2)
preventing defendants from collecting perjured testimony for the trial;
74 Op. Att'y Gen. 4, 11 (1985)
(3)
preventing those interested in thwarting the inquiry and tampering with prospective testimony or secreting evidence;
74 Op. Att'y Gen. 4, 11 (1985)
(4)
freeing witnesses from the threat of immediate retaliation; and
74 Op. Att'y Gen. 4, 11 (1985)
(5)
preventing testimony which may be mistaken or untrue or irrelevant from becoming public.
74 Op. Att'y Gen. 4, 11 (1985)
In re Wis. Family Counseling Services v. State
, 95 Wis. 2d 670, 677, 291 N.W.2d 63 (Ct. App. 1980).
74 Op. Att'y Gen. 4, 11 (1985)
One could also add the concern for pretrial publicity.
74 Op. Att'y Gen. 4, 11 (1985)
Also present to support the secrecy of prosecutors' files, although not available to justify the blanket exemption by itself, is the doctrine of attorney work product which protects papers prepared by an attorney with respect to particular pending or imminent litigation.
Youmans
, 28 Wis. 2d at 684. The United States Supreme Court has held recently that the protection of attorney's work product continues even after the litigation is over.
FTC v. Grolier, Inc.
, 103 S.Ct. 2209, 2215 (1983).
74 Op. Att'y Gen. 4, 11 (1985)
As stated in section 19.31, "it is declared to be the public policy of this state that all persons are entitled to the greatest possible information regarding the affairs of government and the official acts of those officers and employes who represent them."
See
Newspapers, Inc. v. Breier
, 89 Wis. 2d 417, 433-38, 279 N.W.2d 179 (1979). The public interest to be served is not so much the "curiosity" interest in what accusations have been made and what evidence has been gathered against an individual. The public interest underlying the public records law is the interest in monitoring and evaluating how public officials discharge their responsibilities.
74 Op. Att'y Gen. 4, 12 (1985)
With respect to the performance of a prosecutor in a particular case, this evaluation will be much more knowledgeable and objective once the trial is over. It would likely unnecessarily interfere with the administration of justice if the public were allowed to look over the prosecutor's shoulder and proclaim what it sees while a prosecutor is preparing or presenting a case. At least, it is my opinion that the public's right to know and the interest in effective administration of the criminal justice system are harmonized and adequately served if prosecutors' files are exempt from disclosure during the investigative, pretrial and trial stages.
74 Op. Att'y Gen. 4, 12 (1985)
The next question then is whether prosecutors' files are open to public inspection after the trial. Employing the logic used above, it is appropriate to explore the extent to which a defendant has access to the state's file following the trial. We find once again that a defendant's rights are very limited.
74 Op. Att'y Gen. 4, 12 (1985)
The common law in this state is that subsequent to a trial a defendant has no right to inspect relevant portions of the state's files to determine whether they contained evidence in any way useful or helpful to him. Access would be constitutionally required only if there were a specific allegation that the prosecution had suppressed evidence which due process would require it to disclose.
Britton v. State
, 44 Wis. 2d 109, 118-19, 170 N.W.2d 785 (1969). Again, following the rationale used above, if a defendant has only a severely limited right to inspect the state's file for the defendant's case, it necessarily follows that the public at large cannot have a greater right by way of the public records law.
Down
Down
/misc/oag/archival/_155
false
oag
/misc/oag/archival/_155
oag/vol74-4
oag/vol74-4
section
true
»
Miscellaneous Documents
»
Opinions of the Attorney General
»
Opinions of the Attorney General - prior to 2000
»
74 Op. Att'y Gen. 4 | http://docs-preview.legis.wisconsin.gov/misc/oag/archival/_155 | 2019-03-18T19:20:49 | CC-MAIN-2019-13 | 1552912201672.12 | [] | docs-preview.legis.wisconsin.gov |
enable filters in Shop?
The Shop Filters area will show up as soon as it’s populated with at least one widget. Navigate to Appearance > Customize > Widgets > Shop Filters and press Add Widget button, you can add widgets by clicking the available widgets.
To preview the Shop Filters click the Filters button.
| http://wp-docs.jmstheme.com/erado/how-to-enable-filters-in-shop/ | 2019-03-18T19:34:18 | CC-MAIN-2019-13 | 1552912201672.12 | [array(['https://thehanger.wp-theme.help/hc/article_attachments/360001043549/Customize_Add_Widgets_Shop_Filters_TheRetailerPRO_WordPress.png',
'Customize_Add_Widgets_Shop_Filters_TheRetailerPRO_WordPress.png'],
dtype=object)
array(['https://thehanger.wp-theme.help/hc/article_attachments/360001373129/shop-filters.jpg',
'shop-filters.jpg'], dtype=object) ] | wp-docs.jmstheme.com |
Configure the domain controller to trust the StorageZones Controller for delegation
Note: This section applies only to StorageZone Connectors.
To support NTLM or Kerberos authentication on network shares or SharePoint sites, configure the domain controller, as follows.
On the domain controller for the StorageZones domain, click Start > Administrative Tools > Active Directory Users and Computers.
Expand domain, and expand the Computers folder.
In the right pane, right-click the StorageZonesname.
| https://docs.citrix.com/en-us/storagezones-controller/5-0/install/configure-domain-controller.html | 2019-03-18T20:45:06 | CC-MAIN-2019-13 | 1552912201672.12 | [array(['/en-us/storagezones-controller/media/sf-dc-trust-kerberos.png',
'Delegation properties for Kerberos'], dtype=object)
array(['/en-us/storagezones-controller/media/sf-dc-trust-ntlm.png',
'Delegation properties for NTLM'], dtype=object) ] | docs.citrix.com |
You can configure some of the ways vCenter Server interacts with the user directory server that is configured as identity source. For details about identity sources, see vSphere Security.
Prerequisites
Required privilege:
Procedure
- In the vSphere Web Client, navigate to the vCenter Server instance.
- Select the Manage tab.
- Under Settings, select General.
- Click Edit.
- Select User directory.
- In User directory timeout, type the timeout interval in seconds for connecting to the user directory server.
- In Query Limit, type.
- Select the Enabled check box next to Validation to have vCenter Server periodically check its known users and groups against the user directory server.
- In Validation Period, enter the number of minutes between instances of synchronization.
- Click OK. | https://docs.vmware.com/en/VMware-vSphere/5.5/com.vmware.vsphere.vcenterhost.doc/GUID-007C02A8-C853-4FBC-B0F0-933F19768DD4.html | 2019-03-18T20:06:50 | CC-MAIN-2019-13 | 1552912201672.12 | [] | docs.vmware.com |
PerlIS - Perl for ISAPI
- NAME
- DESCRIPTION
- AUTHOR AND COPYRIGHT
NAME
PerlIS - Perl for ISAPI
DESCRIPTION
About Perl for ISAPI.
Sources of other information
Information on Perl for ISAPI can also be found in the ActivePerl-Winfaq6 manpage and the ActivePerl-Winfaq7 manpage.
What is ISAPI? web servers support ActivePerl? for the names of a few. If your server isn't there, check its documentation.
What is Perl for ISAPI?.
Where can I get Perl for ISAPI?
Perl for ISAPI is distributed as a part of the ActivePerl distribution. You can optionally install it when installing ActivePerl..
Where's the source code for Perl for ISAPI?
The source for Perl for ISAPI is not distributed to the public.
AUTHOR AND COPYRIGHT. | http://docs.activestate.com/activeperl/5.24/perl/faq/Windows/ActivePerl-Winfaq2.html | 2019-03-18T19:46:23 | CC-MAIN-2019-13 | 1552912201672.12 | [] | docs.activestate.com |
Pages are similar to
This screen provides features such as editing, quick edits, view. It is also possible to do editing in bulk, filtering and search makes it further easy to easily search the pages matching certain criteria.
Table of List
[] : The checkbox is clicked to select the pages to perform bulk action.
Title: This is the title of the page displayed as a link. When title is clicked it takes you to the edit page screen. The text next to the title of page displays the nature of page i.e if it is a draft, pending or a password protected type.
"ID": This is not displayed as a column of the table. When mouse hovers over the Page Title, the Page ID is revealed as a part of the URL, displayed in the browser status bar. It is a unique number that is used by WordPress's database to identify the pages.
Author: This column displays the author of the page. It is displayed as a link. By clicking a particular author link, the list of all the pages by the authored user is displayed in the tabular form.
Comment Bubble: It is the column heading. Each page row has this section where number of comments for the pages are displayed. When blue comment bubble is clicked it displays comment screen so that comments can be moderated.
Date: This column displays the date "Last Published" for the published pages and "Last Modified" for the rest of
Sortable Columns
Columns with headings title, comment and date allows you to sort the table of pages in ascending or descending order. By hovering over the headings, up or down arrows appear. Accordingly click on the heading to sort the table page.
Page Navigation
Below the screen options, the number of items displayed per page is mentioned. If the pages increase by one page of Pages then two double-arrow boxes (to move to the first and the last page) and two single arrow boxes (to move one page forward or backward) are provided.
Search Box
In the right side, is a search page box where you can enter a word or series of word to display all the search results meeting your search word.
Filtering Box
At the top, below the add new button, there are links such as All, Mine, Published and Draft, that when clicked displays the pages of that particular type in the table.
Other Filter Option
Below the filtering options and to the right of Bulk actions, are one other filter options.
All Dates:
This is to filter the pages month wise. The drop down option allows you to choose the pages date wise. The default option is all pages which displays all of available pages.
Filter:
After selecting the option from drop-down, click filter button to apply the required changes.
Selections
Bulk Action option allows you to chose an option to apply on either
(1) Select one page at a time: This is possible by clicking on the check boxes next to the title of the page.
(2) Select all the pages in
(3) Reverse Action: The reverse is possible by checking the unchecked or unchecking the checked option.
Bulk Action
This action can be applied to one or more than one page simultaneously. Possible options include:
Edit
Bulk Edit allows the fields Author, Parent, Template, Comments Allowed, Statusand Pings Allowed, to be changed for all the selected Pages.
- Cancel - Click Cancel to cancel and abort the Bulk Edit of these Pages.
- Update - Click Update to save the Bulk Edits made to these Pages.
- Move to Trash: It will move all the selected pages to the trash screen.
- Clone: This is to create a copy of page that is saved in the draft. - Click Update to save the Edits made to this Page | https://docs.darlic.com/pages/list-of-all-pages/ | 2019-03-18T19:25:12 | CC-MAIN-2019-13 | 1552912201672.12 | [array(['https://docs.darlic.com/wp-content/uploads/sites/3/2019/02/managepages.png',
None], dtype=object) ] | docs.darlic.com |
Additional Resources
Below are a list of helpful resources about the Empty Set Dollar.
Offical Links
Articles
- Empty Set Dollar - An experiment in decentralised, composable, oracle-driven stablecoins by Lewis Freiberg
- The Empty Set Dollar: Premium Superfluid Collateral by Complement Capital
- Empty Set Dollar: A Game Theoretical Approach to Elastic Stablecoins by Delphi Digital (Paywalled)
Guides
- The elastic stablecoin. A guide to bonding to earn ESDs by 0xAns
- Bonding and Unbonding Instructional Video - The Bearded Prof
- Coupons Instructional Video - The Bearded Prof
Tools
- ESD tools - Simple statistics site for ESD
- ESD Coupons - A website that enables you to authorise bots to redeem coupons on your behalf for a tip
- ESD Money - An application that lets you trade coupons without redeeming them | https://docs.emptyset.finance/resources | 2021-04-10T19:27:00 | CC-MAIN-2021-17 | 1618038057476.6 | [] | docs.emptyset.finance |
This section describes how to enable Japanese language support in the Address Manager user interface. Once enabled, the Address Manager user interface will always be in Japanese, but you can revert it back to English at anytime from the login page.
Japanese].
- Click Update.
- Click Log Out. A language drop-down menu is now visible on the Address Manager login page.
- From the language drop-down menu, select Japanese[ja-JP]. The Address Manager login page immediately changes to Japanese.
- Log in to Address Manager. The Address Manager user interface is now in Japanese.Note: If you ever need to revert the Address Manager user interface back to English, log out of Address Manager and select English[en-US] from the language drop-down menu from the Address Manager login page. | https://docs.bluecatnetworks.com/r/Address-Manager-Administration-Guide/Setting-system-language/8.3.0 | 2021-04-10T19:30:19 | CC-MAIN-2021-17 | 1618038057476.6 | [] | docs.bluecatnetworks.com |
R/search_tweets.R
search_tweets.Rd
Returns Twitter statuses matching a user provided search query. ONLY RETURNS DATA FROM THE PAST 6-9 DAYS.
search_tweets2 Passes all arguments to search_tweets. Returns data from one OR MORE search queries.
search_tweets( q, n = 100, type = c("mixed", "recent", "popular"), include_rts = TRUE, geocode = NULL, since_id = NULL, max_id = NULL, parse = TRUE, token = NULL, retryonratelimit = NULL, verbose = TRUE, ... ) search_tweets2(...)
List object with tweets and users each returned as a data frame.
A tbl data frame with additional "query" column..
Other tweets:
get_favorites(),
get_mentions(),
get_timeline(),
lists_statuses(),
lookup_tweets()
if (FALSE) { tweets <- search_tweets("weather") tweets # data about the users who made those tweets users_data(tweets) # Retrieve all the tweets made since the previous request # (there might not be any if people aren't tweeting about the weather) newer <- search_tweets("weather", since_id = tweets) # Retrieve tweets made before the previous request older <- search_tweets("weather", max_id = tweets) # Restrict to English only, and ignore retweets tweets2 <- search_tweets("weather", lang = "en", include_rts = FALSE) } if (FALSE) { ## search using multilple queries st2 <- search_tweets2( c("\"data science\"", "rstats OR python"), n = 500 ) ## preview tweets data st2 ## preview users data users_data(st2) ## check breakdown of results by search query table(st2$query) } | https://docs.ropensci.org/rtweet/reference/search_tweets.html | 2021-04-10T18:41:43 | CC-MAIN-2021-17 | 1618038057476.6 | [] | docs.ropensci.org |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.