Bug 2018.1: master pages & browser Fill

[Yorh_Ekin]

So, I have designed 100 web pages in Adobe Muse.

All 100 web page layouts contain individual browser fill images.

( I was considering to re-design my site for better Google rankings

in search engine technology in artificial intelligence. )

The master page does not contain a browser fill background image.

I add the master page to my 100 web page layouts ...

and? ... what happens?

All browser fill settings I have individually set for every single page

of my 100 web page layouts ... disappear ... gone.

That doesn't make sense at all if a master page makes huge changes on

web page settings I have set individually for every single page.

So? Which page has the higher priority?

The master page or the web page? I mean developers could at least

create a dialog box which says.

" Overwrite the background image or keep the background image? "

Simple old school question on my opinion.

THANK YOU

[ankushr40215001]

Hey Yorh,

The concept of the master page is for those objects of the site which you want common in all your pages associated with it.

So as I understand that you might have applied a master page with a blank background image and the same has been applied to all the pages.

However, you could also have reverted it using Ctrl+z (Edit > Undo).

Regards,

Ankush

[Yorh_Ekin · Accepted solution]

No, I haven't changed anything. It's a conversion problem of Muse converting

a 2017.0 site project to 2018.1

In general ... the main point is as in most cases in my 25 years of experience

with developers.

Developers may do developing but they don't have time to design a website

on their own to test the result. As said it's like skateboarding, you do the same

trick again and again and again until it works with every try without failure.

On my personal opinion the workflow in software development is as follows.

1. Adobe chooses a bunch of web designers who are making websites using Muse.

2. The web designers offer them their .muse files for testing and evaluation purposes.

(The site projects contain only Muse stuff and do not make use of third party widgets

just to make sure it's only about the application and its own functionality.)

3. You install a testing environment by using four different machines with the same OS versions.

Machine 1: Adobe Muse 2017.0

Machine 2: Adobe Muse 2017.1

Machine 3: Adobe Muse 2018.0

Machine 4: Adobe Muse 2018.1

4. The development team uses the offered .muse site projects from various web designers

to see if their stuff works by converting them from version to version and making sure nothing breaks.

That's how development on my opinion should be done efficiently and correctly. Everything

else is just a lot of blablabla and endless forum postings developers can reduce by using the

methodology as mentioned above.

DONE.

[ankushr40215001]

Thank you for the valuable input, however now as the further development of Muse has been put on end.

The concept given above by you can be used for any other Adobe products as well.

Our product team will take this as a positive feedback and try implementing further in all their testing strategies.a

Regards,

Ankush