Dashboard - 3rd Column - $100
-
Just because it is not tested enough and might badly affect other themes although I tried to avoid this. -( Lots of css stuff looked puzzling to me as usually you do not understand other's people thoughts ver well when they design web-pages using css (all this coordinates, margins, pads, relative-ness etc).
Anyway I'll provide patches and you decide. -
OK I understand your hesitation and can appreciate that.
I'll look it over and worst case scenario we get it in for 2.1.
-
I've sent patches.
I've got $300 from bounty starter. Thanks!!!
I've donated $100 out of these $300 to pfSense. Thank you, pfSense team! -
This is just awesomeness!!
Thx Evgeny! looks very good! Sorry I couldnt contribute more than I did.
-
I think we did a good thing here for the whole community. And I obviously wanted it bad enough to pay for it and test it. I hope the core team finds it safe and suitable for inclusion before 2.0 goes RC. Maybe not, but it's obviously cool enough to include down the line.
Thanks again, Evgeny.
-
Is it backwards compatible with 1.2.3?
-
Backwards compatible?
Nyet! What we've got in 1.2.3 is what we've got, unless there's ever a 1.2.4, I suspect.
Good question for the devs though; Will there ever be a 1.2.4 with a backport of …stuff... from 2.x?
(Way off topic though...) -
No, 1.2.x is dead; Long live 2.0. :-)
-
I was only thinking about the mod here :)
-
The 2.0 dashboard is a lot different than the one backported into the 1.2.3 dashboard package… At this point I doubt it would be worth the effort to backport the changes into that package.
-
Thks Jim :)
The 2.0 dashboard is a lot different than the one backported into the 1.2.3 dashboard package… At this point I doubt it would be worth the effort to backport the changes into that package.
-
I left the 3 column dashboard up all night. It's been 24 hours and no errors, complaints, or lock-ups.
So far it's all good.
-
The third column package had been running for a couple of weeks then I upgraded last night and had issues. Any ideas from the core team on whether or not this package is going to see general distribution soon? Sullrich and Supermule think its cool. So, can we get it included in the general distribution, please?
Thoughts and comments welcomed.
Thanks.
Bryan
-
Probably need to reinstall the package. The upgrade would have likely reset the PHP include files. The downside to packages that modify the base system I'm afraid.
–Bill
-
Yes, before upgrade please uninstall the package. It removes everything it brought in and restores all the file it replaced.
I think 2low4zero's question was 'why can't we put this package into official pfSense package repository?' rather than 'why did I have issues after upgrade?' -) -
Yes, before upgrade please uninstall the package. It removes everything it brought in and restores all the file it replaced.
I think 2low4zero's question was 'why can't we put this package into official pfSense package repository?' rather than 'why did I have issues after upgrade?' -)Sure, I understood the question, but I wanted to answer for others that might have issues. I don't have an answer to the package question, I thought you had commit access to the package repo. Or do you mean getting this in the mainline pfsense repo? If the latter, I think it's going to have to wait until after 2.0 is out.
–Bill
-
It's not ready for mainline but I think perfect for packages.
I do not have commit access and I do not want it as I am not that experienced with git and theoretically can screw up things. What would be nice is if somebody who has commit access would merge this package from my repo to main packages repo.
Thanks. -
It's not ready for mainline but I think perfect for packages.
I do not have commit access and I do not want it as I am not that experienced with git and theoretically can screw up things. What would be nice is if somebody who has commit access would merge this package from my repo to main packages repo.
Thanks.I can commit to the packages mainline on behalf of the creator. The only thing I ask is to only have to commit a final product.
-
I can commit to the packages mainline on behalf of the creator. The only thing I ask is to only have to commit a final product.
Then please commit. It is pretty much final, I've been running it for some time without any problems. Bounty starter has not claimed any issues except problems after upgrade. But I do not know how to resolve upgrade conflict, if files touched by the package are upgraded then you can't do anything about it. The only way to avoid this problems is to uninstall package, upgrade the system, install it again. In any case the package does not touch functionality, it only affects 'appearance'.
-) -
Thanks to tommyboy it is there!
I appreciate your help in this matter.
