I have installed foswiki and made basic configuration changes (enabled/disabled plugins, change of patch etc.). Since that time I can see red error message on every window "No such theme PatternSkinTheme" and the banner with Foswiki's logo, "Jump" and "Search" textboxes is located in the end of the pages.
I tried to revert the configuration back, however the situation still persists. Does somebody know where might be the issue?
Thank you
So there were 2 issues:
First issue was related with error message and the second with incorrect position of the banner.
First issue
The message disappeared after adding in /path/to/foswiki/lib/LocalSite.cfg following lines:
$Foswiki::cfg{JQueryPlugin}{Themes}{PatternSkinTheme}{Enabled} = 1;
$Foswiki::cfg{JQueryPlugin}{Themes}{PatternSkinTheme}{Url} = $Foswiki::cfg{PubUrlPath}/$Foswiki::cfg{SystemWebName}/PatternSkinTheme/jquery-ui.css';
Second issue
Update in file /path/to/foswiki/templates/foswiki.pattern.tmpl structure of the webpage. I removed %TMPL:P{"topbar"}% from the definition like this
...
</div>%TMPL:P{"endsidebarwrapper"}%%TMPL:P{"topbar"}%%TMPL:P{"bottombar"}%
...
and place it to
...
%TMPL:DEF{"main"}%<div class="foswikiPage"><div id="patternScreen">
<div id="patternPageShadow">%TMPL:P{"topbar"}%%TMPL:P{"metanavigation"}%
<div id="patternPage">
...
Related
I have finally successfully installed the Meteor package md-blog from xolvio. The only thing that is bothering me, is that the title of the site is changed to "name". Where can I remove this?
Also on some blog entries my logo in the navbar disappears. Does anyone know what this could be?
If you're basing your blog on the example app (https://github.com/xolvio/md-blog/tree/master/app), the strings used in the app are defined in the internationalization directory (https://github.com/xolvio/md-blog/tree/master/app/i18n). You can edit the en.i18n.json file as you see fit. The site_title property is what you need to edit to change the title of the blog.
Without seeing your blog, I can't evaluate why your logo disappears. Inspect the page to see if it's there but not visible. It's likely a css issue.
I'm getting this error in Chrome when it loads this application I am working on:
Failed to get text for stylesheet 50: No style sheet with given id found
Subsequent page loads repeat the error, but with a different number:
Failed to get text for stylesheet 152: No style sheet with given id found
This only happens in Chrome, and only with this application. There is no stack trace, reference, or any other information about what id is given, what the stylesheet in question is, or what is causing this generally. How can I find what is causing this error and fix it?
I had the same problem. It looks like a bug in Chrome's live-edit CSS/JS. Notice how the number changes on each request.
I fixed it by closing all the files that I had edited in the dev tools 'source' tab and then refreshed the page.
The error went away after I closed all the files in the 'source' tab.
I tried to reproduce it after closing the files, but I can't seem to recreate it, yet.
Here is a picture showing where to find the 'source' tab:
Still present in Chrome 46.0.2490.80 m (64-bit).
Closing sources tabs 'fixed' it.
Fixt it by holding [Ctrl] + [Shift] and refresh the page
Just experienced this today if you have a .css file open in the dev tools. If you close the .css file and reload, the issue does not happen.
Chrome 48.0.2564.109 (64-bit)
I'm having trouble getting my custom error page to work. I have followed the instructions on http://docs.ghost.org/themes/ and added an error.hbs template into the root of my theme. The code inside this template is really simple:
{{!< default}}
<section class="error">
<h1>{{code}}</h1>
<p>{{message}}</p>
</section>
Each time I try to test it by going to a non existent page, the blog shows the default ghost error page every time.
Have I missed anything crucial?
If you are using ghost 0.4.2 I'm sorry this is a bug and would be fixed in 0.5 release
see the bug issue at github
https://github.com/TryGhost/Ghost/issues/2513
Have you restarted Ghost? Whenever you add or remove a theme file you need to restart the application for it to become aware of the changes to your file structure. Edits to files are detected automatically, but new or removed files need this extra step.
. .
I'm trying to set up IIS 7 to use custom error pages, but I'm running into a problem that I can't seem to get around. I've looked nearly everywhere for an answer to this, and have come up empty.
Here's the deal: I open IIS, go into Error Pages (note: this is a classic ASP environment), and open Edit Feature Settings. I set my path type to Execute URL and set my path (for example purposes, let's say it's "/errors/SomeError.asp"). I also set it to "Custom Error Pages."
For the most part, it seems to be okay, but here's where I run into trouble.
I'm sure you've all seen the errors where your page partially loads, and the error appears in the middle of the page. (For example, you'll see your page template, and somewhere in the middle, you'll see your "Error 500 . . . " blah blah blah.)
The error page I created (the "/errors/SomeError.asp" I mention above) is a full page, complete with template and everything.
When an error occurs mid-page, it does not redirect to my custom error page. Instead, the page is "nested" -- that is, the full page appears right in the middle of the problem page -- so it looks like a full page within a full page.
I want it to go to the error page, not have the error page nested within the page.
How do I get around this?
Thanks in advance.
I just answered my own question.
Instead of setting path type to "Execute URL," I set it to "Redirect." Problem solved.
I just uploaded my themantic child theme and am getting a weird error message every time i try to install a plugin
Warning: Cannot modify header information - headers already sent by (output started at /home/content/29/7464729/html/wp-content/themes/coolness/functions.php:126) in /home/content/29/7464729/html/wp-includes/pluggable.php on line 934
Does anybody know what i should do about this?
Check your code with following guide:-
Remove blank line before the opening php statement
Remove blank lines after the closing php statement
Remove irrelevant echo's in your code
More discussions about this issue in WordPress Forum
Solutions and reasons here
More and More in stack overflow please use search box in So before posting qustions