Tuesday, April 30, 2013

how to export large wordpress xml files

my xml file on my ex shitty shared hosting company came to 60MB.

The problem wordpress,blogger does not allow files more then 17mb,10mb

Even other hosting companies will not allow hosting above 20 mb .
You cannot cut xml  files into smaller pieces as it screws up the code .

The only solution is to install wordpress on your own computer and then save the files into smaller parts . OR same the xml files into smaller parts before you leave your ex shitty shared hosting company

So if you are like me and a)did not have time to break them into smaller parts b)was so angry with the hosting company that you did not save them into smaller xml

1) Download xampp from apache friends 97 mb installer

install it on your windows ,linux computer

Open the xampp panel
start apache
start mysql

follow the steps how to download and install wordpress

put it into the htdocs folder. Click config (next to apache ) in the xampp panel
click browse apache

Open the htdocs folder and install it there
after you have installed wordpress on your local computer

Then Click config (next to apache ) in the xampp panel
click php (php.ini)
change those in BOLD to the size you want

; Maximum allowed size for uploaded files.
; http://php.net/upload-max-filesize
upload_max_filesize = 2M

Sorry, there has been an error.
File is empty. Please upload something more substantial. This error could also be caused by uploads being disabled in your php.ini or by post_max_size being defined as smaller than upload_max_filesize in php.ini.

; Maximum size of POST data that PHP will accept.
; Its value may be 0 to disable the limit. It is ignored if POST data reading
; is disabled through enable_post_data_reading.
; http://php.net/post-max-size
post_max_size = 8M

Warning: POST Content-Length of 46980048 bytes exceeds the limit of 8388608 bytes in Unknown on line 0

; Maximum amount of memory a script may consume (128MB)
; http://php.net/memory-limit
memory_limit = 128M

I hope you also restarted your webserver after changing
these values in php.ini??



log into wordpress 
click tools -> import 
install the wordpress install plugin
now you will see 2mb changed to 60 MB or the number you want . 

Saturday, April 27, 2013

new how much do you love spam on facebook

the spam link could be a  blogspot or


Find What Your Birthday Say about Your Pr0fessi0n? at http://ch0ose-your-pr0fession.blogspot.be/

How Much Your Patrner Loves You? find Here->> http://tiny.cc/6mncww

Which Profession Suits you By Your Birthdate? finad at -->> http://check-your-profession.blogspot.no/

Which Pr0fessi0n Suits you By Your Birthdate? Find at -->> http://bit.ly/151WZoe

Find Out H0w Much Your Lover L0ves Y0u?->> hxtp://tiny.cc/bbl4vw

Find Out H0w Much Your Lover L0ves Y0u?->> httpxxx://goo.gl/Lai30

H0w Much Your Patrner L0ves Y0u? find Here->> httpxxx://tinyurl.com/c7yjbja

How Much Your Patrner Loves You? find Here->> httpxxx://l0ver-makecs-youi.blogspot.se/

Find Out H0w Much Your Lover L0ves Y0u?->> httpxxx://tiny.cc/egl4vw

Find What Your Birthday Say about Your Profession? at httpxxx://check-y0urself.blogspot.com/
Find What Your Birthday Say about Your Profession? at httpxxx://check-y0urself.blogspot.in/
Find Out H0w Much Your Lover L0ves Y0u?->> httpxxx://goo.gl/Lai30
H0w Much Your Patrner L0ves Y0u? find Here->> httpxxx://tinyurl.com/cz4sdgk

mod security blocking ips and causing sites to go offline

This can cause site admins to lose access to their sites completely due to automatic blocks by mod security
Error 7 (net::ERR_TIMED_OUT): The operation timed out.

if you get this error on your site then it is most probably  mod_security banning your ip on your server

maybe due to hosting companies using older versions of mod security  software?

Access denied with code 406 (phase 2). Pattern match "(?:\\b(?:(?:type\\b\\W*?\\b(?:text\\b\\W*?\\b(?:j(?:ava)?|ecma|vb)|application\\b\\W*?\\bx-(?:java|vb))script|c(?:opyparentfolder|reatetextrange)|get(?:special|parent)folder|iframe\\b.{0,100}?\\bsrc)\\b|on(?:(?:mo(?:use(?:o(?:ver|ut)|down|move|up)|ve)| ..." at REQUEST_FILENAME. [file "/usr/local/apache/conf/modsec2.user.conf"] [line "117"] [id "1234123404"] [msg "Cross-site Scripting (XSS) Attack"] [data ".cookie"] [severity "CRITICAL"] [tag "WEB_ATTACK/XSS"]

ModSecurity ‏@ModSecurity9h
 You should upgrade ModSecurity to latest 2.7.3 w/restricted htaccess support

However, the fastest way around mod_security issues is to bypass mod_security entirely. Add the line 'SecFilterEngine off' to the .htaccess file in the root of your site . That should turn off mod_security, and allow you to at least verify if that's causing the real problem.




From: Breno Silva gmail.com>
Date: Friday, March 29, 2013 12:55 PM
To: "mod-security-users lists.sourceforge.net" lists.sourceforge.net>, mod-security-developers lists.sourceforge.net>, lists.sourceforge.net>
Subject: [mod-security-users] Availability of ModSecurity 2.7.3 Stable Release

The ModSecurity Development Team is pleased to announce the availability of ModSecurity 2.7.3 Stable Release.The stability of this release is good and includes many bug fixes.

Many issues and missing features for NGINX module were fixed. NGINX module version is now RC. We have fixed some minor issues for IIS.

We also added some important new features, the ability to load some specific directives into .htaccess files and the SecXmlExternalEntity security feature that will disable by default the possibility to load xml external entities. We recommend all users use this version.

Please see the release notes included into CHANGES file. For known problems and more information about bug fixes, please see the online ModSecurity Jira. Please report any bug to mod-security-developers lists.sourceforge.net.


Breno Silva

Tuesday, April 23, 2013

Most Popular Wordpress plugins

Wednesday, April 17, 2013

decision to retire the Google Affiliate Network

Our goal with Google Affiliate Network has been to help advertisers and publishers improve their performance across the affiliate ecosystem. Cost-per-action (CPA) marketing has rapidly evolved in the last few years, and we constantly evaluate our products to ensure that we’re focused on the services that will have the biggest impact for our advertisers and publishers. To that end, we’ve made the difficult decision to retire the Google Affiliate Network and focus on other products that are driving great results for clients.

Publishers can continue to earn revenue through the AdSense network. And marketers can take advantage of other CPA-oriented Google tools like Product Listing Ads, remarketing and Conversion Optimizer to drive valuable online sales and conversions. These areas are growing rapidly and we continue to invest significantly in them.

We’ll continue to support our customers as we wind down the product over the next few months. While we will no longer be adding new product functionality, we will maintain the platform during the transition period. We plan to disable publisher relationships from advertiser programs on July 31, 2013. Publisher payments will be disbursed for network activity generated through this date. We will continue to make certain functionality available through October 31, 2013 for retrieving reports, reconciling orders, and processing payments.

A huge thanks to all our advertisers, publishers and the team that has worked tirelessly on Google Affiliate Network over the past few years. We look forward to helping you grow your business in the future.

If you have any questions, please contact us.

The Google Affiliate Network Team

Friday, April 12, 2013

URGENT: Sites running on Wordpress at risk of a Brute force attack

  The below is applicable to you if you have a Wordpress powered site with us. A global brute force attack is underway on Wordpress sites hosted across the world. The attack is a sophisticated one and has been launched using a botnet, with tens of thousands of IPs being recorded as sources of this attack.
What is a A Brute Force Attack?
A brute force attack is when someone walks up to a locked door and starts repeatedly trying to pick the lock. Given enough time and enough persistence, nearly any lock can be breached. Most of the IPs used in this attack are spoofed which is making it difficult to block all of such attempts. Nevertheless, we are already trying to mitigate the attack at the network level. However, you too need to take a few precautions to make sure your personal WordPress installations are secure. That would give additional security in the ongoing situation.
You need to do the following:
1) The first step is to install WordPress Security plugins from http://wordpress.org/extend/plugins/better-wp-security/
 Run this plugin and follow steps given to secure your WordPress installation.
2) The second step would be to secure your WordPress Login page. To do this you can simply log into your cPanel/Plesk Panel and use the Password Protect Directory option and secure the wp-admin folder of your WordPress installation using a secure password. You need to make sure that you use complex password, preferably generated via a Random Password Generator so that your password is not easily uncovered under a brute-force attack.

In addition, if you are using one of our Linux-based hosting products then can also protect yourself from this attack using CloudFlare. This will protect your website from both this attack and many other types of attacks.
Please refer the below link to help you for configuring CloudFlare: http://tiny.cc/4tefvw
Also, do reach back to us for further clarity or concerns. Thank you for your co-operation.



Here’s what I would recommend: If you still use “admin” as a username on your blog, change it, use a strong password, if you’re on WP.com turn on two-factor authentication, and of course make sure you’re up-to-date on the latest version of WordPress. Do this and you’ll be ahead of 99% of sites out there and probably never have a problem.


Monday, April 8, 2013

some hosting spaces shutting down mail on linux servers from 20th April 2013

Dear Customer,

As you all are well aware that the nuisance of spam emails is ever increasing which causes loss of money and productivity. Till now the spam problem was limited to just receiving spam, however, in recent times, the problem of outbound spam has increased too. The outbound spam results in IP addresses of mail servers getting blacklisted and it leads to email issues resulting in losses to the companies relying on emails for Business. We have investigated the cause of outbound spam emails and have found that most of the outbound spam emails are because of email scripts hosted on the server. Many of the scripts use either the PHP Mail() function or CDOSYS which does not require SMTP Authentication. These scrips can be easily exploited by spammers to send out spam emails. Also, since there is no SMTP Authentication required, it is difficult to track spammers many a times.

In order to reduce the amount of outgoing spam sent from the servers, we have decided to disable the PHP Mail() function in all the Linux servers and IIS SMTP server in all the Windows servers. We will be disabling these features on 20th April 2013. We suggest you to modify your email scripts to provide SMTP Authentication before 20th April 2013 to avoid the email scripts stop functioning.