I have an existing application in epsocrm in which all pages are ready and that all pages have the company logo.
but I have an issue in the login page. the login page has the company logo exactly right side which I want to set in the center.
the example of my login page is given below
I am stuck with finding the solution of this problem. but failed to find
can anybody help me with this.
You just need css like this:
#login .logo-container {
margin: 10px auto;
}
Related
i have on my theme the Customer login/registration button as bellow.
my issue is that on selection of the button it forward me to a page that does not exist. how can i update this button destination page to point to the correct login/registration page?
thanks
after a lot of search i notice that on woocommerce settings there was the account but the login account page. i have update it and the issue is resolved.
thanks
Google+ offer a comments option for websites. They also offer a comments counter like so:
When implementing this, it simply outputs "xx comments". This outputs as an iframe with styling stripped out. I want to keep the styling of the rest of my site, and also want to remove the word "comments" only to show the comment number. Is there an easy way to do this?
There is no way to style the content of an iframe, but you can crop the visible text inside using CSS: iframe { width: 14px; }
I'd like to disable the box that appear when the user hover +1 button I've placed on my site. Also I'd like to disable the box that pops out when the action is made.
Is this possible to do? I can't find any details in the documentation.
Very similar question: Facebook Like Button - how to disable Comment pop up?
Unfortunately, the hover bubble is a feature of the +1 button, as it provides a user with additional information about what they are recommending. At this time, it is not possible to remove them. But you can feel free to make the feature request in our Issue Tracker, which you can find at http://developers.google.com/+/support.
I'd also like to know the proper answer to this! Their data-recommendations="false" attribute currently does nothing. The best I have currently found is a CSS solution to hide the table that is displayed on hover:
table.gc-bubbleDefault.pls-container {
display: none !important;
}
Without using the SharePoint Designer or Visual Studio, is there a way to move the Default Search box to Footer of a page or to a specific custom div tag?
I have found CSS that will allow me to move it to the top of the page however it does not work well when trying to move it to the footer.
This is the CSS that will move it to the top of the page:
.s4-search
{
TOP: 10px;
RIGHT: 400px! important;
POSITION: fixed;
}
There is a div-class called SRSB which you could use to reposition the item. Either by using CSS and using absolute position or similar, or alternatively you could use jQuery to reposition or move it to a different div on the page.
See Difference between div id and div class for using CSS & ID and for moving the elment http://api.jquery.com/category/manipulation/
If you have access to the Master Page Gallery through the browser, you can edit the master page to move the PlaceHolderSearchArea content placeholder.
Go to your site's home page.
Site Actions > Site Settings
On the Site Settings page, click "Master pages and page layouts" under Galleries.
Download your master page (probably v4.master).
Find the [asp:ContentPlaceHolder id="PlaceHolderSearchArea"] tag. Move this where you would like it on the page.
Save and upload back to the Master Pages and Page Layouts Gallery. Check in, publish, and approve.
I highly recommend you not edit the out-of-the-box master pages (like v4.master)--instead copy it to create a custom master page. I won't go into those details here.
As spiders will generally not execute javascript i am thinking of taking one of the options below in order to successfully get them to index the content of a website that requires age verification.
My preferred solution:
Checking for a cookie 'ageverification'. If it does not exist, add some javascript to
redirect the user to ~/verifyage.aspx which will add the required cookie and redirect the user to their previous page.
Another solution:
As above, but do not redirect the user. Instead, if the cookie doesnt exist, draw the age verification form 'over the top' of the existing page.
Another solution:
Add a 'Yes I am over 18' anchor link that a crawler can follow. I am slightly skeptical over the legality of this.
Any insight or ideas greatly appreciated.
What I do - I store age verification in session data. If the session variable does not exist, the server appends a div to the end of the body (after the footer) with the click to verify or click to exit. I use CSS to have it cover the content.
For the css - I use:
display: block; width: 100%; height: 100%; position: fixed; top: 0px; left: 0px; z-index: 9999;
That causes the div the cover all other content in a graphical browser even though it is placed at the very end of the body.
For users without JS enabled, the "Enter" link points to a web page that sets the session variable and returns the user to the page they requested. That results in two page loads of the browser for them to get to the content they want which is not ideal, but it is the only way to do it for non JS enabled browsers.
For JS enabled browsers, a small JavaScript is attached to the page that will change the "Enter" link href link to # and attach a very basic function to the click event, so that clicking on Enter triggers the use XMLHttpRequest to tell the server the person clicked "Enter". The server then updates the session and responds to the XMLHttpRequest with a 200 OK response, triggering the JavaScript to hide the age verification div covering the content. Thus the session is updated so the server knows the user verified the age and the user gets to see the content they wanted with no page reloading in the browser, a much better user experience.
The age verification thus works without JavaScript by sending the user to the verify page the stateless way or in a much friendlier way with JavaScript.
When a search spider crawls the site, it gets the age verification div on every page because a spider will not have the necessary session variable set, but since the div is at the very end of the html body the spider still indexes the real content first.
You've got a real problem either way.
If you let the crawler onto the age-verified portion of your site, then it has that content in its index. Which means it will present snippets of that to users who search for things. Who haven't been through your age verification. In the case of Google, this means users actually have access to the entire body of content you were putting behind the verifywall without going through your screener - they can pull it from the Google cache!
No-win situation, sorry. Either have age-verified content or SEO, not both. Even if you somehow tell the search engine not to spit out your content, the mere fact that your URL shows up in search results tells people about your site's (restricted) contents.
Additionally, about your JavaScript idea: this means that users who have JavaScript disabled would get the content without even knowing that there should have been a click-through. And if you display a banner on top, that means that you sent the objectionable content to their computer before they accepted. Which means it's in their browser cache. Or they could just hack out your banner and have at whatever it is you were covering up without clicking 'OK'.
I don't know what it is your website does, but I really suggest forcing users to POST a form to you before they're allowed to view anything mature. Store their acceptance status in a session variable. That's not fakeable. Don't let the search engine in unless it's old enough, too, or you have some strong way to limit what it does with what it sees AND strong information about your own liability.