2015-12-07 21:44 GMT+01:00 Jacques PYRAT <[email protected]>: > Hi, > > Excuse my english, I read it every day, but don't write often. > > I'm using Dolibarr without any plugin since 2013. > It's a source of dilights, and a pain in the ass alltogether > > Why is it a pain ? > - link pdf generated have a content disposition that force the download > (there is a plugin to handle that : > <https://www.dolistore.com/fr/modules/340-Aper--u-document-3-3-3-8.html> > https://www.dolistore.com/fr/modules/340-Aper--u-document-3-3-3-8.html !) > (and I use browser extension to override this). Why ? Can(t it be a simple > link and let people right click to save ? >
You can achieve this just by a setup of your browser. Another solution, if you don't know how to do this, you can also set option MAIN_DISABLE_FORCE_SAVEAS to 1. > > This one, I think I could fork on github, but only if I'm sure it will be > integrated > - action are in the url or in post that leads the browser to redo the > action if shutdown and tabs are reloaded. In SPIP, actions are handled with > internal redirect so that you can comminicate URLS to other without garbage > ans reload tabs without a question like "Would you like to send the data > again ?" > Dolibarr was designed to be used without need to press F5, so for a common usage, this is not a trouble. I d'ont experience the message "Would you like to send the data again ?". Can you describe a use case when you have this ? - confirmations : why is Dolibarr diplaying confirmation AFTER reloading > the page : can't it be ajax overlay ? > Why ? > > - position of button to add a line and to validate : I click on the > validate loosing all my text to much often ! (consequence of precedent > point) > Sorry, i don't see. Can you provide more information on this ? A screen shot may help to understand. > > - I do not use plugins because the only one I've tried was overwriting > some part of Dolibarr code. > Such plugins are not pluggins, but code hacks. By definition a plugin does not overwrite any dolibarr files. It is a standalone directory. > > And also because I've read that after each update of Dolibarr, I should > desactivate and activate again each of those plugins. > Where did you read this ? It may be true that with a new version of dolibarr, you may need to upgrade also plugin (above all if plugins does not match dolibarr development rules), but need to disable/enable should be rare. > > > Thanks for reading. > > PS : I'm reposting because I've posted from another email not susbscribed > to the list > Jacques - www.pyrat.net > > > > _______________________________________________ > Dolibarr-dev mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/dolibarr-dev > > -- EMail: [email protected] Web: http://www.destailleur.fr ------------------------------------------------------------------------------------ Google+: https://plus.google.com/+LaurentDestailleur/ Facebook: https://www.facebook.com/Destailleur.Laurent Twitter: http://www.twitter.com/eldy10 ------------------------------------------------------------------------------------ * Dolibarr (Project leader): http://www.dolibarr.org (make a donation for Dolibarr project via Paypal: [email protected]) * AWStats (Author) : http://awstats.sourceforge.net (make a donation for AWStats project via Paypal: [email protected]) * AWBot (Author) : http://awbot.sourceforge.net * CVSChangeLogBuilder (Author) : http://cvschangelogb.sourceforge.net
_______________________________________________ Dolibarr-dev mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
