When I try to validate my rss feed, I get this result (with w3c feed validator)
This feed does not validate.
line 1, column 39: Undefined root element: status [help]
<?xml version="1.0" encoding="UTF-8" ?><status>Service unavailable.</status>
But my feed does NOT contain that status tag. I have no idea where that is coming from?
This is the link to the feed: https://www.vrmodelphotography.com/feed/ I did a search on "status" and I did not receive any hits ...
I do have a background in IT, but it's been a few years and maybe this is a stupid question ... but I can't find any resources on it in google ... and I'm desperate at this point ...
I found it!
So for future reference, if anybody has the same problem ... I had the plugin "under construction" activated. This plugin allows me to work on my website and showing me the design, menu, ... while the rest of the world just sees an under construction page.
It appears as if this plugin was a bit too ambitious and also shut down the RSS feed.
Related
I'm trying to support a CQ5 (5.5) installation developed by an outside firm for my company.
It appears that my company wanted a pretty 404 page that looked like the rest of the site, and using the custom Sling 404.jsp error handler to redirect to a regular page that merely says "Page Not Found" was the easiest way to do it. The problem is that the 404 page actually returns a 200 status code since it really is just a regular content page that bears a "Not Found" message on it.
This is causing us problems with Google and the GoogleBot, since Google believes all the old search links to now non-existent pages are still valid (200 status code).
Is there any way to configure CQ to return the appropriate 404 status code for the "not found" HTML page that we display? When I am in the CQ Author mode editing the page, I find nothing in page properties or in components that could be added to the page.
Any help would be appreciated, as CQ is not exactly my area of expertise.
You'll have to overlay /libs/sling/servlet/errorhandler/404.jsp file in order to do so - copy it to /apps/sling/servlet/errorhandler/404.jsp and change according to your specification.
And if you are looking specifically into setting appropriate response status code - you can do it by setting respective response property:
response.setStatus(404);
UPDATE: instead of redirecting to the page_not_found.html you might want to include it to the 404.jsp after setting response status:
<sling:include path="path/page_not_found.html" />
You can set the response code fairly easily with this sort of code: response.setStatus(SlingHttpServletResponse.SC_NOT_FOUND);
So for example, a quick-and-dirty implementation on your page_not_found.jsp would be as follows:
<%
response.setStatus(SlingHttpServletResponse.SC_NOT_FOUND);
%>
(or a longer-term/better implementation would be to set it via a tag and a tag library to avoid scriptlets)
If your page_not_found.html page is a static HTML page and not rendered via a jsp, you may need to change your 404.jsp so it redirects to a page that is rendered via a jsp for this approach to work. The status code is set by the server rendering the response. It is not something intrinsic in the HTML itself, so you won't be able to set this in a regular, static HTML page. Something must be done on the server to set this status code. Also see How to Return Specific HTTP Status Code in a Plain HTML Page
I'm using Plone 4.2. I had the need to manage imagemaps in my application so I installed the following product: http://pypi.python.org/pypi/zopyx.tinymceplugins.imgmap. This product uses TinyMCE to edit the images and add links to them.
After installing this product, I noticed that I am now unable to view my TinyMCE controls while editing a content type. Looking at my browser's error console, I notice that all my *.kss cannot be read. This is the error that is displayed for all *.kss files:
Error: The stylesheet http://localhost:8082/plone/portal_kss/My%20CMS%20theme/++resource++tinymce.kss/tinymce.kss was not loaded because its MIME type, "text/plain", is not "text/css".
Source File: http://localhost:8082/plone/folder-test/image-maps-test/page-with-imagemap/edit
Line: 0
I do not understand why there should be error regarding the MIME type. Anyone has a clue on how to fix this?
Additionally, I get the following:
GET http://localhost:8082/plone/portal_javascripts/My%20CMS%20theme/plugins/imgmap/editor_plugin.js 500 (Internal Server Error)
Just to answer my own question:
I opened the product's skins.xml file
(i.e. zopyx.tinymceplugins.imgmap-0.3.1/zopyx/tinymceplugins/imgmap/profiles/default/skins.xml)
This is how it looks like:
<?xml version="1.0"?>
<object name="portal_skins" allow_any="False" cookie_persistence="False">
<object name="zopyx_tinymceplugins_imgmap"
meta_type="Filesystem Directory View"
directory="zopyx.tinymceplugins.imgmap:skins/zopyx_tinymceplugins_imgmap"/>
<skin-path name="Plone Default">
<layer name="zopyx_tinymceplugins_imgmap"
insert-after="custom"/>
</skin-path>
<skin-path name="Sunburst Theme">
<layer name="zopyx_tinymceplugins_imgmap"
insert-after="custom"/>
</skin-path>
</object>
It appears that the product has been geared towards specific themes.
Now, my application has a custom theme i.e. MyCustomTheme. When I inspect my portal_skins
Site > Zope Management Interface > portal_skins > properties
I notice that indeed the "Sunburst Theme" has included the zopyx_tinymceplugins_imgmap skin layer in the 'Plone Default' and 'Sunburst Theme', but NOT in my 'MyCustomTheme'. It has added it right after the custom layer.
So I go ahead and manually add zopyx_tinymceplugins_imgmap in MyCustomTheme, just immediately after the custom layer.
This manages to fix it, and I can now view my TinyMCE controls. I believe there must be a better way to have it work.
Hope this helps someone in future.
UPDATE: See this for a better solution.
I'm attempting to add a LinkedIn Share button to our content-driven website. I've generated the embed code using the button builder, but whenever I try to actually use the button, I get a generic error:
There was a problem performing this action, please try again later.
It's been doing this for several days (since I first added the code), so I don't know if the error is on the LinkedIn side or mine. Is there any way to get a more specific error message? The code they provide is just a script tag that you paste in:
<script src="http://platform.linkedin.com/in.js" type="text/javascript"></script>
<script type="IN/Share"></script>
Unfortunately LinkedIn's "support" forums are limited to the various API's; there's nowhere available to submit a question regarding the build-a-button functionality. I'm hoping someone else has used this function and can point me in the right direction.
Most likely the page you are trying to share is not web accessible (local, under htaccess password or something). It looks to me like LinkedIn tries to actually look at the page you are sharing, and if it can't reach it, it gives you this message.
Most likely the url which you are sharing is not encoded, try encoding that, also follow this article for more.
The easiest way to ensure the linkedin share button works properly, is to use
<!DOCTYPE html>
instead of other alternatives.
look at the data-url attrbute. Remove the "http://" and only use "www." for your website url. That fixed my issue at least.
I found this way for validate in xhtml:
< !DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
< script src="http://platform.linkedin.com/in.js" type="text/javascript">< /script>
< div id="linkedin">< /div>
< script type="text/javascript">
var po2 = document.createElement('script');
po2.type = 'IN/MemberProfile';
po2.setAttribute("data-id","http://www.linkedin.com/pub/luca-di-lenardo/11/4b7/3b8");
po2.setAttribute("data-format","hover");
po2.setAttribute("data-text","Luca Di Lenardo");
document.getElementById("linkedin").appendChild(po2);
< /script>
Remove the white space and it works!
If anyone is getting this error, and cannot figure out why, I recommend checking the URL of the page you're sharing with: LinkedIn Post Inspector.
So, for instance, if I were to check out how wikipedia.org looks when shared, I would visit and enter that URL, like so...
https://www.linkedin.com/post-inspector/inspect/https:%2F%2Fwww.wikipedia.org%2F
And I see...
But there's a ton of information here, showing how everything is parsed, from the description to the title to the image selection for thumbnail display...
Warning: Add an og:image tag to the page to have control over the content's image on LinkedIn.
Title: Wikipedia
Type: Article
Image: No image found
Description: Wikipedia is a free online encyclopedia, created and edited by volunteers around the world and hosted by the Wikimedia Foundation.
Author: No author found
Publish date: 6/1/2020, 6:39:59 AM
They even give you instructions on how to fix your page! Hey, got some advice for Wikipedia.org here!
Provide a metadata tag for the og:image in the page's head section. For example:
<meta name="image" property="og:image" content="[Image URL here]">
I am stuck on this. My project is to do this..This week you will be creating a theme for a web development company.
* You can use http://www.1kbgrid.com/ for a base design.
* Come up with a color scheme that will match this logo.
* Decide what your top links should be. Create an RSS feed for these top pages.
* Create a report that states the scope of the project (why you are doing it), the top level pages, why you picked the color scheme,etc.
ok I have done and rss thing and this is what it looks like
<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0">
<channel>
<title>Web design software</title>
<link></link>
<description>Has different soft ware and prices.</description>
<item>
<title>Adobe Dreamweaver</title>
<link>http://shopping.yahoo.com/search?p=web%20design</link>
<description>This tells you how much it cost and what it is
for.</description>
</item>
<item>
<title>Frontpage 2003 upgrade</title>
<link>
http://www.softwaremedia.com/microsoft/frontpage/frontpage-
2003-upgrade.html?ovchn=PGR&ovcrn=39202323&ovtac=CMP&ovcpn=frontpage-2003---upgrade</link>
<description>THis is to help build a better web
site.</description>
</item>
<item>
<title>WebPlus X4 Website Maker Mini Box</title>
<link>
http://accessories.us.dell.com/sna/productdetail.aspx?sku=A3310055&cs=04&c=us&l=en&dgc=SS&cid=52102&lid=1342490</link>
<description>It helps you to make websites</description>
</item>
</channel>
</rss>
what i am stuck on is how to decide what my top link should be.Create an RSS feed for those top pages. Ok the question is am I suppose to link the rss feed or if that is even possible. I am totally lost on this question. Thank you for ready this.
You generally link to RSS documents from your main site by using the <link> tag. It should look something like this
<link rel="alternate" type="application/rss+xml" title="Top Web design software Feed" href="http://LINKTOMYRSSFILE" />
If you site is a dynamic site, you'll need to replace LINKTOMYRSSFILE with the link to the file that generates your RSS. If it's a static file, just save this file in your server and point it to that.
Also, your main channel link should point to the link of the page that displays all this content.
EDIT
First off, you should use the W3C service to validate your feed. They point out what's wrong/best practices and tells you how you can fix them (use the help link next to the error)
Make sure the empty <link></link> tag contains a url to your site
To answer your questions in the comments
Missing atom:link with rel="self"
According to the RSS Advisory Board's
Best Practices Profile, identifying a
feed's URL within the feed makes it
more portable, self-contained, and
easier to cache. For these reasons, a
feed should contain an atom:link used
for this purpose.
via : http://validator.w3.org/feed/docs/warning/MissingAtomSelfLink.html
You can fix this by changing your <rss> tag to
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
And having the following above items
<atom:link href="http://LINKTOFEED" rel="self" type="application/rss+xml"/>
Line 12, column 2: item should contain a guid element
It's recommended that you provide the
guid, and if possible make it a
permalink. This enables aggregators to
not repeat items, even if there have
been editing changes.
A frequently asked question about
s is how do they compare to
s. Aren't they the same thing?
Yes, in some content systems, and no
in others. In some systems, is
a permalink to a weblog item. However,
in other systems, each is a
synopsis of a longer article,
points to the article, and is
the permalink to the weblog entry.
So in your case adding the following to each of your items will fix it
<guid isPermaLink="false">LINKTOSOFTWARE</guid>
Replace LINKTOSOFTWARE with the links in your <link></link> tags.
I corrected your mistakes and your feed validates fine. You just need to fix these errors.
You can follow this tutorial on how to add RSS feeds to your pages : https://developer.mozilla.org/en/RSS/Getting_Started/Syndicating
It's as simple as adding an HTML tag into your page.
Hey im wondering why I am receiving the following error in my rss feed
"This XML file does not appear to have any style information associated with it. The document tree is shown below."
from a bit of research ive done this is becuase I dont have a stylesheet attached. But I have done plenty of RSS Feeds before and normally they pick up the default look and feel as below
http://www.tbray.org/ongoing/ongoing.atom
I am just wondering why this one is giving the above error ?
Most likely, the content-type of your feed is not correct, so IE is treating it as raw XML.
What is the URL of your feed? What browser are you using?
the tbray.org URL returns a
Content-Type: application/atom+xml
What is the content-type header returned by your misbehaving feed?
('wget --save-headers ...' may be useful)
my guess is that you need to make sure you declare your namespaces.
Take tim bray's feed and save it locally as test.htm. bring it up in firefox and it will show nicely. now if you remove a namespace in that's being used like :thr the content will disappear. if you remove the base namespace you'll just get plain text.