[Bps-public-commit] RT-Extension-FeaturedTickets branch, master, updated. 4c7d2eb31fcf3e9ac72b67fbfa3e2a44398002d2

Jim Brandt jbrandt at bestpractical.com
Fri Jun 1 11:19:45 EDT 2018


The branch, master has been updated
       via  4c7d2eb31fcf3e9ac72b67fbfa3e2a44398002d2 (commit)
       via  a13d0623f0af211b5a20de9003487ac75bf157fd (commit)
       via  528ffb70dfcf8b459270957104f0d2ce2968d8a3 (commit)
       via  9fd28871ee85662e567a39b79ad809c2a6dbb414 (commit)
      from  3488c9a7eb747df38c5b640ab40fc831ba064330 (commit)

Summary of changes:
 Changes                             |  5 +++-
 MANIFEST                            | 25 +++++++++++++++++
 META.yml                            |  2 +-
 README                              | 54 +++++++++++++++++++++----------------
 html/NoAuth/Featured/index.html     | 26 +++++++++---------
 lib/RT/Extension/FeaturedTickets.pm | 51 ++++++++++++++++++++++-------------
 static/css/featured-tickets.css     | 19 ++++---------
 7 files changed, 111 insertions(+), 71 deletions(-)
 create mode 100644 MANIFEST

- Log -----------------------------------------------------------------
commit 9fd28871ee85662e567a39b79ad809c2a6dbb414
Author: Jim Brandt <jbrandt at bestpractical.com>
Date:   Fri May 25 16:14:43 2018 -0400

    Update docs

diff --git a/README b/README
index 3f4f0de..4560793 100644
--- a/README
+++ b/README
@@ -16,29 +16,6 @@ INSTALLATION
 
             Plugin('RT::Extension::FeaturedTickets');
 
-        or add RT::Extension::FeaturedTickets to your existing @Plugins
-        line.
-
-        $FeaturedTicketsQueue specifies which queue the featured tickets
-        will be loaded from when the initial data is loaded the
-        'FeaturedTickets' queue is created by default. Renaming this queue
-        is the simplest way to use another queue name but keep the relevant
-        applied custom fields.
-
-            Set($FeaturedTicketsQueue, 'FeaturedTickets');
-
-        $FeaturedTicketStatuses is an array ref, where the ticket statuses
-        that will be accepted from the $FeaturedTicketsQueue are specified.
-        Only tickets with one of the statuses in the array will be listed on
-        the featured page.
-
-            Set($FeaturedTicketStatuses, ['open', ...]);
-
-        Set which queue new sponsor tickets will be placed into with the
-        $SponsorsQueue variable.
-
-            Set($SponsorsQueue, 'Sponsors');
-
     Clear your mason cache
             rm -rf /opt/rt4/var/mason_data/obj
 
@@ -50,6 +27,37 @@ DESCRIPTION
     linked ticket in the same queue. The tickets featured can be selected
     from a queue and limited to their statuses.
 
+CONFIGURATION
+    This extension requires settings for a few configuration items to work
+    properly.
+
+  $FeaturedTicketsQueue
+    $FeaturedTicketsQueue specifies which queue the featured tickets will be
+    loaded from. During installation, a queue called 'FeaturedTickets' is
+    created by default. Renaming this queue is the simplest way to use
+    another queue name but keep the relevant applied custom fields.
+
+        Set($FeaturedTicketsQueue, 'FeaturedTickets');
+
+  $FeaturedTicketStatuses
+    $FeaturedTicketStatuses sets the list of tickets statuses of tickets
+    that should be displayed on the public page. Only tickets with one of
+    the statuses in the array will be shown.
+
+        Set($FeaturedTicketStatuses, ['open', ...]);
+
+  $SponsorsQueue
+    When a sponsor signs up for a ticket, a new ticket is created in this
+    queue with the new sponsor as the Requestor.
+
+        Set($SponsorsQueue, 'Sponsors');
+
+  Custom Fields
+    There are several custom fields that are used to create the content for
+    each item on the public page. These are created when you run make
+    initdb. Feature Type also needs to be set to see tickets on the public
+    page and it defaults to 'RT'.
+
 AUTHOR
     Best Practical Solutions, LLC <modules at bestpractical.com>
 
diff --git a/lib/RT/Extension/FeaturedTickets.pm b/lib/RT/Extension/FeaturedTickets.pm
index 4363788..748e19e 100644
--- a/lib/RT/Extension/FeaturedTickets.pm
+++ b/lib/RT/Extension/FeaturedTickets.pm
@@ -30,30 +30,12 @@ Works with RT 4.4
 
 May need root permissions
 
-
 =item Edit your F</opt/rt4/etc/RT_SiteConfig.pm>
 
 Activate the plugin by adding the below:
 
     Plugin('RT::Extension::FeaturedTickets');
 
-or add C<RT::Extension::FeaturedTickets> to your existing C<@Plugins> line.
-
-$FeaturedTicketsQueue specifies which queue the featured tickets will be loaded from when
-the initial data is loaded the 'FeaturedTickets' queue is created by default. Renaming this queue is the simplest
-way to use another queue name but keep the relevant applied custom fields.
-
-    Set($FeaturedTicketsQueue, 'FeaturedTickets');
-
-$FeaturedTicketStatuses is an array ref, where the ticket statuses that will be accepted from the $FeaturedTicketsQueue
-are specified. Only tickets with one of the statuses in the array will be listed on the featured page.
-
-    Set($FeaturedTicketStatuses, ['open', ...]);
-
-Set which queue new sponsor tickets will be placed into with the $SponsorsQueue variable.
-
-    Set($SponsorsQueue, 'Sponsors');
-
 =item Clear your mason cache
 
     rm -rf /opt/rt4/var/mason_data/obj
@@ -68,7 +50,38 @@ Create a webpage that anyone can view (NoAuth), displaying details on featured t
 can decide to sign up as a requestor on a linked ticket in the same queue. The tickets featured
 can be selected from a queue and limited to their statuses.
 
+=head1 CONFIGURATION
+
+This extension requires settings for a few configuration items to work properly.
+
+=head2 C<$FeaturedTicketsQueue>
+
+C<$FeaturedTicketsQueue> specifies which queue the featured tickets will be loaded from.
+During installation, a queue called 'FeaturedTickets' is created by default. Renaming
+this queue is the simplest way to use another queue name but keep the relevant applied
+custom fields.
+
+    Set($FeaturedTicketsQueue, 'FeaturedTickets');
+
+=head2 C<$FeaturedTicketStatuses>
+
+C<$FeaturedTicketStatuses> sets the list of tickets statuses of tickets that should be displayed on
+the public page. Only tickets with one of the statuses in the array will be shown.
+
+    Set($FeaturedTicketStatuses, ['open', ...]);
+
+=head2 C<$SponsorsQueue>
+
+When a sponsor signs up for a ticket, a new ticket is created in this queue with the new sponsor
+as the Requestor.
+
+    Set($SponsorsQueue, 'Sponsors');
+
+=head2 Custom Fields
 
+There are several custom fields that are used to create the content for each item on the public
+page. These are created when you run C<make initdb>. Feature Type also needs to be set to see tickets
+on the public page and it defaults to 'RT'.
 
 =head1 AUTHOR
 

commit 528ffb70dfcf8b459270957104f0d2ce2968d8a3
Author: Jim Brandt <jbrandt at bestpractical.com>
Date:   Fri Jun 1 11:05:27 2018 -0400

    Allow one more line in the feature box

diff --git a/static/css/featured-tickets.css b/static/css/featured-tickets.css
index 61a06ee..735a1d8 100644
--- a/static/css/featured-tickets.css
+++ b/static/css/featured-tickets.css
@@ -124,7 +124,7 @@ body {
     position: relative;
     background-color: lightgray;
     overflow: hidden;
-    height: 13em;
+    height: 15em;
 }
 
 /*

commit a13d0623f0af211b5a20de9003487ac75bf157fd
Author: Jim Brandt <jbrandt at bestpractical.com>
Date:   Fri Jun 1 11:18:01 2018 -0400

    Restrict styles to just featured tickets page

diff --git a/html/NoAuth/Featured/index.html b/html/NoAuth/Featured/index.html
index 57cdf18..5d89a1a 100644
--- a/html/NoAuth/Featured/index.html
+++ b/html/NoAuth/Featured/index.html
@@ -47,14 +47,14 @@
 <div class="featured-tickets-modal" id="featured-tickets-modal-modal" align='center'>
     <div class="featured-tickets-modal-content">
         <div class="featured-tickets-modal-submitted" id="featured-tickets-modal-submitted">
-            <h2>Thanks for your pledge of support!</h2>
-            <h2>You'll receive an email soon with more details.</h2>
+            <h2 class="featured-tickets-heading">Thanks for your pledge of support!</h2>
+            <h2 class="featured-tickets-heading">You'll receive an email soon with more details.</h2>
             <button onclick="FeaturedTicketsHideModal();" class="featured-tickets-button-choose pure-button">Close</button>
         </div>
         <div id="featured-tickets-modal-unsubmitted">
             <form class="pure-form pure-form-aligned" onsubmit="event.preventDefault(); NewSponsor();">
                 <span class="featured-tickets-modal-close" id="featured-tickets-modal-close"></span>
-                <h2><div id="featured-tickets-subject"></div></h2>
+                <h2 class="featured-tickets-heading"><div id="featured-tickets-subject"></div></h2>
                 <h4><div id="featured-tickets-description"></div></h4>
                 <h4><div id="featured-tickets-details"></div></h4>
                 <h4><div id="featured-tickets-goal"></div></h4>
@@ -85,7 +85,7 @@
     <div class="pure-u-1 pure-u-md-1-3">
         <div class="pricing-table pricing-table-free">
             <div class="pricing-table-header">
-                <h2><% $ticket->Subject ? $ticket->Subject : 'Ticket: ' . $ticket->Id %></h2>
+                <h2 class="featured-tickets-heading"><% $ticket->Subject ? $ticket->Subject : 'Ticket: ' . $ticket->Id %></h2>
                 </div>
 %   if ( $ticket->FirstCustomFieldValue('Funded') && $ticket->FirstCustomFieldValue('Funded') eq 'Funded' ) {
     <div class='ribbon-wrapper'>
@@ -98,7 +98,7 @@
         <div class='ribbon'>Partially Funded!</div>
     </div>
 %   }
-    <p>
+    <p class="featured-tickets-paragraph">
 % if ( length($ticket->FirstCustomFieldValue('Description')) > 140 ) {
     <% substr $ticket->FirstCustomFieldValue('Description'), 0, 140 %> ...
 % } else {
@@ -116,8 +116,8 @@
     <div class="information pure-g">
         <div class="pure-u-1 pure-u-md-1-2">
             <div class="l-box">
-                <h3 class="information-head">What is this page?</h3>
-                <p>
+                <h3 class="information-head featured-tickets-heading">What is this page?</h3>
+                <p class="featured-tickets-paragraph">
                     As an open source product, the majority of the new features we add to Request Tracker are sponsored by users just like you. When we talk to organizations who use RT, we often share our product roadmap to provide options for sponsorship in the core product. We wanted to find a way to share these product ideas with a wider audience, so we created this page to make it easier for supporters to see new features we'd like to build into RT and RTIR.
                 </p>
             </div>
@@ -125,8 +125,8 @@
 
         <div class="pure-u-1 pure-u-md-1-2">
             <div class="l-box">
-                <h3 class="information-head">When can I have it?</h3>
-                <p>
+                <h3 class="information-head featured-tickets-heading">When can I have it?</h3>
+                <p class="featured-tickets-paragraph">
                      Smaller features and bug fixes are included in the next point release in the current stable release. For larger features, we typically target the next minor series, and we can also provide you with an extension that is compatible with the current stable release. (Versions consist of a major series, minor series and point release. RT 4.4.2 is major series 4, minor series 4, and point release 2.) 
                 </p>
             </div>
@@ -134,8 +134,8 @@
 
         <div class="pure-u-1 pure-u-md-1-2">
             <div class="l-box">
-                <h3 class="information-head">What happens after I sponsor?</h3>
-                <p>
+                <h3 class="information-head featured-tickets-heading">What happens after I sponsor?</h3>
+                <p class="featured-tickets-paragraph">
                     Once you sign up to sponsor a feature, we'll be in touch to discuss our development process, scheduling, payment, and answer any other questions you have. 
                 </p>
             </div>
@@ -143,8 +143,8 @@
 
         <div class="pure-u-1 pure-u-md-1-2">
             <div class="l-box">
-                <h3 class="information-head">My feature isn't here</h3>
-                <p>
+                <h3 class="information-head featured-tickets-heading">My feature isn't here</h3>
+                <p class="featured-tickets-paragraph">
                     We offer a wide variety of <a href="https://bestpractical.com/services">services</a> for RT, including <a href="https://bestpractical.com/support">product support</a>, <a href="https://bestpractical.com/training">training</a>, and <a href="https://bestpractical.com/services/">development</a>. If you'd like to sponsor the development of a feature not included here, or are seeking joint sponsorship of a feature for RT, please <a href="mailto:contact at bestpractical.com">contact us</a>.
                 </p>
             </div>
diff --git a/static/css/featured-tickets.css b/static/css/featured-tickets.css
index 735a1d8..4a67495 100644
--- a/static/css/featured-tickets.css
+++ b/static/css/featured-tickets.css
@@ -2,15 +2,10 @@
  * -- BASE STYLES --
  * Most of these are inherited from Base, but I want to change a few.
  */
- .featured-tickets-body {
+.featured-tickets-body {
 /*    color: black;  */
     background: #FAFAFA;
-}
-
-.featured-tickets-h2, featured-tickets-h3 {
-    letter-spacing: 0.25em;
-    text-transform: uppercase;
-    font-weight: 600;
+    color: #526066;
 }
 
 .featured-tickets-p {
@@ -49,20 +44,16 @@
     padding: .5em .7em;
 }
 
-h2, h3 {
+h2.featured-tickets-heading, h3.featured-tickets-heading {
     letter-spacing: 0.25em;
     text-transform: uppercase;
     font-weight: 600;
 }
 
-p {
+p.featured-tickets-paragraph {
     line-height: 1.6em;
 }
 
-body {
-    color: #526066;
-}
-
 .information-head {
     color: black;
     font-weight: 500;

commit 4c7d2eb31fcf3e9ac72b67fbfa3e2a44398002d2
Author: Jim Brandt <jbrandt at bestpractical.com>
Date:   Fri Jun 1 11:19:36 2018 -0400

    Prep for 0.02 release

diff --git a/Changes b/Changes
index d346630..9dc38a1 100644
--- a/Changes
+++ b/Changes
@@ -1,4 +1,7 @@
 Revision history for RT-Extension-FeaturedTickets
 
-0.01 [Release Date]
+0.02 2018-06-01
+ - Style updates
+
+0.01 2018-05-25
  - Initial version
diff --git a/MANIFEST b/MANIFEST
new file mode 100644
index 0000000..ce08cc2
--- /dev/null
+++ b/MANIFEST
@@ -0,0 +1,25 @@
+Changes
+etc/initialdata
+html/NoAuth/Featured/index.html
+html/NoAuth/Helpers/NewSponsor
+inc/Module/Install.pm
+inc/Module/Install/Base.pm
+inc/Module/Install/Can.pm
+inc/Module/Install/Fetch.pm
+inc/Module/Install/Include.pm
+inc/Module/Install/Makefile.pm
+inc/Module/Install/Metadata.pm
+inc/Module/Install/ReadmeFromPod.pm
+inc/Module/Install/RTx.pm
+inc/Module/Install/RTx/Runtime.pm
+inc/Module/Install/Win32.pm
+inc/Module/Install/WriteAll.pm
+inc/YAML/Tiny.pm
+lib/RT/Extension/FeaturedTickets.pm
+Makefile.PL
+MANIFEST			This list of files
+META.yml
+README
+static/css/featured-tickets.css
+static/images/rawpixel-com-250087-unsplash.jpg
+static/js/featured-tickets.js
diff --git a/META.yml b/META.yml
index 39b6650..33859fa 100644
--- a/META.yml
+++ b/META.yml
@@ -25,7 +25,7 @@ requires:
 resources:
   license: http://opensource.org/licenses/gpl-license.php
   repository: https://github.com/bestpractical/rt-extension-featuredtickets
-version: '0.01'
+version: '0.02'
 x_module_install_rtx_version: '0.40'
 x_requires_rt: 4.4.0
 x_rt_too_new: 4.6.0
diff --git a/lib/RT/Extension/FeaturedTickets.pm b/lib/RT/Extension/FeaturedTickets.pm
index 748e19e..17725c7 100644
--- a/lib/RT/Extension/FeaturedTickets.pm
+++ b/lib/RT/Extension/FeaturedTickets.pm
@@ -2,7 +2,7 @@ use strict;
 use warnings;
 package RT::Extension::FeaturedTickets;
 
-our $VERSION = '0.01';
+our $VERSION = '0.02';
 
 RT->AddStyleSheets("featured-tickets.css");
 RT->AddJavaScript("featured-tickets.js");

-----------------------------------------------------------------------


More information about the Bps-public-commit mailing list