In the past we organized pages inside the page-tree by putting them into pages like "meta" or "submenu". These pages had the option "exclude from speaking url" so their name was not rendered to the url.
Is there any option to do this in TYPO3 9.5 to ignore pages from generating the "slug"?
as example:
WRONG: https: //www.somedomain.tld/metamenu/terms-and-conditions/
RIGHT: https: //www.somedomain. tld/terms-and-conditions/
How to "ignore" the page "metamenu" for automatic-generating the slug?
Best regards
Johannes
It is mandatory for a page to have set a slug and every menulevel will generate another url part. It is not possible to exclude a page - think about how to access this page via url
Here Mathias Schreiber tells a bit about this feature: Feature Demo - Speaking URLs Part 1
The TYPO3 extension "masi" provides this feature, including an upgrade wizard that migrates the realurl tx_realurl_exclude settings.
Have you tried using a Folder instead of a "Page"?
page/page/page
somedomain.tld/metamenu/terms-and-conditions/
page/folder/page
somedomain.tld/terms-and-conditions/
You can leave the parent-page as it is and edit your child-pages. There you can delete parts of the urls in the slug-field.
There's a feature in RealURL for TYPO3 8.7 "Exclude from speaking URL". If set 'domain.com/page-one/' loads 'page-one' and 'domain.com/subpage-of-page-one/' loads 'subpage-of-page-one' with no need of 'page-one' in the URL.
The very same thing can be achieved in TYPO3 9.5 manually editing slugs but you can't set the parent page to be excluded from the URL automatically.
It's a missing feature.
I had the same Problem. Sadly there is no "good" solution as far as i know. But there is a little trick. You can fix this in the database. I deleted all my "slug"-entries in in the database for my pages. Then i wrote in all pages wich should not show in the url in slug "/". This does sadly not work in TYPO3, because the BE allows just one "/" and the second "/" will be changed to "/1". But in the Database you can do it. After you edited the slug for your page metamenu and other to "/", you can go into the upgrade-wizard in the installtools, reset the "generate slugs" task and run this task again. This is sadly the only solution i came up with.
I have a simple Tumblr website blog, upon which I post content.
However since I changed my DNS, the Facebook Object debugger sees really old data for my root url: http://www.kofferbaque.nl/ and for every post (for instance: http://kofferbaque.nl/post/96638253942/moodoid-le-monde-moo) it shows a 404 not found, which is bullshit because the actual content is there.
The full error message: Error parsing input URL, no data was cached, or no data was scraped.
I have tried the following things to fix it:
clear browser cache / cookies / history
using ?fbrefresh=1 after the URL (didn't work)
I've added a FB app_id to the page (made sure the app was in production - added the correct namespaces etc. - also didn't change anything)
Checked out other questions regarding this subject
Rechecked all my meta tags a dozen times
What other options are there to fix this issue?
If you need more info please ask in the comments.
2014-09-08 - Update
When throwing my url into the static debugger https://developers.facebook.com/tools/debug/og/echo?q=http://www.kofferbaque.nl/. The 'net' tab from firebug gives the following response:
<meta http-equiv="refresh" content="0; URL=/tools/debug/og/echo?q=http%3A%2F%2Fwww.kofferbaque.nl%2F&_fb_noscript=1" /><meta http-equiv="X-Frame-Options" content="DENY" />
2014-09-11 - Update
removed duplicate <!DOCTYPE html> declaration
cleanup up <html> start tag (aka - removed IE support temporarily)
I've placed a test blog post to see if it would work, it didn't. Somehow my root url started 'magically' updating itself. Or let's say, it removed the old data - probably due to the fact that I removed the old app it was still refering to. However, it still doesn't see the 'newer' tags correctly.
Still no succes
2014-09-12 - Update
Done:
moving <meta> tags to the top of the <head> element
removed fb:app_id from page + the body script, for it has no purpose.
This appearantly doesn't make any changes. It also appears that tumblr injects lots of script tags at the start of the head element. Maybe that is the reason the Facebook scraper doesn't 'see' the meta tags.
The frustrating bit is that through some other og tag scanner: http://iframely.com/debug?uri=http%3A%2F%2Fkofferbaque.nl%2F, it shows all the correct info.
First, the HTML is not valid. You got the doctype two times (at least on the post page), and there is content before the html tag (script tag and IE conditionals).
This may be the problem, but make sure you put the og-tags together at the beginning of the head section - The debugger only reads part of the page afaik, so make sure the og-tags are in that part. Put all the other og-tags right after "og:site_name".
Btw: ?fbrefresh=1 is not really necessary, you can use ANY parameter - just to create a different url. But the debugger offers a button to refresh the scraping, so it´s useless anyway.
OK, here is a weird one...
Try putting this URL (http://dev.bride.ca/wedding-dresses/index.cfm?page=1&shopRegions=162&GownTypeID=1&maxGownPrice=1000&GownLabelID=12) through the Facebook debugger.
Here, just click this : http://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fdev.bride.ca%2Fwedding-dresses%2Findex.cfm%3Fpage%3D1%26shopRegions%3D162%26GownTypeID%3D1%26maxGownPrice%3D1000%26GownLabelID%3D12
See the weird change?
When it creates a canonical URL which to parse, it takes the very last URL variable (GownLabelID=12) and changes it to "GownLabelID=0"
Actually, it does the same with the previous variable : maxGownPrice=1000 becomes maxGownPrice=0
But it does not do it with all the variables, just those two. And it does not do it to the last two. I swapped the order and moved the last one to the beginning and it still did it to the same variable.
I am out of ideas.. ANYONE??
Thanks in advance! (*) this being on the DEV server, feel free to try different things etc. It is not "live" to consumers or anything..
When it crates a canonical URL which to parse, it takes the very last URL variable (GownLabelID=12) and changes it to "GownLabelID=0"
The scraper does not “create” the canonical URL – it reads them from your page’s OG meta tags.
You are the one that put
<meta property="og:url" content="http://dev.bride.ca/wedding-dresses/index.cfm?
page=1&shopRegions=162&GownTypeID=1&maxGownPrice=0&GownLabelID=0"/>
into the page’s HTML code – and the scraper just follows what you’re telling it.
When I view the page source the meta tags are fine, however when I try to share the website link (the problem is only with frontpage item) on Facebook, the preview points to "Joomla! ..." text.
I have also changed
Changed the global config file (that only ensures all other pages work fine except the frontpage item)
hardcoding the MetaDesc tag in *.php files.
Maybe I'm missing something very basic?
Have you tried removing the Generator meta tag from Joomla? The only meta data tag I know of that starts Joomla! is the generator tag. In Joomla 1.6 onwards you can remove this by adding a line to your template. In 1.5 however you have to edit the following file.
\libraries\joomla\document\html\renderer ~ line 84
As mentioned earlier, the Google problem should be solved by waiting for a while.
Facebook seems to need custom meta tags in order to work properly. There is a thread about it here. Also worthwhile checking out facebook developers section.
Your home website not show metadescription and keyword although you config it in Global Configuration .
Menu manager -->Home is Front Page Blog view.Try insert metadesc and keyword in file
I try using get values from configuration.php.But it not working with 2 parameter MetaDesc, MetaKeys.
Edit file yourwebsite\components\com_content\views\frontpage\view.html.php
$config = & JFactory::getConfig();
$document->setDescription($config->getValue( 'config.MetaDesc'));
Sumary I fix my problem like that,
Edit file yourwebsite\components\com_content\views\frontpage\view.html.php
$document->setMetadata(“keyword abc here”);
$document->setDescription( "Description about your website" );
Hope this help someone have some problem's.My name is vanhien771354
www.nhipcau.us
When someone posts a link on facebook, a script usually scans that link for any images, and displays a quick thumbnail next to the post. For certain URLs though (including mine), FB doesn't seem to pick up anything, despite their being a number of images on that page.
I read up that FB prefers the "image_src" rel tag for the image the user wishes to specify, but this does not generate that thumbnail either for my site.
My url goes directly to the DNS, and is not forwarded, so I don't imagine that could be the problem either.
Does anyone have an idea as to why FB can't generate any thumbnails from my site?
The easiest way is just a link tag:
<link rel="image_src" href="http://stackoverflow.com/images/logo.gif" />
But there are some other things you can add to your site to make it more Social media friendly:
Open Graph Tags
Open Graph tags are tags that you add to the <head> of your website to describe the entity your page represents, whether it is a band, restaurant, blog, or something else.
An Open Graph tag looks like this:
<meta property="og:tag name" content="tag value"/>
If you use Open Graph tags, the following six are required:
og:title - The title of the entity.
og:type - The type of entity. You must select a type from the list of Open Graph types.
og:image - The URL to an image that represents the entity. Images must be at least 50 pixels by 50 pixels. Square images work best, but you are allowed to use images up to three times as wide as they are tall.
og:url - The canonical, permanent URL of the page representing the entity. When you use Open Graph tags, the Like button posts a link to the og:url instead of the URL in the Like button code.
og:site_name - A human-readable name for your site, e.g., "IMDb".
fb:admins or fb:app_id - A comma-separated list of either the Facebook IDs of page administrators or a Facebook Platform application ID. At a minimum, include only your own Facebook ID.
More information on Open Graph tags and details on Administering your page can be found on the Open Graph protocol documentation.
http://developers.facebook.com/docs/reference/plugins/like
I know this question is old, but I recently dealt with the exact same problem and went round and round on it for a couple weeks. Multiple searches on Google turned up a lot of useful information, but most of it was focused on Open Graph tags, which I wasn't interested in using. Turns out my site had multiple issues, but here are some of the basics.
As EightyEight said, make sure your HTML is valid - and the same goes for your javascript and server-side code (PHP, ASP, etc.). I had a small PHP error in a piece of code that was executing as a separate call to the server from the main page. Due to a number of bizarre coincidences, that code was generating a 500 error - but ONLY for IE6 and strict parsing engines like the W3C validator and the Facebook page crawler. The problem didn't appear in modern browsers (Chrome 4, FF 3.5, IE 8, etc) so I didn't see it right away, but older/stricter clients were showing the 500 every time and that was the main reason FB wasn't crawling our page (when everything else seemed to be correct).
Regarding Randy's response, he's correct that Facebook will keep an old cached copy of your page long after you've updated it. FB claims it's only held for 24 hours, but I experienced much longer times than that. FORTUNATELY, FB has released their "URL Linter" tool that will show you a preview of how your page will appear when being shared on FB, and it will force FB to instantly update its cache of your page. This was a lifesaving tool. You can find it at http://developers.facebook.com/tools/lint/
Regarding the URL Linter tool, be aware that each variation of a URL is cached separately on Facebook, so "www.example.com" is not the same as "example.com". Also, unique capitalization is stored as well, so "ExampleOne.com" is not the same as "exampleone.com". (This led to a lot of confusion between my client and myself when it appeared to me that the cache had been updated just fine and the client claimed they weren't seeing the updates. Turns out I was looking at exampleone.com and had used Linter to update the cache, but they were looking at exampleOne.com which I hadn't submitted to Linter. As a result, I ended up submitting quite a few variations of the URL to Linter just to cover the bases.)
WyrdNEXUS's advice to use the image_src link tag is spot-on. This allows you to be sure that FB is scraping the best possible image for your page. There are some varying guidelines out there about what specs the image file should have, but I've successfully used a 128px square image and have seen a 130x97 image make it through as well. Here is Facebook's official documentation from http://developers.facebook.com/docs/reference/plugins/like/:
Images must be at least 50 pixels by 50 pixels. Square images work best, but you are allowed to use images up to three times as wide as they are tall.
Obviously, FB will resize a large image for you, but you'll almost always get better results if you resize it yourself beforehand.
Regarding Mike Cooper's link to the eHow article, avoid using step #1 in that article. It was valid advice when the article was written and when Mike posted the link, but it's now better to use the URL Linter tool for previewing how your page will appear when being shared. By using Linter, you won't cause FB to cache a (potentially) bad copy of the page before you get a chance to tweak it.
Use the facebook lintter available here. http://developers.facebook.com/tools/lint/
This will check your link and re fetch any images. this also clears any old cache.
Or try this - https://developers.facebook.com/tools/debug
To change Title, Description and Image, we need to add some meta tags under head tag.
STEP 1 :
Add meta tags under head tag
<html>
<head>
<meta property="og:url" content="http://www.test.com/" />
<meta property="og:image" content="http://www.test.com/img/fb-logo.png" />
<meta property="og:title" content="Prepaid Phone Cards, low rates for International calls with Lucky Prepay" />
<meta property="og:description" content="Cheap prepaid Phone Cards. Low rates for international calls anywhere in the world." />
NEXT STEP :
Click on below link
https://developers.facebook.com/tools/debug
Add your URL in text box (e.g http://www.test.com/) where you mentioned the tags. Click on DEBUG button.
Its done.
You can verify here https://www.facebook.com/sharer/sharer.php?u=http://www.test.com/
In above url, u = your website link
ENJOY !!!!
try this: http://www.ehow.com/how_4938148_thumbnail-show-up-facebook-share.html
Is the site's HTML valid? Run it through w3c validation service.
Actually, if you've already tried linking that page on Facebook BEFORE adding the "image_src" link, Facebook will keep using the old cached copy and not even see your changes. Try modifying the URL by removing or adding the 'www', or duplicate your page to test it.
I've noticed that Facebook does not take thumbnails from websites if they start with https, is that maybe your case?
had the same problem and figured out that my head closing tag was in the wrong place
Old question but recently I seemed to be running into same issue with thumbnail images from my link not showing in status updates on Facebook. I post for many clients and this is relatively new.
FB doesn't seem to like long URLs anymore — if you use a URL shortener such as goo.gl or bitly.com, the thumbnail from your link/post will appear in your FB update.
Try using something like this:
<link rel="image_src" href="http://yoursite.com/graphics/yourimage.jpg" /link>`
Seems to work just fine on Firefox as long as you use a full path to your image.
Trouble is it get vertically offset downward for some reason. Image is 200 x 200 as recommended somewhere I read.
If you used any plugin for seo then Check 1st your seo plugin settings.Then find out Noindex setting if Enable Media for Noindex then disable it.