We have an issue with Preview in Wagtail CMS. I have looked around at several other people that have had this issue but none are the same as mine. As preview is not even working in Dev and we are receiving no errors to suggest what the issue might be.
We Use Wagtail 1.13.1 & DJANGO 1.11.8
When i click the preview button It just takes me to a new tab thats blank with no error or anything.
if i inspect the button I can see:
<button class="button action-preview icon icon-view" data-action="/admin/pages/30/edit/preview/" data-auto-update="false">Preview</button>
So I took: /admin/pages/30/edit/preview/ and manually pasted into the browser and it gives me:
https://domain.dev:8000/admin/pages/30/edit/preview/
I am still receiving no errors, which leaves me to believe either a setting is incorrect or this is a bug in Wagtail as it does not work in Dev,Staging or Prod
If anyone can shed more light on this topic it would be greatly appreciated as at least if i got an error I could look to resolve it. but i get nothing.
Where am i going wrong?
Related
So I install Ghost CMS and it is working great, but I noticed recently that the navigation settings (where I add new links to the menu and such) are acting strange and not working right.
So in the image above you will notice the ':80' port being added onto the domain. Which is fine I guess, but what is odd is that if i click out the field and then back into it it adds another port ':80' and continues to do that as many times as I click out, also if I tried to delete and save it immediately adds them back in. Look at Teaching and you will see what it ends up looking like.
Also when I go to the site front page and click one of the menu items I see a 404 error in the console saying the page doesn't exists.
I can't figure out what is going on it was working just fine a few weeks ago and I have touched anything on the server. I am stumped, I don't really know enough about Ghost so I am relying on a better expert to help me out here. I am using the Bitnami Ghost Cloud Image. and have the theme bleak installed.
Any Thoughts?
Is it just me, or is the angular-material "Getting Started" example broken?
On that page (link above), there's an inline codepen to show using angular-material. But the demo doesn't work! (In particular, I don't see a button to collapse the sidebar.)
Since I used this example in my started project, I spent quite some time troubleshooting it -- to no avail. Then, I realized the example itself it may be broken. And sure 'nuff, it is!
Does anyone know what the actual bug is, so I can work around it on my test app? It must have worked at some time; but I can't figure out why it's broken now.
Thanks!
That particular pen is working fine for me but I have noticed a few are not working, and it's due to the angular-material.js link being incorrect in the dependencies (under the pen's settings) the link provided redirects to the CSS.
This is intentional - the sidebar only becomes collapsable on smaller screens and is open on larger screens. Shrinking your browser window will show the collapse button.
That being said, the Getting Started page is definitely in need of an update. It is a good guide for a basic page structure, but the individual demo pages will be a lot better if you're looking to try out some of the components. (Every demo has a CodePen link to open an editable version.)
I am facing some strange issues with Firefox only and only on one of my PC's. I know these are not the issues with my website. But i am concerned more about it if my customers face this issue only with my website. I still want to confirm about it that if they are from my end or any other issue. Kindly help and provide me a better solution.
My problems are listed below:
1) Sometimes my profile image appears on other images or we can say replace my other images. Infact the profile image is also corrupted.
2) My Dropdowns sometimes shows weird design as shown in the screenshot below.
3) Scrollbar image appears on my saved bookmarks.
I have tried many solutions to resolve this. Here are the troubleshooting steps which i have already tried:
1) I disabled all of my add-on plugins.
2) I resetted my firefox.
3) I uninstalled my firefox , shut down my computer and then i reinstalled it . Still i faced this issue on my website only.
Kindly ask if you still want to know something more about it.
Thanks in advance for any help or Suggestions.
We have never experienced this issue in Umbraco 4, but we've got this twice in Umbraco 7.
The Problem
So we've got a page: www.mywebsite.com/sale
It has been working for a month, then suddenly it shows 404:
The (non-ideal) Solution
We could change the template of this document, eg. from SalePage to TextPage, then back to SalePage.
That will temporarily fix it.
But after IIS restart, or after republishing the page, it will show the 404 error again.
For a permanent fix, we have to change the page name, eg. from Sale to Sale1.
The Question
Sometimes changing the page name is not an ideal solution at all.
Has anyone experienced this? Or know where to look? May be the database has a corrupted entry somewhere..?
We found the problem! We have this structure under Content:
Home
HomeSlide1
HomeSlide2
Pages
Sale
About Us
etc
The problem started when someone created a "home slide" under Home called "sale".
So, both Home/sale and Pages/Sale has the same path: /sale/
Deleting/renaming Home/sale fixed the problem.
This sounds like a corrupt cache.
To find out what went wrong:
Investigate the xml config (/config/umbraco.config)? I suspect this file will still contain the correct information.
If the umbraco.config file doesn't contain wrong elements, check the examine indexes. When you do a "rebuild indexes" from the developer node in the umbraco backend the problem might go away also.
If you know what is going wrong, you can start finding a solution for fixing the issue. E.g. finding out which action went wrong.
This is an issue I've been experiencing only for the last few days; when following a link to jsfiddle, or even going to the jsfiddle homepage (on IOS 6, iPad 2), jsfiddle doesn't initialise properly, and all I see is "initialising the awesome". Even logging in and creating a fiddle doesn't work. The issue only seems to have appeared since some recent downtime which I assume they were updating jsfiddle during it. Has anyone else experienced this issue/have a fix?
NB: this occurs on both safari and chrome.
Alright, I've sent an email to jsfiddle support, and I came up with this response:
We're working on that.
https://github.com/jsfiddle/jsfiddle-issues/issues/330
For the moment please use draft feature or add /embedded/result to the
URL.
http://doc.jsfiddle.net/basic/introduction.html#draft-page
Regards, Piotr
Hopefully this means that the issue will be fixed soon, however, in the meantime, use: (for example)
http://jsfiddle.net/ (your fiddle)/embedded/result
I.e, just add /embedded/result to the end of the url as Piotr suggested.