I have 2 master pages, 1 for home, 1 for the secondary pages. my home master page is showing up on all my secondary pages when I publish.
the real background should be longer and have no brown band until the bottom of the page. Please advise!!!!! (it used to work fine, now with the new update it doesn't)
Message was edited by: Lisa Jaworski2
What I mean is, while working in Plan view you are able to assign different Master pages to each of your site pages. You can do it by dragging a Master page thumbnail onto your site page thumbnail. In the image below, the labels highlighted in orange indicate which Master Pages I have assigned to each of the pages in my site. That said, if it's showing up correctly in Design and Preview mode, it's doubtful that's your problem.
When you update your site are you updating the whole thing, or just portions. I'm not sure this would have an impact either way, but I'm curious.
yes, they are correct in plan view and yes, this past time I updated the whole site because I had to "deactivate and reactivate Muse" because I had just encountered the "Unauthorized name problem" that was fixable by deactivating muse.
Another weird problem is my nav topics are supposed to be black and roll over to red, but now they are previewing and publishing in magenta???? wierd...... any thoughts on that as well as the master page problem?
well, now I re-published all resent files (not just an update) and the bottom boundary margin is wrong on the home page (and the coloring is off, its very faded) and now all the secondary pages have the correct background master B page BUT the navigation words that should be black on that master page B are fuschia???????
What is happening? Engineers please.... fix.... this.... bug.
Hmm, interesting that it is not showing up in Muse itself.
Could you try exporting it to HTML, and see if the problem is reproducible locally? To do this, go to File > Export to HTML and you can choose a folder to export the site to. When it completes, there should be a link to "View Site". Click on this link and see if it has the same issues. If it doesn't, try logging into your Business Catalyst account and deleting all of the files, and republishing again from Muse.
If it does have the same problems, or if deleting the files from Business Catalyst does not help, send your .muse file to email@example.com so that we can take a look and try and help figure it out. In the email, be sure to include a link to this thread, and "ATTN: Andrew" so that we know where it was coming from.
the .muse file is 32 MB that won't go over email.. is there an ftp?
it had similar problems.... the Master B page ended up having the master A page on top of the Master B....urggghh!
I've found the bug you describe. The issue is that the backgrounds on the master page are both being exported with the same name, so one is overriding the other. Unfortunately this won't be fixed for the release version coming out this week, but I have logged it in our system. In the meantime, to fix the issue, you can place the background image for the homepage on the homepage itself, instead of on the master page, and it should solve the problem.
WELL the problem switched with the last upload to the Master B page and now the home page is showing up on top of the pages associated with master B. The problem is the Master B page is a variable depth... so how would I "temporarily fix" that. when I goto put the correct background photo on each page itself, the depth keeps moving.?????
thanks for your quick reply
I don't see the links as Fuscia from my screen. There might be a browser setting you have set to override these styles. If that is not the case, your browser may be styling it differently because you have visited those links.
And I'm not sure what you mean by the depth keeps moving. I do see that the height of your pages is variable, and from the looks of it you have your background image set to "Scale to Fill" so it will resize the image to try and make it fit the size of the page. If you remove this, your image will stay the same size, but on pages where your image is shorter than the page, a background color will show through. You can make this background color the same as the background color on the image by using the eye-dropper tool, and it should remove any ill effects of a shorter background image.
I have done what you said to do, however... if I want the bottom of the extended page to be an eye-dropper sample but want the browser background (outside of the page outline) to be brown... how would I do that?
Also...will I be notified when this bug about master pages is fixed???.. because it still isn't perfect as I could not register the bottom of the page to the margin.
The are two background fills you can control on the each page. The first, is the browser fill, found in the control strip on the far right hand side (the default for this is a grey color, what you have as brown). The second is the page background fill, which will control the background of the content within the page border (the default is white, and it is where you currently have the image set for the page background). You will want to use the eyedropper to set the background fill on the page, which will sit below the image. You shouldn't need to change the fill for the browser background. Hopefully I understood you correctly, but if I did not, let me know and I can try and help further.
As for the bug, this will be fixed in an upcoming release of Muse. I'll post here as we get more information.
I have a similar issue. In Design view my home page shows a footer. In Preview and when published, the home page footer disappears.
We exported to html as guided above; the footer wasn't there.
It appears on every other web page, but not on my home page.
See images below.
This is the design view:
This is the preview view:
Thank you for any help you can give me.
Gay Ann Rogers
Yes, it is published at www.GayAnnRogers.com
Please forgive it right now -- it is very new and not complete. I am in the process of migrating from my former website.
Thank you for any help.
Gay Ann Rogers
Thanks for confirming that.
I think you have missed out on some statcounter code that you inserted using the Insert HTML feature. The statcounter code ends with a code like ...</a></div></noscript>. In your case, you missed out the closing </noscript> tag (at least). Muse checked that and placed a </noscript> tag at the end of the html code - effectively hiding ALL code on page following the <noscript> tag in statcounter code.
I recommend you place complete code again in the HTML box for statcounter. Although just typing </noscript> at the end of statcounter code in HTML box would do the trick.
Hello again, Vikas,
You were so helpful the last time I wondered if you would help me with another problem.
Below are three photos. Photo #1 is the page as I designed it and as it appears in 'Design'.
Photo #2 is how #1 looks in 'Preview'. Note the text is the same but the image is different.
Photo #3 is later on in the series. It's as if 'Preview' for photo #1 stole the image from photo #3.
Do you know what happened?
The photo below is the page in 'Design'
In preview mode the page immediately above is correct.
If you wish to see the pages, they are as follows:
Photo #1 which is in my Design mode doesn't appear on the published site.
Thank you for your help.
It appears as if you are not adding the image(s) using File > Place option. Rather you are copying the image from another image editing software like Photoshop and then pasting in Muse using Edit > Paste or Ctrl+V or Cmd+V.
If that is the case, I would suggest that you first save your image as a JPG or PNG on disk and then import that into Muse using File > Place.
Let me know if that is not the case.
I did use the File > Place option, but I went back and File > Placed a different copy of the photograph and all is well now.
Thank you. I should have thought of replacing the photo.
Here's another problem
The page splinters. It is OK in Design, but it splinters in Preview and sometimes (depending on the size of the page) in the published version.
See photos below:
Here is the URL for the published page: