Copying a YouTube Video to Another YouTube Account

I asked my students to create a YouTube video and create annotations (like sticky notes on the video) by editing their video within YouTube. Problem is, apparently on their GAFE (Google Apps for Education) account the option to add annotations was not working. This necessitated that we copy the videos to personal YouTube account.

Step 1:

Go to http://YouTube.com and go to the video manager

Step 2: 

Check the checkbox next to the video

Step 3: 

From the actions menu choose creative commons

Step 4:

Go to the video. Right click on the video to “copy the video URL”

Step 5:

Log out or open an incognito window (Chrome – command+shift+n)

Step 6:

Log into other YouTube account

Step 7:

Paste the URL of the video into the address bar (ie: go to the video logged in under new account)

Step 8:

Under the video is the option to “remix this video.” Note this only shows up if the video is under a creative commons license.

Step 9:

At the top left NAME the video something meaningful.

Note: you can use the Youtube.com/editor to actually edit this video, add music or text if you desire. If just wanting to make a copy, simply rename and publish.

Step 10:

Publish


Now the video is COPIED to the new YouTube account.

Binary Details’ to check the supported GALAXY Specials options

The registered binaries do not meet the category conditions for GALAXY Specials. The GALAXY Specials category can be selected only if at least one binary supports GALAXY Specials. You can go to ‘Binary>Advanced Mode>Binary Details’ to check the supported GALAXY Specials options.

Recently Samsung seller office has done some changes, if you simply upload APK like Google play store it will throw error,

"The registered binaries do not meet the category conditions for GALAXY Specials. The GALAXY Specials category can be selected only if at least one binary supports GALAXY Specials. You can go to ‘Binary>Advanced Mode>Binary Details’ to check the supported GALAXY Specials options."

There is no option to disable Galaxy specials in seller office, so the simple and easy way to fix this problem is just add a permission in your manifest file i.e,

<uses-permission android:name="com.samsung.android.providers.context.permission.WRITE_USE_APP_FEATURE_SURVEY"/>

Thats all, now export your APK in release mode and upload it in Samsung seller office, a confirmation message appears, just confirm it.

Now APK will be successfully uploaded to Samsung app store.

حل cgi-sys/defaultwebpage.cgi

Fix defaultwebpage redirection caching

Add the following to to /usr/local/apache/htdocs/index.html

Code:

<meta http-equiv="Pragma" content="no-cache" />

Ideally a better solution would be to modify either httpd.conf or the local .htaccess file such that this header would be sent as a header, but at least sending it as an http-equiv would be better than what we have now.

Problem:

When a domain isn't properly configured, the document in /usr/local/apache/htdocs/index.html redirects the browser to /cgi-sys/defaultwebpage.cgi -- which itself is a pretty bad idea to begin with... but even if you like that, what's really problematic is that this redirection is cached by the browser for that session.

This means that when the domain is fixed (often done immediately in response to seeing that page), the user still can't see the correct page content because the redirection to defaultwebpage.cgi is cached client-side. So when the user types in the site URL, it immediately redirects to defaultwebpage.cgi without checking the server for an updated homepage.

The typical user response in this type of situation is to hit "reload" on the browser to get an updated page -- and browsers are programmed to skip this session cache when a reload is requested. But the problem here is that the page that gets reloaded is defaultwebpage.cgi rather than the homepage URL -- remember that the homepage URL immediately redirects to defaultwebpage.cgi, so you can't hit "reload" before the redirect happens.

The only solution is to close down all browser windows or manually clear the page cache, neither of which is something that the average shared hosting user would even think to try. The result is a lot of needless confusion due to a somewhat poorly thought-out design.

And this is absolutely trivial to fix. Just instruct the browser to not cache the redirect page, and you're done.

Blank page after login to phpMyAdmin

The solution is simple for most of you...

go to WHM > Home > Account Information > List Accounts

Find the relevant account and press on the [+] to expand the action panel for this account.

Check the "[v] Synchronize MySQL password".

Add a new password and press on "Change".

If "Synchronize MySQL password" is missing then I guess it is automatically update the MySQL password with the new cPanel password.