I can not to subscribe on change of all sections in Stores ->Configuration using event admin_system_config_changed_section

[katesuykovskaya]

Steps to reproduce

1. M 2.0.7
2. Create extension, create etc/adminhtml/system.xml there
3. add section tab with id, that contains number, in my case "b2b" https://drive.google.com/a/interiorwebdesign.com/file/d/0BzTvZltZJMLlemNCOGVwdUM5S00/view?usp=drivesdk
4. create etc/adminhtml/events.xml and add event listener to listen to changing of this section https://drive.google.com/a/interiorwebdesign.com/file/d/0BzTvZltZJMLlRFpqOEIyc2RKRW8/view?usp=drivesdk

Actual result

1. Error message Invalid XML in file D:/OpenServer/domains/magento207.loc/app/code/IWD/SalesRep/etc/adminhtml/events.xml:
   Element 'event', attribute 'name': [facet 'pattern'] The value 'admin_system_config_changed_section_b2b' is not accepted by the pattern '[a-zA-Z_]+'.
   Line: 3

Element 'event', attribute 'name': 'admin_system_config_changed_section_b2b' is not a valid value of the atomic type 'eventName'.
Line: 3

Element 'event', attribute 'name': Warning: No precomputed value available, the value was either invalid or something strange happend.
Line: 3

Expected result

1. There should be ability to subcsribe on changing of each section, so I see 2 possible options:
   • extend regex to allow numbers be in name of event, or
   • disallow to set name of section, that contains numbers
     In other words, patterns, that are used to validate there values should be compatible.

[mtauqir]

I am on 2.1.4 version of magento.
I am still seeing this validation error but on events.xml file validation.

I am trying to observe an event from a third part module. The event has a number in its name. That number is in actually third party company's name.

Strange thing is that they are able to raise this event with numbers in its name, but XML validation prevents me to observe it. And obviously due to copyrights I am not allowed to edit their code to rename event name.

[orlangur]

This was fixed in #10837 for 2.3.x.

[okorshenko]

Hi @katesuykovskaya. Thank you for your report.
The issue has been fixed in #12758 by @Mobecls in 2.2-develop branch
Related commits:

• 937b26d
• 85fa671

The fix will be available with the upcoming patch release.

[magento-engcom-team]

Hi @katesuykovskaya. Thank you for your report.
The issue has been fixed in magento-engcom/magento2ce#1362 by @magento-engcom-team in 2.3-develop branch
Related commit(s):

• 4705e23
• 6d355e0
• 77f34cf
• 748ab4d
• 90f9d95
• 44ca24f
• f0b7f2b
• c3e1d93
• 4810755
• 4709a22
• a2b9fab
• ac7df33
• 245238d
• 2c153c3
• 48a72fa
• 625f685
• afa4516

The fix will be available with the upcoming 2.3.0 release.