Entries Tagged 'Web Hosting' ↓

(1) When Activating LiveLinks

If you are seeing an error that looks like this when you try to activate LiveLinks…

Fatal error: Cannot redeclare dap_filter_posts() (previously declared in /home/sitename/public_html/wp-content/plugins/DAP-WP-LiveLinks/DAP-WP-LiveLinks.php:11) in /home/sitename/public_html/wp-content/plugins/DAP-WP-LiveLinks/DAP-WP-LiveLinks.php on line 11

First click on the DigitalAccessPass link on the left side bar of your WP admin panel and see if you able to login to the DAP Admin Panel successfully.

If yes, then  you can ignore this error. If not, try out these solutions one-at-a-time.

Solution A) This could be because you have incorrectly named the DAP or Livelinks folders.

Remember, the dap folder must always be named dap (all lower case – and not, say, dap_v4.3). And the livelinks folder must be named DAP-WP-LiveLinks .

Solution B) Make sure you have installed dap to the root of your site/domain. If you installed it right, you will be able to access this URL:

http://yoursite.com/dap/phpinfo.php

Note: Replace yoursite.com with the name of your site.

Now go back to WP admin panel -> plugins  and de-activate and re-activate the DAP-WP-LiveLinks plugin.

Solution C) Go to /dap folder on your site

Rename dap-config.php to dap-config.old.php

Now go back to WP Admin -> Plugins -> de-activate and re-activate DAP live links plugin.

Solution D) Go to WP admin panel -> plugins

Try to de-activate all active plugins. Just activate DAP-WP-LiveLinks first. See if it works. Then re-activate all other plugins one-at-a-time to find out if there is a plugin conflict.

Solution E) Go to WP admin panel -> Appearance -> Theme

Try to de-activate the currently active theme and use the WP default theme. Now go back to WP admin -> plugins and de-activate and re-activate DAP Live Links plugin and see if that resolves the issue. If yes, it points to a theme issue and you might have to consider switching the theme or contact the theme developer for a possible fix.

Solution F) This applies to DAP installation on a sub-domain or add-on domain.

If you are installing DAP on a sub-domain or an add-on domain, then this problem is likely because the path to the root of your site does NOT match the server document_root.

Here’s how you can figure out the siteroot and document root.

Run this command in a browser window:

http://yoursite.com/dap/getpath.php and note down the path. That’s the path to the root of your site.

Run this command in a browser window:

http://yoursite.com/dap/phpinfo.php and search for document_root. Note down the path. That’s the path to the document root of your site.

NOTE: replace yoursite.com above with the name of your site.

If the only difference is that the first one (getpath.php) has a /dap at the end, then it’s fine. But if getpath.php results in a different path than the one returned by phpinfo.php, then you will have to update wp-config.php with a new siteroot definition using the value returned by getpath.php.

Copy the results of getpath upto /dap as shown below and add it to wp-config.php.

For ex – if getpath.php returns – /home/yoursite/yoursite.com/dap, then this will be what goes into wp-config.php

if ( !defined(‘SITEROOT’) )

define(‘SITEROOT’, ‘/home/yoursite/yoursite.com’);

Please Note :

Replace backticks (‘) above with single quotes in the define statement. When this document is updated, wordpress replaces single quote with backticks, but if you copy and paste the define statement above directly from this document to your wordpress config file, remember to change backticks back to single quote.

Now try to re-activate dap live links plugin.

If it succeeds and installs DAP successfully, then go back to /dap folder on your site. You will now see a new file called dap-config.php. Edit the dap-config.php file.

Add the same line to dap-config.php also.

if ( !defined(‘SITEROOT’) )

define(‘SITEROOT’, ‘/home/yoursite/yoursite.com’);

That’s it. You will not see any of these warning/errors after that.

NOTE: here ‘/home/yoursite/yoursite.com’ is just a sample, you need to use the path returned by http://yoursite.com/dap/getpath.php on your site.

Solution G) It is possible that your web site does not meet the minimum requirements to run DAP .

If you open a ticket and give us your FTP info and your WordPress Admin login info, we can confirm this to you right away.

— *** —

If you are seeing an error that looks like this when you try to activate LiveLinks…

Oops! Could not create the config file (dap-config.php). Please make the ‘dap’ folder writable by doing CHMOD 755 (and if that doesn’t work, then try CHMOD 777.)

Installation failed. Please de-activate LiveLinks and re-activate it when you’ve fixed the issue. (106)

* CHMOD just the dap directory to 777.

* Then de-activate and activate the LiveLinks plugin.

* This time around, it should be able create the dap-config.php file within the dap directory. You should see the successful installation message.

* CHMOD just the dap directory back to 755.

If that doesn’t work, then open a ticket with the FTP info and WP admin info.

————————————————————

(2) Session Error

If you see an error that looks like this…

Fatal error: Dap_Session::isLoggedIn() [dap-session.isloggedin]: The script tried to execute a method or access a property of an incomplete object. Please ensure that the class definition “Dap_Session” of the object you are trying to operate on was loaded _before_ unserialize() gets called or provide a __autoload() function to load the class definition in /home/site/public_html/dap/inc/classes/Dap_Session.class.php on line 41

This is basically caused by someone else’s 3rd-party WordPress plugin that is wiping out the “session” data (or user data stored in memory) which DAP relies on to store the user information. So there are two things you can try…

1. See if you have a plugin by name “WordPress Automattic Upgrade” in your wordpress plugins page.This has created many issues for so many other plugins too, including LiveLinks. Just de-activate this plugin, and your error should go away. Also, if you are using WordPress version 2.7.1, you don’t really need this plugin any more – the automatic upgrade feature has been built right into this version.
2. See if you have a plugin for doing “Captcha” – this is where to prevent bots from spamming your comments, your visitor is presented with some kind of an image to verify that they are human. Try with that de-activated.
3. If none of the above worked, or if you don’t have any of the above plugins active and you’re still seeing the error, then just try de-activating all other plugins temporarily (except LiveLinks, of course), and turn them back on one-by-one.

Refresh your blog page every time you activate a plugin. That way, you will know which is the plugin that is causing the error.

If that still doesn’t help, just open a support ticket and we’ll take care of it.

————————————————————

(3) PDO Error

You see an error like this:

Fatal error: Class ‘PDO’ not found in /home1/knowlee3/public_html/buildamagneticnetwork/dap/inc/classes/Dap_Connection.class.php on line 19

If DAP had been working fine on your web site, and you all of a sudden see this error, then your host quietly pulled the rug from under your feet . This appears because they either deliberately or mistakenly disabled the “PDO” library, which is a must-have requirement for DAP to run.

So check with your host and ask them “if they disabled PHP/PDO for MySQL on your server recently”.

————————————————————

(4) Memory Allocation

You see an error like this:

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 16 bytes) in /home/yoursite.com/public_html/dap/inc/classes/Dap_Connection.class.php on line 19

If this happens just once, then just ignore it.

But if it occurs more than once, then it could be because:

a) You recently made some changes to your DAP files or web site files, and overwrote/updated your dap-config.php file with the wrong database information. Even though it shows up like a memory issue, in reality it could be because DAP is unable to connect to the database because of incorrect information in the dap config file. Check the database settings within your dap-config.php file.

b) Your server legitimately has a low memory limit set by your host, and your host needs to increase the memory allocated to PHP/PDO. Open a ticket with your web host to do this.

Or add this line to the top of your wp-config.php file:

ini_set('memory_limit', '64M');

————————————————————

(5) Simple-Pie & Memory Allocation

You see an error like this:

Fatal error: Allowed memory size of 37423432 bytes exhausted (tried to allocate 371520 bytes) in /…/public_html/~username/wp-includes/class-simplepie.php

Open the file wp-config.php (which is in your blog’s main folder)

Add this line at the top…

define('WP_MEMORY_LIMIT', '64M');

That should take care of the error.

What are the minimum web-hosting requirements to run DAP?

See “Minimum web-hosting requirements”

What web hosts to you recommend?

See “DAP-Certified Web Hosts”

I’m getting an error during installation

See this post for more details about errors .

How can I avail of Free Installation?

See “Free Installation”

How do I setup Cron?

Setting up Cron Jobs

All about Cron Jobs

Your host does not support Cron Jobs

(Note: You can get this setup as part of your free installation. But if you insist on doing it yourself, keep reading

There are two cron jobs (back-end, scheduled jobs) that you need to setup.

A) dap-cron.php (mandatory – once an hour)

This is the main one. It sends out broadcast emails, autoresponder emails, handles bulk member imports, affiliate commissions processing, clean up, etc. This one is mandatory.

B) dap-emailorder.php (optional – every 10 minutes)

This is the email order processing cron, used ONLY for 1ShoppingCart. Skip setting this cron up if you’re not using 1ShoppingCart or 1SiteAutomation.com.

Path to DAP

Visit the url below in a browser window (replace YourSite.com with your actual domain name):

http://YourSite.com/dap/getpath.php

This will show something like this in your browser:

/home/path/to/yoursite.com/dap

This is your “Path to DAP” to your root folder.

To the end, add “/dap-cron.php”. So that makes your new “Path to DAP” to be:

/home/path/to/yoursite.com/dap/dap-cron.php

This is your new “Path to DAP”. Make a note of this on a piece of paper, or in a notepad/text editor window.

Setting up the Cron jobs

A) dap-cron.php

This one is mandatory. Should be set up to run Once Every Hour. This hourly process is what sends out all the scheduled broadcast (bulk) emails and processes different types of “bulk actions” – like importing a large list of customers into DAP from an external system, for instance.

1. Log in to your web host’s control panel (or cpanel)
2. Look for the icon “Cron Jobs” in the “Advanced” section – usually towards the bottom of that page, and click on it.
   
3. On the next window, in the “Common Settings” drop down, select “Once an hour…”.
   And in the “Command” field, enter this:/usr/bin/php<insert space>/home/path/to/yoursite.com/dap/dap-cron.php

   NOTE: The text <insert space>above means you must hit the spacebar and insert an actual space

4. Click on “Add New Cron Job”.

That’s it for this one.

B) dap-emailorder.php

Follow this step ONLY if you’re using 1ShoppingCart or any private label of 1SC – like 1SiteAutomation.com.

This cron job should be set up to run once every 10 minutes. This is the script that processes all of your orders from your customers through email. So, if you set this up to run once every 10 minutes, then every 10 minutes, it will log in to your billing email address (you can configure what this email id is within the admin control panel on the “Config” screen) and process the email notifications that you have received from 1ShoppingCart (and its private labels).

Running it sooner than once every 10 minutes – like say, once every minute or even once every 5 minutes is resource intensive. Your web host may not not even allow it in the first place. But even if they do, it’s not recommended.

Follow steps A(1) through A(4) above. Only difference is in what you’re going to be entering in the “Command” field.

For this cron job, it is…

/usr/bin/php<insert space>/home/path/to/yoursite.com/dap/dap-emailorder.php

Only difference between the two cron jobs is in the name of script that is being run. For the hourly cron (A), it was dap-cron.php. For the 10-minute cron (B), it is dap-emailorder.php.

MISCELLANEOUS NOTES:

1. Where you see the text <insert space>, replace with an actual space (hitting the space bar).

2. Cron Email Reports:

Your webhost control panel allows you to set an email address where it can send the cron output. So login to your Webhost Control Panel > Cron Jobs page, and add your email address where you want the cron report sent.  If you do not want to receive the cron report, you can just remove the email address, leave it blank, and save changes.

3. To check if you have set up the cron job correctly, you can set DAP Admin -> Setup -> Config -> Log Level to 5 . Then go to DAP Admin -> System -> Logs . Empty the logs by clicking on the “Empty Logs” link, and then revisit the screen and refresh the page, after say 10 minutes (to verify the running of dap-emailorder.php) or at the top of hour (to veryify the running of dap-cron.php).

4. To force run a cron (manually), click on this link:

http://YourSite.com/dap/dap-cron.php
(to run hourly cron)

http://YourSite.com/dap/dap-emailorder.php
(to run the email order cron that runs every 10 minutes)

Replace YourSite.com with the actual domain name of your web site.

5. Disabling Cron Emails:

The cron job by default will send you an email every time it runs (feature of your web host, not that of DAP). If you wish to disable it, go to the Cron tab page and just remove your email address from that page (“Please enter an email address where the cron output will be sent”).