I am going on making a Drupal site matches with my requirement. A requirement describes that on each node, such as Blog or Forum, except publisher's name and published date below the node's title, should show the user's thumbnail (similar to avatar in Facebook or Twitter) too.
I thing there is an existing module for this requirement. but I couldn't find it.
Could you tell me how to do this? some guideline or link to an example? it would be nice if you can tell me the module that is able to do this thing.
you wany to enable picture support: http://drupal.org/node/22271
and in addition, you probaly want to change the theme to call
theme('user_picture', $account);
where you want to display the picture (where $account is the account object of the user that is posting the node/comment)
the corresponding template file is user-picture.tpl.php
Related
We are using kentico 9 at work for our website.
You can subscribe to our newsletter using a "box" which is integrated all the way down on our homepage.
However, I would like to have the opportunity to share a direct subscription link on social media so people can click on it and subscribe to the newsletter.
Now, I have to invite people to go on our website and to go down the page to subscribe which is inconvenient (nobody is going to do this).
I can't find a way to get a direct link (I'm not a developer).
Does anybody know how I could do it ?
Thanks in advance ! :D
Anne
If someone want to subscribe to newsletter, he/she must provide you with email address and I'm not sure that can be done with direct link, because you are not aware of user email address (your target group is unknown group from social media).
You can set up anchor in 'subscribe to newsletter' link, which will automatically scroll down your page to box at the bottom, but I don't think that is the best solution. Maybe, to create a new content page, with only purpose to subscribe users to newsletter (have some introduction text, and widget for 'newsletter' where users can subscribe). I don't know is that what you are looking for, but it is nicer solution then asking people to scroll down and subscribe to newsletter.
Best regards,
Dragoljub
My suggestion would be to create a specific landing page with that signup form on it. This way you can have a link you share in social media that takes them directly to that page and allows them to put in their info (first, last and email) and sign up for that specific newsletter. This way it's a specific call to action on that page and allows for the user to only do one thing.
I'd like to place a Schema.org Organization item on my website.
Should I place the JSON-LD only on the contact page or can I add it to every page of the website? What is the best solution?
With Schema.org, you would typically provide structured data about what is relevant to the current page.
Assuming that it’s the website of the organization, you could specify your Organization as value for these properties:
publisher
(for WebSite, for every WebPage)
about and mainEntity
(for WebSite, for the WebPage on the homepage, for the AboutPage)
author
(for Article, BlogPosting etc.)
(There are more properties, of course. Simply check the type pages for properties that have Organization, or the parent type Thing, as "Expected Type".)
Note that you don’t have to repeat the data, you could simply refer to it instead. Then it would make sense to provide the full data on the page that is given as url of the Organization, so typically the homepage.
According to Google, Organization Schema should be on only 1 page of a website (usually the homepage of contact page).
Source: https://www.searchenginejournal.com/google-do-not-put-organization-schema-markup-on-every-page/289981/
Working on log analysis, I found a string with odd syntax and contents, by parsing page field of web log (a webshell?):
/campaign/(f(2ewt_ygmarlagti7sw4tvhj0zk17klgxnhnk1aawgtixm5x-2qmvsvouolvaffrhitumf4wnk496p2dbzmkc3ywfloksiixdtrlawmt78f_mg-45kdzzpdlnogeishkcgtohttp://www.facebook.com/externalhit_uatext.phptelf6gqmu2ia0i1j5lfgmcvw1))/home/index
Could someone guide me how to decode this string and find a clue ? Also why is the following:
http://www.facebook.com/externalhit_uatext.php
included in the string?
I am quoting https://www.facebook.com/externalhit_uatext.php
Facebook allows its users to send links to interesting web content to other Facebook users. Part of how this works on the Facebook system involves the temporary display of certain images or details related to the web content, such as the title of the web page or the embed tag of a video. Our system retrieves this information only after a user provides us with a link. You may have found this page because a Facebook user sent a link from your website to other Facebook users. If you have any questions or concerns about any links or content sent by one of our users, please contact us at legal#facebook.com.
My guess is that someone posted a link to your website to Facebook and someone clicked on that link (visited your website through that link). The (probably) encoded stuff seem a bit random though. If I were you I would either post a link from my website on Facebook, click on it and see if I get something similar. If it doesn't look like that, I would contact legal#facebook.com to clarify whether it is linked to them.
Using Liferay 6.2, I try to workaround to set a specific layout for the Terms of use, shown after an user registered to the portal, and also Verify Email Address page after the user clicked "Agree" under URL /c/portal/....
I would like to have these pages showing with a look and feel I created. For example, I have created a layout called "1_column_white" in the theme I am using for this site and would like to assign to these pages (Terms of use and Verify Email Address). I did try to overwrite property in portal.properties but there is nothing come up.
Please kindly give me an advice.
Regards,
Create a Liferay hook as explained here to modify /portal-trunk/portal-web/docroot/html/portal/terms_of_use.jsp file as per your requirement.
The tool I'm building needs pull data from IBM Connections Ideation Blogs. I therefore use the Connections API with basic authentication to read Blog Entries. This goes well until the description contains images. When I ask the API to provide media resources for the blog, it does not show any entries of the /BLOGS_UPLOADED_IMAGES location - the one containing images uploaded through the blog's richtext editor. The user I use in my API call is the same user who created blog entries and uploaded pictures.
However the API call DOES contain images I publish using the API and a POST request to the blog's media entry collection. This is where the next problem appears. Those Atom entries for images contain various links, one of them with a ref="enclosure", of which the API documentation (link) tells me to "Use the web address in the href attribute to obtain the binary content of the file". However, my calls to this adress are always answered with 404 response code.
Another url in the Atom entry (this time of the element) is described by the same documentation (see link above) as: "Provides access the document's media. The following operation is supported: GET: Use the web address to obtain the media." When I make a call to this url, as always with basic authentication credentials attached, the response contains the html of the login form of Connections, so API authentication does not seem to be supported on this url. This is only the case for non-public communities, which require authentication, of course, if the picture is publicly availabe all works just fine.
Am I missing something out? Is there another way to retrieve the actual image from a blog's media entry through the API? Are manually uploaded pictures never contained in the media entries result or is this a bug?
It now magically works using the link with ref="enclosure" from the atom entry. I might have gotten something wrong with authentication I guess (although I'm not actually realizing what I'm doing different now than I did before).
Problem remaining: Pictures uploaded through the rich-text editor in the folder /BLOGS_UPLOADED_IMAGES do not appear in the media feed of the blog.