Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

In this Discussion

osTicket v1.10 (stable) and Maintenance Release v1.9.15 are now available! Go get it now

Dead or alive? - Continued...

«1

Comments

  • :)

    Oh, SCP look and performance it just excellent. Great Job, greatly appreciated...:)

    One thing that i want to know more is, after the final release of osticket 1.7, can i use my existing database with the new version because i have more than 300 closed tickets in the database and i dont want to loose it, want to keep records. So, will i able to use my existing database? :)
  • @Peter: Could you offer a zipped package of the files for download from here from time to time? Guess there are a lot of devs out there who do not use Git.


    Thanks
    T.
  • Any changelog or planned features?
  • @shitansh - Thanks for the kind words (It's needed around here.. :D) Yes, you'll be able to seamlessly upgrade from your existing installation.

    @thofei - You can download a zipped package directly from Github. I'll also encourage you to give git a try.

    @chiefer - We're in the process of putting together a list of changes. Changelog won't be ready until development is frozen in preparation for public release.

    Thanks,
  • Just installed 1.7.

    First looks : colors are much easier on the eyes,
    love the hover functions over the tickets

    I like the fact that you moved the users time zone setting into the admin side, but why did you leave the DST radio button in the user preferences? Just curious.

    Thanks for all the hard work.

    Keith
  • time estimate

    expectation time for public version?
  • @ksalisbury - Thanks for the feedback. Admin can set global (system wide) time zone, but users can still set their own local timezone. We didn't move the user time zone setting!

    @ionut.cazacu - I won't make promises on ETA anymore! That said, it won't be another 2 years. We'll make announcement once we feel it's ready for public release.
  • Keep getting an error on install:

    Fatal error: Cannot use object of type Installer as array in C:\inetpub\wwwroot\Beta\setup\install.php on line 32

    Web Server:
    PHP 5.3.3 - FastCGI
    MySql 5.1.50
    IIS 7
  • peter;26405 said:
    @ksalisbury - Thanks for the feedback. Admin can set global (system wide) time zone, but users can still set their own local timezone. We didn't move the user time zone setting!
    Maybe I phrased it incorrectly.
    The Global setting I knew about. but that wouldn't apply to the staff members. Those needed to be set individually. (At least I had to do it that way). Bear in mind I've been at this for all of a month now:o , so I may have missed something.

    [CENTER]In 1.6[/CENTER]
    admin panel/staff/staff members and choose a member. There is no way(see disclaimer above if I am wrong about this) for the admin to change the staff members time zone. I had to open the user profile and go to their 'My Preferences'.

    [CENTER]in 1.7[/CENTER]
    When I got to Admin panel /staff/ staff members/ and choose a member. I have the option to change their timezone but not whether or not they observer DST.

    Even if it was a lucky mistake, Thanks :)
  • well.... it looks very nice, great work Peter!

    suggestion: maybe you can add more padding space on settings rows...

    :mad: and very important question: why you don't use id's in DB for status ticket ?

    i see for priority you used id's... maybe most of us want to change language, or others want to use some icons for status ticket... please let me know about this.
  • @zalez - We'll look into the issue - for now try disabling global variables.

    @ksalisbury - We added the ability to set the timezone on purpose - but forgot DST (It's on to do list now) :)

    @abis - Language of enum fields shouldn't matter - you can map it to the actual language independently via a translation - giving you ability to support multiple translation hash tables. I'll have more to say about multilingual support AFTER v1.7 release. :cool:
  • ?

    Sometimes when i post a reply, i made typing error. And, i cant correct it. Is it possible to add an option to edit a posted reply through SCP or ACP?
    Please reply.
    Thanks.
  • Error while first start

    Hi,

    after installation, when I first visit either the front page or the staff-login php is writing the following warnings:

    Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Paris' for '1.0/no DST' instead in C:\xampp\htdocs\osticket17\include\class.config.php on line 85

    Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at C:\xampp\htdocs\osticket17\include\class.config.php:85) in C:\xampp\htdocs\osticket17\include\class.ostsession.php on line 39

    Warning: session_regenerate_id() [function.session-regenerate-id]: Cannot regenerate session id - headers already sent in C:\xampp\htdocs\osticket17\include\class.staff.php on line 518



    Any Ideas?
  • adding fields / asset

    Hello

    Could you create a feature to allow us to add fields to the create ticket page?

    Also,

    Adding a field for Asset ID would be great - which maybe links to an asset table which could hold information on the item and show previous tickets regarding it?

    Thanks
  • Hi, I currently use OST 1.6... Wanted to know for new version if there way to allow for deleting and/or archiving system logs? IMO, the logs grow over time and having a way to manage this would be ideal.

    Have not seen any listing of expected features for new release but I'll list some desired features IMO would be nice:)

    1) Allow admin to control keeping certain client info private when assigned to partners. Ex: Name, Email Address, etc

    2) A billing functionality would be nice built right into OST.

    3) Creating SLA's for certain clients or on a per ticket basis.

    4) Ability to add additional fields for clients and partners.

    Glad to see some development activity going on - keep up the good work!

    - Joe
  • error on instal

    from the comments I see here, it looks to be good step ahead.

    however i am getting an error on install:

    Fatal error:
    Cannot use object of type Installer as array in ... setup\install.php on line 32

    after i tried again the same message
    Fatal error:
    Cannot use object of type Installer as array in /data/r/u/mydomain.com/sub/helpdesk/test/setup/install.php on line 81


    Web Server:
    PHP v5.3.8 - (5.3.8)
    MySQL v5.1 (module loaded)

    tried on 2 webservers.
    thank you for advice
  • vladivlad;26465 said:
    from the comments I see here, it looks to be good step ahead.

    however i am getting an error on install:

    Fatal error:
    Cannot use object of type Installer as array in ... setup\install.php on line 32

    after i tried again the same message
    Fatal error:
    Cannot use object of type Installer as array in /data/r/u/mydomain.com/sub/helpdesk/test/setup/install.php on line 81


    Web Server:
    PHP v5.3.8 - (5.3.8)
    MySQL v5.1 (module loaded)

    tried on 2 webservers.
    thank you for advice
    same here

    Fatal error: Cannot use object of type Installer as array in www\osTicket\setup\install.php on line 81
  • after i change the browser the old message is gon

    but now in the last step in setup got this message

    Fatal error: Cannot use object of type Installer as array in setup\install.php on line 32

    and i cant go to the setup again :(
  • @ahmed_badawy & @vladivlad We'll be pushing a new release today which will address the issue. For now, try disabling global variables.
  • will wait
    peter;26475 said:
    @ahmed_badawy & @vladivlad We'll be pushing a new release today which will address the issue. For now, try disabling global variables.
    ok i will wait for this Peter.
    (i cannot disable globals, i dont have these permissions on server - i am using external hostings only, where this is not allowed, (or i don't know trick that would work, did not find any on google yet).

    so I will await.

    Thank you Peter
  • peter;26475 said:
    @ahmed_badawy & @vladivlad We'll be pushing a new release today which will address the issue. For now, try disabling global variables.
    thanx and waiting for it
  • where is it?
  • peter;26475 said:
    @ahmed_badawy & @vladivlad We'll be pushing a new release today which will address the issue. For now, try disabling global variables.
    where is it?
  • Support Ticket System Offline

    hi folks, thanks for the great job about osticket, we were waiting the new version with great spectatives...

    We installed app from zip and git (both-os17-45b80f1) but in all cases get the same message: Support Ticket System Offline

    Already activated the Online (active) status through SCP.

    Could you give us any help about this issue?

    thanks in advance, df
  • Everyone,

    To get the latest changes - you'll need to download/checkout develop branch - not the master.

    Please note that, the code base is by no means stable and may change by the hour! Report any bugs as issues on GitHub, so we can address them.

    Thanks,
  • when will release the stable version, is there a specific date?

    and thanx alot for your hard work
  • html

    why you use text mail for reponse why not use hmtl mail to but example logo
    progression graphe of ticket
  • is there a demo available? I can't seem to get it installed on my server, but I'd love to take a peek.
  • nice

    I would just like to say at first glance 1.7 looks really nice, i know its still in developmet and more changes are underway.

    @peter is version 1.7 going to be compatible with php 5.3 and 5.4

    also as a feature request i am sure i am not the only one it would be nice if users could login with email addresses and their own passwords, since if customers go back to the site they dont want to have to remember their ticket number to view their tickets or have to recheck their email to get their ticket numbers.

    just a minor inconvience to some people.
  • +1 for using users email address for login.
This discussion has been closed.