blackcell

June 12, 2008

Released some updates to the system. Still working on some things.

June 11, 2008

Yep, thanks.

June 11, 2008

Thanks.

June 11, 2008

If I build something with another language how do I implement it into a web page? Do you have to do the interfacing method with the language you built it with? For instance, JAVA applications on websites. Are they built with the functions to tie into a web page with the Java language?

June 11, 2008

Is it possible to create buttons as rich as the ones in this example:

http://www.oscaralexander.com/tutorials/how-to-make-sexy-buttons-with-css.html

and retain the submit functionality? Anybody can draw a picture of a neat button with a graphic and make it a hyperlink but I have little luck on finding one for input purposes without using a non-scalable background image?

June 11, 2008

How would you plug something written into a different language into a php script? For instance a chat program written in C? Sorry if this is the wrong forum.

June 11, 2008

I don't particularly like the way it pushed your chat send down as your chat box fills up.

June 11, 2008

I don't know I guess I have it completely keys to what we need in our IT department.

Tickets - Basic issues submitted from the end user or even reminders for yourself. Everything dealing with tickets editing/navigation is contained within the Tickets Tab. Outside links consist of mainly linking to the project it is attached to.

Projects - A larger scale ticket that can be used to group tickets. Flexibility allows for projects to be used as categories of tickets also. Tickets and Project use flexibility allows for something like creating a "bucket" or free PCs to deploy within the company where each ticket is a PC and has its specs listed. Activity can be used to track where the pc is deployed to and who to. The project will be the category.

Solutions - Used to document troubleshooting steps for moderate frequency issues. These can be categorized into existing categories or create a new on the fly.

June 11, 2008

You guys make me want to give up on college quit my job and go back to working in the oilfield or one of my previous young person hard labor jobs I had.

You guys give the problems with very few problems having possible corrective paths. I guess I should have started learning php and programming at the age of 13 to amount to something.

June 11, 2008

1) Code does not validate

This should go here: http://www.phpfreaks.com/forums/index.php/topic,201145.0.html

2) you fail to use css extensively, you still call "bgcolor, align, height" as inline css declarations

This should go here: http://www.phpfreaks.com/forums/index.php/topic,201145.0.html

3) The site is too bland, absolutely no color

What colors do you suggest?

4) What is up with the "firefox icon" - I use FF, but users will hate you for telling them to switch their browser (As the web designer, it is your duty and responsibility to create cross-browser compatible browsers....)

Have you read anything above the past two posts?

5) Take out the system overview - do users really need to know the most recently registered user?

The forums you use have these types of things. Other ticket systems have these types of things... I will eventually find something better to put in the space.

6) Use some icons - http://tango.freedesktop.org/Tango_Icon_Library

Thank you for the site I will look into it. Why not be original and make your own?

7) Logo is distorted

Read a few posts up.

Cool You use tables for you code (bad idea)

Cool to use tables? I have heard nothing bad but quite frankly out of 18+ simple programs and reports I have made there have been no complaints. Can I get a low down on the bad things called (tables)

9) There are way too many tabs; maybe you can cut down on the number of tabs you have? Combine some together?

To me they all seem independent and serve their purpose? I bet there would be no complaints if I took them out of tabs and strung them across the top in textual hyperlinks looking like this:

[Home][Help][search][Profile][My Messages][Calendar][Members][Rules][staff List][Logout]

June 11, 2008

Ok, the design sucks. I thought it was pretty nifty to get around in and my boss pretty much coached the developement through feedback on what he wanted to see. Where are the rough spots? I have an alternate version that 100%s the lower frame to expand the working area to the width of the window with a constant javascript update so that you will only get one scroll bar. I am not as good as I want to be with graphical interfaces and I have been forced to keep gui's very simple and dumb for the sake of speedy production. Therefore I lack in the knowledge of catchy graphical concepts. You guys are giving me "I don't like its but it has potential" and "It is lacking functionality" but make it a challenge instead of a pitfall and tell me what it needs.

Thanks again everybody for their input.

June 10, 2008

I haven't done anything. What gradient, the grey to silver headers?

June 10, 2008

Let me work it.

June 10, 2008

Space is something that is hard to manage when you are building this for people likely to use 1024x768. Do you have any suggestions to get around that? I have been searching for awhile.

June 10, 2008

Would you happen to know why so that I may fix it?

June 10, 2008

I understand your looking at this from a standpoint of me trying to sell it. If anything I would release it as open source for improvement by people like yourself.

IE crusaders can eat dirt. I would prefer the mindless drones not mess with the code and put their touch on it. I would like to see it on Opera just to see it. I might do this though. Reality is reality but there is discrimination isn't an issue when money is not a factor.

I have a way of distributing the css source to each page from a file so that I may see it when viewing the html source from the page.

I have looked at other open source ticket systems. They all had interfaces that were overly complicated for what it needed to do. Submit a ticket, view a ticket, and manage a ticket. Why have 500(exaggeration) menus with 3000(another exaggeration) sub-menus within those 500 to work these simple tasks? This is tailored for a company with constant flow of feedback, suggestions, and bug reporting. All the users seem to greatly appreciate it compared to the last open source ticket system we had.

May I ask that you provide some of the lacking functionality you stated you weren't going to "list out". I would love to improve the system further.

Thank you for your feedback.

June 10, 2008

Overall it's not a very friendly interface nor is it appealing to look at. To be commercially acceptable, you should probably consider hiring a designer to do some of the interface for you if you can't produce something better than your current attempt (no offense).

Rotflmao. I respect your honesty. I guess I am not a natural that can produce a perfect program first attempt. I know those people are everywhere.

1) Graphics are all very poorly done.

What graphics? The banner will be customizable. The little icons were quick and I would be open to suggestions.

2) You need more color... right now it's a lot of black and gray, very boring.

Where could I use color influence? The tabs?

3) It doesn't play well with large resolutions. It's all smashed to the left of the screen.

Everything is meant to be smashed to the left to deal with varying resolutions. Centered does not flow very well with the top tabs.

4) Submitting a ticket should take you to the status area of your tickets, not just show the form again.

When your in admin mode or submitting a ticket as a user? I believe you have a good point either way.

5) Should be cross-browser compatible. I lose respect for developers when they put "works best on X browser" on their sites.

Screw IE. The people that believe it is the standard to use it can mod the system to work for it. If you viewed this with IE that is half the problem.

6) Your CSS should be linked, not in the page itself.

My css is linked by file.

7) You are using tables for general layout... this is not the best way to go.

What are your suggestions? I would love to get away from tables.

8 ) Your fonts are not consistent: example would be the column contents on the projects screen. They're varying sizes and it does not look uniform.

Probably because your viewing it with IE.

Did you have any positive feedback?

June 10, 2008

Oh, the GAY part of it. First, considering that part of the domain name is my actual name I don't see it on the level you see it. Second, the domain name is for my testing purposes and I guess I should have posted a note saying:

Please critique my web SITE and not my web DOMAIN.

because I thought that might have been part of the forum.

Do you have any other feedback besides a post not worth the disk space it is stored on?

Didn't think so, you probably didn't even look at the site.

June 10, 2008

GAYloraid?

- bad domain.

What are you talking about?

June 9, 2008

What were you doing to get these:

Full Path Disclosure:

When adding a user.

Quote

Warning: fsockopen() [function.fsockopen]: php_network_getaddresses: getaddrinfo failed: Name or service not known in /home/bgaylor/public_html/Tickets/admin/mailer/class.smtp.php on line 105

Warning: fsockopen() [function.fsockopen]: unable to connect to :25 in /home/bgaylor/public_html/Tickets/admin/mailer/class.smtp.php on line 105

Message was not sent

Mailer Error: Language string failed to load: connect_host

Full Path Disclosure:

http://www.gayloraid.com/Tickets/admin/mailer/newTicket.php

Quote

Fatal error: Call to undefined function: mailer_host() in /home/bgaylor/public_html/Tickets/admin/mailer/newTicket.php on line 11

Full Path Disclosure:

http://www.gayloraid.com/Tickets/admin/mailer/sendMail.php

Quote

Fatal error: Call to undefined function: mailer_host() in /home/bgaylor/public_html/Tickets/admin/mailer/sendMail.php on line 11

June 9, 2008

Please don't break it, it is still in the debugging phase. FYI the password changing is disabled. Here are links for multiple users because I think it should boot someone off if it 2 users log in as the same name:

User1 - www.gayloraid.com/Tickets/admin/index.php?user=tester2@tickets.com&pass=123456789

User2 - www.gayloraid.com/Tickets/admin/index.php?user=tester3@tickets.com&pass=123456789

User3 - www.gayloraid.com/Tickets/admin/index.php?user=tester4@tickets.com&pass=123456789

User4 - www.gayloraid.com/Tickets/admin/index.php?user=tester5@tickets.com&pass=123456789

User5 - www.gayloraid.com/Tickets/admin/index.php?user=tester6@tickets.com&pass=123456789

User6 - www.gayloraid.com/Tickets/admin/index.php?user=tester7@tickets.com&pass=123456789

User7 - www.gayloraid.com/Tickets/admin/index.php?user=tester8@tickets.com&pass=123456789

User8 - www.gayloraid.com/Tickets/admin/index.php?user=tester9@tickets.com&pass=123456789

EDIT:

Feel free to enter data, edit data, close tickets, assign tickets, blah blah blah.

Also, the typical users' interface is here: www.gayloraid.com/Tickets/

June 9, 2008

1) Cross Site Scripting(XSS):

If Cross Site Scripting is the ability to add html, I want to eventually add a text formatting toolbar to it. What are the dangers right now?

What is the best way to combat XSS?

Edit:

Removed Question.

3) Where the fsockopen() come from?

4) How did you manage to get this:

SQL Error:

http://www.gayloraid.com/Tickets/admin/panel_tickets_show.php?WHERE=a

You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1

LOL @ marquees by the way.

June 9, 2008

One more thing,

I built this using Firefox and have no desire to make this 100% compatible with IE. I consider IE a plague that preys on the ignorant, therefore I will leave it to one of those to make it compatible.

June 9, 2008

Please don't break it. I would like to know about bugs if you find them. FYI the password changing is disabled. Here are links for multiple users because I think it should boot someone off if it 2 users log in as the same name: