[asterisk-bugs] [JIRA] (ASTERISK-25818) Blank extensions.conf, refuses to perform "dialplan save"

[Matt Jordan (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-25818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=229750#comment-229750 ] 

Matt Jordan commented on ASTERISK-25818:
----------------------------------------

And just to include your original text:

> Secondly, the new asterisk forum is a web 2.0 piece of garbage that is not even possible to log into, please restore the old forums and fire the perps responsible.

Hi! That's mostly me.

You're more than welcome to call Digium and ask them to fire me. My boss would enjoy the chuckle.

> Blank extensions.conf, refuses to perform "dialplan save"
> ---------------------------------------------------------
>
>                 Key: ASTERISK-25818
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25818
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 1.8.32.3
>         Environment: Centos 7
>            Reporter: na
>
> Asterisk went ahead and destroyed the extensions.conf file, and now refuses to "dialplan save". The command "dialplan show" does show a version of the dialplan which I would have to painstakingly rewrite by hand, how about getting that to match the actual code so as to actually be useful? I could have just re-pasted the raw plan back in but no dice with how the output is formatted.
> -----------------------------------------------------------------
> CLI> dialplan save
> I can't save dialplan now, see 'extensions.conf' example file.
> Command 'dialplan save' failed
> -----------------------------------------------------------------
> While I have your attention, please restore all the broken CLI commands which now require the pesky and burdensome "core" prefix, no one wanted that. Also some need it and some dont work with it, making a standard syntax impossible and unmemorable.
> Secondly, the new asterisk forum breaks the continuity with past eras, and is not even possible to log into. 
> Thirdly, this interface itself is a tad bit of a bear. It has flipped back a complaint at me now about 10 times. versions: Version with id '1.8.32.3' does not exist. It very well indeed does. I had to wait for a dropdown list to appear and click it instead of just typing in the numerical version.



--
This message was sent by Atlassian JIRA
(v6.2#6252)