Foodle: How to insert logo in the Header for the foodle theme.

-
We have to edit a css file found in the Fooodle folder viz.. social_network.css 

If you have a logo (logo.jnpor logo.gif or logo.png) in your Foodle directory then then add the following css mark-up to social_network.css

#header, #header-home{
background-color:#3B5998 url(logo.jpg) no-repeat left top; 
margin-top: 0px;
height: 200px; 
border:1px solid #526ea6;
border-bottom:#fff 1px solid;
}


Save the css file and then check.

Comments

Post a Comment

Popular posts from this blog

ACTION_FAILED:OU_INVALID: Solution for GoogleApps bulk user upload issue, username@domainname.com:ACTION_FAILED:OU_INVALID. This error is because you have not specified the Org Unit Path properly.

-
To upload bulk users to GoogleApps, you will require a following required fileds, other fields are optional:-               First Name               Last Name               Email Address               Password               Org Unit Path What is 'Org Unit Path'? This field was not their earlier. This is the path to place users in an organizational unit. For example if your domain has different organization unit like , staff, students, guest etc.. then the Org Unit Path would be just :  /
Read more

Moodle OAuth 2. This account is pending email confirmation! Solved

-
Image
If you happen to come across this ' This account is pending email confirmation' message while using Google OAuth2 in Moodle. Try these following solutions: Solution 1. First login to you Moodle and Admin. Go to Site Administration --> Server--> oAuth 2 Services go to setting. Make sure the Require email verification is NOT checked. Solution 2: Login to Moodle database and delete the particular user #mysql -uroot -p\ mysql> use moodledb; mysql> SELECT * FROM mdl_auth_oauth2_linked_login WHERE email='sjamso@moodle.edu.bt'; mysql>D ELETE FROM mdl_auth_oauth2_linked_login WHERE email='sjamso@moodle.edu.bt';
Read more

[Solved][Proxmox update] Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/buster/InRelease 401 Unauthorized [IP: 51.79.159.216 443]

-
Here is the solution to the Proxmox update and upgrade issue. Error :  E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/buster/InRelease  401  Unauthorized [IP: 51.79.159.216 443] Error:  root@moni:~# # apt update Hit:1 http://security.debian.org buster/updates InRelease Hit:2 http://ftp.debian.org/debian buster InRelease            Hit:3 http://ftp.debian.org/debian buster-updates InRelease    Err:4 https://enterprise.proxmox.com/debian/pve buster InRelease 401  Unauthorized [IP: 51.79.159.216 443] Reading package lists... Done            | E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/buster/InRelease  401  Unauthorized [IP: 51.79.159.216 443] E: The repository 'https://enterprise.proxmox.com/debian/pve buster InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-s...
Read more