mura cms new site: preview not displaying - coldfusion

I have set up a new site on mura cms 5.4 and gave it the domain localhost but nothing gets displayed in the preview.it is a site in construction and so assigned it localhost as the domain.
why doesnt it allow me to preview the changes?
it keeps giving me page cannot be displayed.
i have tried getting to it from the link that appears on the top of the page
please help. greatly appreciate it.

I advice to upgrade to the latest version of Mura (version 6) and see if the issue still occures. Since Mura 5.4 is an old version, there is a big chance the issue is fixed meanwhile.
It's very easy and save to upgrade Mura. http://docs.getmura.com/installation-set-up/upgrading-mura/

Related

OpenCart 3.0.3.8 upgrade to 4.0.1.1

I recently upgraded an old store from 2.0.1.1 to 3.0.3.8 but to comply with PHP8 I need to upgrade again from 3.0.3.8 to 4.x. My question stems because I was able to successfully install the new 4.0.1.1 storefront, but I am no longer able to access my admin panel. Attempting to login to my admin will always give me the error that the account does not exist.
I have double checked the config.php files in both my root & admin folders and the database information stored there is correct. Also, I checked my actual database to make sure the user accounts weren't deleted in the upgrade and they were not.
I don't see a lot of documentation about the upgrade process to a 4.x OpenCart storefront so I am coming here in hopes someone has been brave enough to attempt this upgrade that may be able to point me in the right direction. Some tips and tricks would be greatly welcomes because I imagine this is just the first of many moles I am going to need to whack.
Let me know if any code would be needed/handy, but keep in mind this install is basically all stock barebones at this point because I haven't even tried to activate my custom theme yet (mostly because I can't access the admin to activate it).
Solved this by upgrading to the OpenCart 3.x.x_Maintenace branch, instead of OpenCart 4.x.x version, as it is also PHP8 compliant and much more stable.
For anyone with similar issues, they can refer this link.

Installed version not tested with active version of WooCommerce 4.4.1

I continue to get this error message on my wordpress front page:
Warning: Cookie paths cannot contain any of the following ',; \t\r\n\013\014' in /var/www/aveugle-shop.com/public_html/wp-content/plugins/woocommerce/includes/wc-core-functions.php on line 1035
I can't figure out why this message is showing?
My hosting said that it was because they updated their php database (or something), and all i needed to do, was to run back their old one, by inserting a snippet into .htaccess file.
This worked for a day or two, and now it's showing again.
Do anyone know what the actual issue is, and how to fix it?
My woocommerce status also says this on a bunch of plugins, and i don't know if that's the fault:
Installed version not tested with active version of WooCommerce 4.4.0
I dont know if this is the correct solution but I got the same error just now.
It happened to me when I upgraded PHP from 7.2=>7.4.
It seems to originate somewhere from the database because I solved it by just importing the database again from my testserver, same database, same codebase but all of a sudden, it started to work after reimporting db... A cache issue maybe?

Refused to display iframe or embed tag in django 3.0 and chrome

I had a django app that used an iframe to display a pdf stored in my local machine, something like this:
<embed src="path_to_file.pdf" type="application/pdf">
Everything worked just fine in all supported browsers... Until today.
The app suddenly stopped working on Chrome and the console displays the message Refused to display 'path_to_file.pdf' in a frame because it set 'X-Frame-Options' to 'deny'.
In other browsers it's still working as usual. I don't know if Chrome just made an update or what changed but it is not working anymore. ¡Any help would be appreciated!
After going through a lot of similar questions and trying lots of different things, I finally found a solution for my problem thanks to the django documentation.
Since Django 3.0. The default value of the X_FRAME_OPTIONS setting was changed from SAMEORIGIN to DENY.
So I just had to add X_FRAME_OPTIONS = 'SAMEORIGIN' to settings.py and the problem was gone.
I still don't know what change made my code stop working because I already used django 3.0 version since it was released, probably it was a Chrome update.
Recording an incident here specifically with a Vimeo embedded video. I needed to set SECURE_REFERRER_POLICY to None. The default was changed in Django 3.1.

Sitecore menu items not working - javascript errors

So I'm just starting to work in sitecore and for some reason none of menu options are working in Page Editor mode for the site that I'm working on. We pretty much have the sitecore website and add some extra page content (MVC app files) to it. I'm getting a variety of javascript errors.
In content Editor, if I click the Sitecore logo and click on Properties I get
TypeError: contentIframe.dialog is not a function
In page editor if I click on the blue components button I get:
TypeError: i.widget is not a function
I'm guessing maybe it's a conflict between jquery that we're using for this website and whatever Sitecore is using. I think it's 7 - but I can't see it via the menu option :)
That guess could be wrong - it could in fact be a browser issue, but I've ensured Firefox is not blocking popups. It doesn't work in Firefox, IE or Chrome though.
The weird thing is that no one else on the project is having this issue it's only on my computer.
Edit - I've also just tried re-installing (7.2) without any local code changes I still can't click on a page and go to Presentation, Details (Layout) - I get a TypeError: contentIframe.dialog is not a function
Edit 2 - I've noticed that I can use sitecore in the QA environment and the dialogs work fine there. So it's something specific to my local build of the site we have (sitting on top of sitecore). But the dialogs just throw jquery errors when I do stuff locally. I was hoping it would be a browser setting but doesn't look like it.
Edit 3 - What I've tried this morning.
Same thing happens in all browsers (FF, IE, Chrome) and I’ve cleared
my browser cache I can access the QA site and the dialog appears as
expected
Copied across the QA site files, pointed my local Digital
site in IIS to the new folder – dialogs don’t work
Team member tried accessing the site from his machine (pointing to my IP address) and
dialogs work for him
I tried seeing if another local sitecore site dialogs were working – but the menu items for that are opening as new windows (so I’m guessing it’s a sitecore 7.2 feature that they appear as jquery dialogs??)
So after googling for rejected-by-urlscan it turns out there's a program called UrlScan from microsoft that was blocking my dialogs. Uninstalled that and I now have dialogs appearing for sitecore. Very exciting :)
I guess it is a problem with some browsers plugin. Sitecore is sensitive to scripts that are used(different versions of jquery or prototype.js). Plugins can inject scripts to HTML source of pages and it can cause errors.
Try to switch off all plugins at least at one browser and check the results.

Joomla 2.5 admin page will not show

I am upgrading from Joomla 1.5 to 2.5 and developed my site in a sub folder on the live site. Everything was working fine in the test area. (dev site is here: http://academyphysicians.com/test) Used Akeba backup and moved the site to the root folder. Front end is working as expected, but the admin page is blank after log in. New install of 2.5 is here: http://academyphysicians.com.
I was googling the issue and saw that php version may be the problem. I am running v 5.2.14 and I saw that 5.3 may be required. It seem like I would have had the problem in the test site if that was the case. Anyone have any ideas?
If the site worked in a subfolder, then it will work in the root. When you moved the site you did something wrong or you have touched a setting you shouldn't have because Joomla should be folder agnostic.