I’m with you. I bought Ninox to replace FileMaker and I think it’s going to work out quite well. It was a recommendation from the forum.
Rob
1 Like
Filmmakers(owned by Apple) pricing has just gotten out of hand. Ninox is cheap and seems really good(still learning it).
But I think the Safari issue is something unique to your Mac. Unfortunately, it’s built into the OS and I don’t know of a way to just reinstall Safari.
Haven’t come across Ninox - will take a look.
Delighted to say that a re-install of OSX has banished the gremlins and sorted the issue. both sites look absolutely fine now. Sadly hasn’t made Rapidweaver’s preview engine any quicker when it comes to the larger sites - another problem I have been experiencing (along with others). Time for a RW re-install perhaps with plugins / stacks re-aadded one by one?
Not so delighted now… Closed Safari and next time I opened got a message that ‘you cannot use Safari it is being updated’ - not seen that message for a number of years.
Eventually re-opened and the exact same problems have returned on both websites - which were both completely fine until I closed Safari!
I’m suspecting there is a glitch with Safari 12.1 under High Sierra as it appears the install is failing somewhere. Wish it could be installed separately from the OS!!
@manofdogz - here’s a direct link to install Safari 12.1 without the OS. Just be aware that the latest Security Update may also impact Safari.
Fred
That’s interesting - didn’t think this could be done! As I recall, the message about ‘you cannot use safari - it is being updated’ occurred when it hadn’t fully installed so maybe this will do a better job. Do you think it is older than the last security update?
Anyway, I re-installed but the problem has not gone away. Time to ignore it I think!
@manofdogz - the Security Update came out after 12.1. Good luck. Maybe it will resolve itself over time 
Fred
@manofdogz So you are saying that the issue was with your local machine and nothing to do with Go CMS whatsoever?
I just want to have that stated in case anyone comes across this thread in the future.
I wish I knew. Problems have arisen on two new Go CMS sites displaying in Safari but it seems to be just MY installation of Safari - nobody else sees any issues and when I re-installed High Sierra (including Safari of course) the problems disappeared - although they have now returned. So it definitely appears to be primarily my install of Safari but on the other hand I’m not seeing display issues with any other of my sites.
However, there are 2 other factors about these sites which are new for me and either could be playing a part. One is I’m using Screens for the first time and probably have too much content on some pages - this could be causing overlapping content issues in the dog-training site. Secondly I’m using Yuzool’s Navigation stack for the fist time and notice that the ‘content starts below navigation’ option doesn’t work when you select fixed navigation. So this might be an issue where the dental care site is loading half way down the page. I’m sure all these could be tested but all i really want is to get the sites finished and some cash through the door!
Confused - i am! Burt I certainly don’t see GoCMS as the likely culprit.
1 Like
If I understand correctly how go-cms works, the user makes a GoCMS Page using their content stacks, and then that page is editable online using the password. GO-CMS needs to remember which page is which, so if you are testing out the software, like a normal person would need to do, you might not use the meta section of stacks to name the page and instead of a useful unique page name, you get the RW default name, which is probably something like “page1”. Then you might not know that the GO-CMS data will repopulate that “page1” with your test blog data, unless you use a FTP to remove any testing content from the server files. In my case, I normally test using very small jpeg files that have a picture overlayed with the size of the picture, Like 70 x 120. that way while testing page layout I get a visual of how different file sizes look and fit.
It was not clear to me in the beginning how to prevent these test blog pages from repopulating the page when I have finished with the testing and am ready to publish blog content.
If I was the developer of GO-CMS I would have on my support site very clear instructions on how to correctly name test pages and how to permanently remove testing content as well as a brief clear explanation of how the page naming structure controls the content.
I believe that many users often have multiple issues causing problems at the same time and consequently having more clear instructions from the developer would help alleviate lots of the questions support staff get.
M
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.