Branding package maker

RouterOS General
1

Is the branding package URL broken? The error will appears after I click on make for V6.7 and above.
2022-11-06_00-09-57.jpg

2

up.

3

It’s up now?

4

NO, I await an answer or confirmation that the ERROR is not at my end.

5

Works for me. https://mikrotik.com/client/branding
Is the problem still there? Can somebody else confirm?

6

Thanks for your reply, The error appears after clicking on making a file.
2022-11-07_17-53-05.gif

7

I confirm, on Make for v6.47 and above do error 500 or blank page after a 10s timeout.
On Make for older versions simply reload the page without do anything.

8

Problem confirmed, working on it

9

Problem has returned, it was working yesterday but now broken again.

10

just try this and show the same error :frowning:

11

issue fixed … again :slight_smile:

12

Branding page in error 500 again.

13

fortunately, I got all my testing done and finalized the new config package I had to build late last night while this was still working, but the branding maker outages this week put me 3 days behind schedule on projects, Normis can you comment on what the root issue is and what’s being done to ensure the next time it’s fixed, it actually stays fixed?

14

Hi. The Branding page works again
YET !

creating packages for “6.47 or above” th epackage is created , but
it is recognized as package in ROS BEFORE 6.47, even if it actually does nothing and on rebooting the package is installed as version 7.6. Uploading the file in file msagaer appears with package icon
it is NOT recognized as package in ROS 6.47 or above, also in 7.6, which should be the version it is created for. Uploading the file in file msagaer appears with generic file icon

creating packages for “older versions” the package is created , but
it is NOT recognized as package in file manager, it appears as generic icon. on Router reboot the files stays in file manager and it is not installed.

UPDATE
creating package for older version the file is not recognized as packed. it stays in file manager after reboot, with generic file icon.
YET

  • the skin ARE INSTALLED
    the custom ogo for webfig page IS NOT USED
    the custom terminal banner IS NOT USED

Hope to be able to give you more updates soon.

15

Please provide more information about the issue that you have with the Branding package maker.
What are you trying to achieve?
Can you please give a step by step instructions to try to reproduce your issue?

16

HI

I’m trying to produce a package with the following content

  • default name for router, i.e. Identity


  • custom branding logo in web login page


  • custom website url


  • custom skins, one for installer, one for user. Related users will be created by custom script


  • custom default script for router reset


  • some custom files, used by the custom default script. these files will contain data, not scripts

the custom script is already working. Int he current release it is written in the router by NetInstal as the script must be customized.
New release for our system shall have a default custom script for every router, and the costumization moved to the custom files, all ROS shall be upgraded to 6.49, of course

For current tests I’ve included in the branding package

  • the installer SKIN


  • the custom logo

But I cannot make it working nor in old ROS <6.49, neither in the newer 6.49 or above and 7.x

Step by step instruction

  • Enter the branding page


  • clear all fields


  • upload custom skin (alredy in use in routers. Currently it is uploaded by ftp or manually by winbox)


  • upload the custom mikrotik_logo.png (I’ve dowloaded the mifrotik default logo, cleanded and pasted in my custom logo, then saved in PNG format using GIMP)


  • Press MAKE button, choose Make for 6.47 nd above


  • download the file


  • drag and drop the file using winbox in a router formatted by netinstall with ROS 7.6


  • the uploaded file appears in file manager, but has the default generic file icon


  • reboot the router

the file is deleted, but no branding package appears in package list.

Best Regards

17

After reboot, the branding package should not be in the package list.
All fields that have been filled in must be applied after reboot, skins and scripts can be found in the /file menu

18

so the branding package appears only if written by NetInstall ?

why the custom logo does not appear ? but the skin does !

19

Now the custom logo works
Difference from previous tests
when I upload the custom logo, the file now appears as mukrotik_logo,.png
in previous tests (this morning) the uplaoded logo appeared as logo.png

definitely something changed.
Thanks for your effort!