• Friday, October 14th, 2011
Category: WordPress
| | Leave a Comment
An expert is a person who has made all the mistakes that can be made in a very narrow field.
— , Quotes of the Day
• Wednesday, March 23rd, 2011
WordPress MU is no longer under active development as a separate product. Its features were rolled into core and released with WordPress 3.0. You can install WordPress and Create A Network instead. It functions generally the same.
WordPress MU, or WordPressµ, is the multi-user version of WordPress. It is ideal for people who want to set up a large network of blogs. WordPress MU is the underlying software that powers the WordPress.com hosted blogging service. WordPress MU is also used by newspapers, magazines, blog networks, universities and large companies running corporate blogging systems behind firewalls.
Using the WordPress multi-user edition, you will be able offer users an opportunity to sign up for a new blog. They will be able to securely manage their templates and settings without affecting any other users. You can have unlimited users with unlimited blogs, and users can have various roles (administrator, editor, author, contributor, subscriber) on each other’s blogs. One or more Site Administrators can perform site-wide management tasks, including adding users and blogs, altering permissions and granting access to themes.
WordPress MU Features
WordPress MU Plugins and Themes are controlled by a central system administrator. Unlike the single-user version of WordPress, individual WPMU bloggers cannot upload their own WordPress Plugins and Themes. The users can only select from the ones made available by the system administrator. Individual themes can be made available to all blogs or just to specific ones.
WordPress Mu Host Benefits
- Ability to create a hosted “community” of users.
- Ability to host thousands of users on one site.
- Opportunity to provide free hosting as an alternative to paid hosting services.
- Ability to limit sign-up to specific email domains if required.
- Various options for adding Plugins and administration features.
- Customization of the administration panels.
- Ability to add WordPress Themes, increasing user choices.
- Ability to control WordPress Themes, limiting user choices per site needs.
- Security precautions and protections in place.
- Easy addition of comment spam protection through Plugins.
WordPress MU User Benefits
While WordPress MU users are blogging with a restricted version of WordPress, able to choose from WordPress Themes and Plugin options as set by the Administrator, there are still a lot of benefits.
- No installation or setup. Enter user name and password and blog.
- A chance to test drive WordPress at little or no risk.
- Choose WordPress Themes that have been tested and are ready for use – no fuss, no muss.
- Part of a community, with potential for community relationships through competition and awareness.
- Comment spam protection built-in.
WordPress MU is designed for hosts to offer hosting of WordPress blogs to individual users. WordPress MU is free, as is the single hosted version of WordPress.
WordPress MU Support and Installation
For information on installing and setting up a WordPress MU site, see Installing WPMU.
For support and information on installing and using WordPress MU, visit the WordPress MU website and WordPress MU Support Forum.
If you are a WordPress MU user click on the Feedback button in your Dashboard. Some help may be found within the WordPress Codex in the articles listed on WPMU or in Donncha’s FAQ.
- There are some special WPMU Plugins and not all WordPress Plugins work with WPMU, see WPMU Plugin Compatibility
- There are WPMU Functions and WPMU Global Variables that should use to interact with WPMU’s multiuser features
- WordPress Plugins and Widgets can be modified to become WPMU Widgets.
- The code can be checked out from the WPMU SVN Repository.
- There is the WPMU IRC Channel for real time help and chat.
- Information is available about how the tables are set up in WPMU Database Description.
For more information, see the Codex Table of Contents for WPMU or the Category:WPMU.
Other Helpful Resources
- WordPress Development Blog – Information on WordPress in General
- Using WordPress MU to Power Multiple Blogs at DevLounge (13DEC07)
- WordPress Mu Magyar Információs oldal (Hungarian)
- Plugins for WordPress MU
- WordPress MU tutorials and how-to articles
Source: http://codex.wordpress.org/WordPress_MU
Category: WordPress
| Leave a Comment
• Wednesday, March 23rd, 2011
If you are using WordPress as a CMS, then you probably want to present your content with multiple languages. Recently, I came across a WordPress blog that presents their content with three different languages, so I decided to investigate the methods and plugins to turn WordPress into a multilingual website, and share my findings with WDB’s readers.
Maintaining a multilingual website is not easy. The best way to present multilingual content to your visitors is to allow them to switch between different languages anytime. So, the plugin needs to take care of this and links different languages’ content together.
Beside linking the content, the URL of the translated content also important. There are two different ways to present your URL:
- You can have the same permalink for the translated content, and add a language flag at the end of the URL (ex: www.domain.com/multi-language-article/?lang=en, www.domain.com/multi-language-article/?lang=es, www.domain.com/multi-language-article/?lang=zh).
- The translated content will have absolutely different URL.
So, how to choose your URL is yet another main consideration before you launch the multilingual website? In SEO point of view, having an absolutely different URL will gain better advantages Later on, we are going to look into 5 different plugins to manage your multilingual WordPress website. These plugins have their pros and cons, so choosing the best plugin that suit your needs in the most important.
1. WPML
In my opinion, WPML is the most powerful WordPress multilingual plugin. WPML has a complete startup guide for new users and its side-wide navigation adds top navigation with drop down menus, breadcrumbs trail navigation and also sidebar navigation. WPML is rather too powerful for a simple multilingual website. You can have a lot of options and configurations through the backend admin menu. Adding a non-support language is not that easy. For example, when I tried to add a language which is not supported by default, I need to go to my MySQL backend and manually add in the SQL queries. Hopefully future version will make this easier.
2. qTranslate
qTranslate is yet another powerful multi languages WordPress plugin. It has advantages over WPML because it allows users to add new languages to the system through the Simplistic Configuration Page. In terms of URL structure, qTranslate provides three modes to make your URLs pretty and SEO friendly:- everywhere compatible ?lang=en, simple and beautiful /en/foo or nice and neat subdomain en.domain.com.
3. ZdMultiLang
You can define multiple languages and translate posts/tags/categories using the interface that will be added to your blog’s administration panel. Adding a new user-defined language is very simple through the admin panel, but there are a couple of important things that you should check before adding a new language. For example, the language code and the language permalink. You can read more about this is the plugin website.
4. Language Switcher WordPress Plugin
Setting up the language switcher plugin to work with your WordPress site does take some work. The official website provides a very comprehensive startup guide which covers installing, theme and plugin modifications, translating and Q & A.
5. xLanguage
xLanguage is a full featured plugin which allows you to blog in different language. It works for blog post, page, tags and categories. xLanguage uses tags to differentiate different languages and serve the content to the user based on their selected language.
Source: http://www.webdesignbooth.com/wordpress-multi-languages-5-plugins-to-built-a-multilingual-website/
Category: Web Page Design, WordPress
| Leave a Comment
• Tuesday, February 08th, 2011
Name
svn switch — Update working copy to a different URL.
Synopsis
svn switch URL[@PEGREV] [PATH]
switch --relocate FROM TO [PATH...]
Description
The first variant of this subcommand (without the --relocate option) updates your working copy to point to a new URL—usually a URL that shares a common ancestor with your working copy, although not necessarily. This is the Subversion way to move a working copy to a new branch. If specified, PEGREV determines in which revision the target is first looked up. See the section called “Traversing Branches” for an in-depth look at switching.
If --force is used, unversioned obstructing paths in the working copy do not automatically cause a failure if the switch attempts to add the same path. If the obstructing path is the same type (file or directory) as the corresponding path in the repository, it becomes versioned but its contents are left untouched in the working copy. This means that an obstructing directory’s unversioned children may also obstruct and become versioned. For files, any content differences between the obstruction and the repository are treated like a local modification to the working copy. All properties from the repository are applied to the obstructing path.
As with most subcommands, you can limit the scope of the switch operation to a particular tree depth using the --depth option. Alternatively, you can use the --set-depth option to set a new “sticky” working copy depth on the switch target. Currently, the depth of a working copy directory can only be increased (telescoped more deeply); you cannot make a directory more shallow.
The --relocate option causes svn switch to do something different: it updates your working copy to point to the same repository directory, only at a different URL (typically because an administrator has moved the repository to another server, or to another URL on the same server).
Source: http://svnbook.red-bean.com/en/1.5/svn.ref.svn.c.switch.html
Category: How-to
| Leave a Comment
• Monday, January 17th, 2011
BlueScreenView scans all your minidump files created during ‘blue screen of death’ crashes, and displays the information about all crashes in one table. For each crash, BlueScreenView displays the minidump filename, the date/time of the crash, the basic crash information displayed in the blue screen (Bug Check Code and 4 parameters), and the details of the driver or module that possibly caused the crash (filename, product name, file description, and file version).
For each crash displayed in the upper pane, you can view the details of the device drivers loaded during the crash in the lower pane. BlueScreenView also mark the drivers that their addresses found in the crash stack, so you can easily locate the suspected drivers that possibly caused the crash.
Source: NirSoft BlueScreenView v1.30
Category: How-to, Software Tools
| | Leave a Comment
• Wednesday, December 01st, 2010
Once you’re sure your site is free from any infected code and content, you can request a malware review.
The malware review is designed for sites that have previously been infected with malicious software. If your site hasn’t been flagged as having malware, but has been removed from Google’s index, or no longer performs as well as it did—perhaps because it violated the Webmaster Guidelines—you should file a reconsideration request instead. You can also use the form to request reconsideration of a site that has been identified in our search results with a “This site may be compromised” warning message. In both cases, you should make sure that your site now complies with the Webmaster Guidelines before submitting the request. However, if your site has been flagged as containing malware, filing a reconsideration request isn’t enough. You must follow the process on this page to request a malware review.
- On the Webmaster Tools Home page, select the site you want.
- Click Diagnostics, and then click Malware.
- Click Request a review.
Google’s automatic systems will scan your website. If no malware is found, we’ll remove the warning from your site. This may take a day or so to happen; you can check the status of your request in Webmaster Tools on the Malware page under Diagnostics.
If you’ve cleaned your site, but the warning is still in place after a couple of days, you may not have found and removed all the problematic content on your site. (Our automatic scanners are far more accurate than humans, and they may discover code that you have missed.) Check Webmaster Tools for a list of URLs with potential problems—but remember that the list contains only a sample of problematic URLs.
Very rarely, it can take up to a day for malware warnings (and links to the malware review request form) to be visible in Webmaster Tools after your search has been flagged in search results. If you don’t see a warning in Webmaster Tools, but your site is flagged, please check back later.
Source: http://www.google.com/support/webmasters/bin/answer.py?answer=168328
Category: How-to, Web Apps
| | Leave a Comment
• Wednesday, December 01st, 2010
This page provides information about identifying, removing, and preventing badware on your website. It does not cover every situation, only the most common cases that we see at StopBadware. Some cases may require further assistance from security professional. You may also find additional information and volunteer assistance in our online community.
We provide this advice as-is and cannot guarantee the results of following it. Like you, we do the best we can.
There are three basic steps to restoring and maintaining a clean website:
- Identifying badware behavior
- Removing the badware behavior
- Preventing future infection
Identifying badware behavior
The first step to keeping your website badware-free is to check for any badware or badware behaviors that may already be on your site.
What to look for
The three most common forms of badware that StopBadware sees on compromised sites are:
Malicious scripts
Malicious scripts are often used to redirect site visitors to a different website and/or load badware from another source. These scripts will often be injected by an attacker into the content of your web pages, or sometimes into other files on your server, such as images and PDFs. Sometimes, instead of injecting the entire script into your web pages, the attacker will only inject a pointer to a .js or other file that the attacker saves in a directory on your web server.
Many malicious scripts use obfuscation to make them more difficult for anti-virus scanners to detect:
Some malicious scripts use names that look like they’re coming from legitimate sites (note the misspelling of “analytics”):
.htaccess redirects
The Apache web server, which is used by many hosting providers, uses a hidden server file called .htaccess to configure certain access settings for directories on the website. Attackers will sometimes modify an existing .htaccess file on your web server or upload new .htaccess files to your web server containing instructions to redirect users to other websites, often ones that lead to badware downloads or fraudulent product sales.
Hidden iframes
An iframe is a section of a web page that loads content from another page or site. Attackers will often inject malicious iframes into a web page or other file on your server. Often, these iframes will be configured so they don’t show up on the web page when someone visits the page, but the malicious content they are loading will still load, hidden from the visitor’s view.
How to look for it
If your site was reported as a badware site by Google, you can use Google’s Webmaster Tools to get more information about what was detected. This includes a sampling of pages on which the badware was detected and, using a Labs feature, possibly even a sample of the bad code that was found on your site. Certain information can also be found on the Google Diagnostics page, which can be found by replacing example.com in the following URL with your own site’s URL: www.google.com/safebrowsing/diagnostic?site=example.com
There exist several free and paid website scanning services on the Internet that can help you zero in on specific badware on your site. There are also tools that you can use on your web server and/or on a downloaded copy of the files from your website to search for specific text. StopBadware does not list or recommend such services, but the volunteers in our online community will be glad to point you to their favorites.
Removing the badware behavior
Once you have located the code that is causing the badware behavior, removing it is often as simple as deleting the offending code from all files in which it appears. Sometimes, it is easier, if you have a clean backup of your site’s contents, to re-upload all of the site’s files, though be careful about overwriting files that may have changed since your last backup. In some cases, the bad content may be stored in one or more database records, in which case restoring a recent backup of the database or manually editing the relevant records may be necessary.
Preventing future infection
Preventing badware on your website requires protecting three things: your site itself, the password(s) used to upload content to the site, and the computer(s) used to upload content to the site. The site itself must be protected because attackers often look for vulnerable software to exploit so they can modify your site’s contents. The passwords are critical because, if they are guessed or stolen, they can be used to modify the site. Finally, computers are important because badware on your computer can steal your password and/or modify the contents that you are uploading.
Protect your site
- Ensure that any software you use (e.g., blogging software like WordPress, third party scripts, etc.) is kept up to date with the latest security fixes, either by you (if you installed the software) or by your hosting provider.
- Remove any scripts, services, or other software that you are no longer using.
- Change any default passwords that come with the software you are using.
- Use appropriate file permissions on your web server.
Protect your password
- Use a strong password and change it occasionally, especially if you have reason to think it has been compromised.
- Tips for choosing and protecting a strong password can be found at this helpful page
Protect your computer
Additional resources
Two members of our online community have guides to cleaning a badware-infected website:
- How to prevent your website from getting hacked & repair a damaged site
- Practical Guide to Dealing With Google’s Malware Warnings
Note: These sites may recommend, advertise, or link to products or services. This does not indicate an endorsement by StopBadware of any of these products or services.
Once your site is clean and protected, be sure to remove it from our partners’ badware lists.
Category: How-to, Web Apps
| | Leave a Comment
• Thursday, November 25th, 2010
This is a Stable Release of PeerBlock. It includes many bugfixes and a few new features over our last PeerBlock 1.0 Stable Release, and should work great on Windows 2000, XP, Vista, and 7 (plus server variants), both 32- and 64-bit versions. New Stable 1.1.x bugfix releases should come out every few months from here on in, but new feature development releases will be PeerBlock 1.1+ Beta Releases.
What’s New?
Here are the most important changes present in this new Stable Release, as compared to our previous Stable Release PeerBlock 1.0 (r181).
- Signed Driver - We now have a signed driver! If you’re using a 64-bit version of Windows Vista or 7, you will no longer need to test-sign the driver, or hit F8 during boot, or anything else. It should all just work!
- iBlocklist Lists - We’ve updated our standard list URLs to point at iblocklist.com lists instead of the original peerguardian.sourceforge.net ones. They are faster, and are much more reliable – no more “Error contacting URL” messages! We will also upgrade your pre-existing lists from sourceforge.net hosted ones to iblocklist.com ones. Also note that the “Gov” list has been removed, since its contents were merged with the “P2P” list long ago.
- Installer Rewrite - Our newest Dev Team member, XhmikosR, has pretty much completely rewritten the installer from scratch. Most importantly, it should actually work now, even during uninstall! (Not that you’ll ever want to uninstall PeerBlock, of course, but just in case…)
- Updated List Manager - Reworked this window a bit, to make it easier to get back to the lists originally presented to you in the Startup Wizard.
- Allowed Connections Displayed - By default, the “Show allowed connections” option will be disabled. (This is due to performance reasons, as the tool will consume considerably more CPU if displaying of allowed connections is enabled.) We are still logging the first 9 allowed packets though, so that you know that we’re actually working!
- Save Settings - We’ve added a “Save” button to the settings panel, so that you can be sure your settings updates have been saved.
- List Verification - After downloading an updated list, we’ll now make sure that the file contains at least one ip-address range before we’ll overwrite your old list. This way you will be protected against your lists being corrupted while downloading them.
Installation
New install? No problem, just download the above .exe file and run it, and it will take care of everything for you . . . even migrating over your old PeerGuardian 2 settings if you had that installed on your machine already.
Upgrading from an older release? No need to uninstall that previous version of PeerBlock before installing PeerBlock 1.1 – you just need to exit any currently-running version, then download and run the installer. You can exit PeerBlock by right-clicking on the little cube/”block” PeerBlock icon in the lower-right corner of your screen, by the clock, and selecting “Exit”.
Other Download Options
If you’d rather not use the Installer based version of PeerBlock, you can instead download a “Portable” .zip version. Those files, along with checksum information for all our files if you’d like to verify that your download hasn’t been corrupted, can be found on our Other Downloads page.
Category: Software Tools
| | Leave a Comment
• Monday, November 01st, 2010
Most likely the portable media player can handle mp4 file format.
Use WinAVI Video Converter to handle iPod, PSP, 3GP and MP4 files.
For mp4 file, the best bet would be convert all size to 320×240 format, most media player support this size. If keeping the original size like 720×480 (for DVD size), PC can play it, but media player might reject it.
Category: How-to, Video Tools
| | Leave a Comment
• Friday, October 29th, 2010
Type in is:unread in the search box.
Category: Email, How-to
| | Leave a Comment
