Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length

 
Advanced search

2506 Posts in 649 Topics- by 1315 Members - Latest Member: jfields

eTicket CommunityDevelopmentModule Development (Moderators: jason, Hummdis)Topic: Extra functionality - Client database
Pages: [1]   Go Down
Print
Author Topic: Extra functionality - Client database  (Read 3765 times)
0 Members and 1 Guest are viewing this topic.
stephen
New Member
*

Karma: +0/-0
Offline Offline

Posts: 2


« on: November 10, 2008, 11:57:05 PM »

Hi,
I'm not sure if this is the right section to post this, but here goes anyway  Grin

eTicket is awesome and is 90% what we want for our business. The other 10% is what we would like if it could be included somehow with a module/plugin:

*  A table in the database that stores info of all our existing clients.
*  The ability to assign a ticket to an existing client, preferably after the new ticket has been created. Sometimes another member of the family of that client will phone in, so we would like to have the functionality of capturing the name of the person phoning and have it assign under the client info.
*  The ability to see all the tickets ever created for a client when viewing a specific client's info.
*  A print button that will print a ticket in printer friendly format. (this one isn't that important, just a nice to have)

I will try and attempt to implement these features, although I know very little of PHP and it will most likely take me a few months to do. So it would be nice if there is someone uber that make this possible  Wink
Logged
Hummdis
Moderator
Super Member
*****

Karma: +13/-0
Offline Offline

Posts: 558



WWW
« Reply #1 on: November 11, 2008, 06:30:15 AM »

Quote
*  A print button that will print a ticket in printer friendly format. (this one isn't that important, just a nice to have)

This one is actually quite easy for you to implement without the need for a print button.  Using CSS, this can be done by creating a CSS file for print only useage (print.css is a good name).

You would then declare the changes that are to be made in print.css (if you choose to call the file that).  Once you've changed the colors and settings, then just specify the following in the <HEAD> and </HEAD> tags of the themes/[THEME_NAME]/theme.php file:

Code:
<LINK HREF="print.css" REL="stylesheet" TYPE="text/css" media="print">

Wherever you want something to be removed, just declare a span or div with the class "noPrint" and put the following in the print.css file along with your other print specified colors:

Code:
.noPrint {
display: none ! important;
}

The "!important" forces the display:none value to ensure that it is not displayed.

With this format, no matter what browser you're using, just print the page and the unwanted stuff will automatically be removed.  No "Printer Friendly" button needed! Wink
« Last Edit: November 14, 2008, 05:15:49 AM by Hummdis » Logged

Don't PM me directly for help.  Post to the forums, that's what they are for after all.  PM's to me that request help will be ignored.

Hummdis Communications - Freelance Website Design & IT Consulting
stephen
New Member
*

Karma: +0/-0
Offline Offline

Posts: 2


« Reply #2 on: November 12, 2008, 01:34:01 AM »

Thanx Hummdis, I'll try out what you suggested.
Logged
Hummdis
Moderator
Super Member
*****

Karma: +13/-0
Offline Offline

Posts: 558



WWW
« Reply #3 on: November 12, 2008, 09:07:29 AM »

Let me know if you have trouble with that and I'll see what I can do to clarify my steps if possible.

Here is the W3C text of the "! important" delcaration:

http://www.w3.org/TR/REC-CSS1/#important
« Last Edit: November 14, 2008, 05:14:12 AM by Hummdis » Logged

Don't PM me directly for help.  Post to the forums, that's what they are for after all.  PM's to me that request help will be ignored.

Hummdis Communications - Freelance Website Design & IT Consulting
eTicket Community
   

 Logged
Pages: [1]   Go Up
Print
eTicket CommunityDevelopmentModule Development (Moderators: jason, Hummdis)Topic: Extra functionality - Client database
Jump to: