@whitexp:

fixed in 2.3.a.20151231.1726

This kind of issue was happening when a new version was being rsync'd. I've change directory structure to help with cases like this

@yon:

I find upgrade not normal. it is not real upgrade any code.

Since we are in alpha state now, pfSense main package version changes on every incremental build. So lets say a new version of an additional package (e.g. pfBlockerNG) was committed, then pfSense package version was incremented. If you don't have pfBlockerNG installed you will still see pfSense upgrade.

@Sopalajo:

I am testing v2.3-Alpha, and it seems the drag and drop feature to change order in Firewall Rules does not work.
I have created a rule and would like to move it up. How can I do this with CLI?

Maybe you are using an old snapshot, because it was fixed.

on CLI you cannot do it

Fix is working thanks.

@Steve_B:

I think that is because you did not "Apply" the changes (creating a new limiter) before adding the new queue, so the limiter didn't really exist.

I have suppressed the PHP error message and altered the error message presented by the GUI to include "Did you remember to apply any recent changes?"

Yup forgot to hit apply changes after every step

Thanks.

The ADI installer has the ADI console settings in the installer. Past that point it's the same as a full install. The code to keep the ADI console active is in every image, just needs a special installer so it will work when booting the installer.

You can upgrade to a new 2.2.x or 2.3 from there just fine, or install 2.3 fresh from an ADI 2.3 image.

Fixed.

Thank you  :D

Yes, its working now! Thank you.

System > Update, system info dashboard widget, option 13 from the console, all of those update 2.3 to the latest available version.

yeah guess i must have left it open closed browser and reopened browser fixed it

Sounds like a poorly behaved password manager filling in your admin user/pass when you edited the entry.

Exolon posted a fix here:
https://forum.pfsense.org/index.php?topic=102470.270#lastPost

Just need to add the following to line 500:
id="widget-_panel-footer" class="panel-footer collapse">

I'll get that in the next PR…

OK thanks. I've added some code to /etc/inc/upgrade_config.inc to fix that.

Thanks for taking care of that :)

I don't have a good way to test it with the system I'm currently running, but it appears to be fixed.  If I pick an interface that's invalid, in the past it would spit out those php errors, when I do it now, it actually responds with something reasonable:

The following input errors were detected:
Interface supplied as member is invalid
Interface supplied as member is invalid

It was a regression introduced by me, sorry. It's fixed now!

Thanks. This issue has also been corrected and the mask now saves correctly.

That was definitely my issue.  Disabled the ramdisk and was able to upgrade like normal.