Your comments
Disclaimer: I like the fact that additional features for GLPI are possible via plugins: this makes the GLPI core less bloated.
Why integrate a plugin into the GLPI Core? If the plugin does the job there is no need to make it part of GLPI.
If you think the plugin's features should be integrated into GLPI's core: please explain why it should be, which advantages it would brings, why the plugin-solution is not working (or badly).
Could you explain what theses notifications should look like and/or behave?
Isn't it a extension/duplicate of Add the posibility to put Maps and the option "Ubication" with coordenates and metadata ?
Please write in english on this UserEcho project.
Are you suggesting to add a feature that would make GLPI list all existing (see note below) GLPI plugins on "Setup > Plugins" page (or a sub-page of this GLPI area) and allow to fetch their installer directly from this page (+ installation and activation as currently) without leaving the browser?
This is a good idea.
« all existing » = any plugins listed on multiple configurable directory/sources (initial one being: http://plugins.glpi-project.org/).
Are you talking about this Wiki?
Don't know if it still used but it is listed on the official GLPI website.
You mean associate the computer the requester user is using to the opened ticket?
Tickets are not only for computer issues, it can be for phones, printers, Internet connections, etc.
How could GLPI determine such information when a user is associated to more than one computer?
In the "Create ticket" form, user gets prompted for the element, his computer is in that list.
Can you provide more informations about the context: what were you doing to make this error happens?
Which web server are you using?
Is it returned to the browser? Is it in the web server logs? Is it in the application logs?
I'll provide a translation of initial idea:
Hello,
Regarding notifications, the ##ticket.urlapprove## placeholder currently links to Ticket tab (main tab for Ticket) instead of Processing ticket tab. Yet it would give the user a one-click access to solution approval or refusal from the notification e-mail.
Thanks
I'm +1 on this: it is sometimes difficult to obtain feedback from end-users, let's make sure nothing gets in their way.
Customer support service by UserEcho
Disclaimer: I forked the Room plugin (on GitHub) and is making it up-to-date with new GLPI releases.
You can grab a GLPI v0.84, v0.85 and v0.90 compliant version of the Room plugin on GitHub: https://github.com/C-Duv/glpi-room/releases
Also, why integrate a plugin into the GLPI Core? If the plugin does the job there is no need to make it part of GLPI.
If you think the plugin's features should be integrated into GLPI's core: please explain why it should be, which advantages it would brings, why the plugin-solution is not working (or badly).