Welcome guest

Please note that access of most of this forum's features, including the ability to post, access to mods and various other features require prior registration using an approved invite key.

If you are an owner,  administrator or webmaster of a website using a version of the phpLinkDirectory script, please use the contact form to request a key.

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - bruleoadmin

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 »
Update History / 25 December 2017
« on: 25 December 2017, 11:41:52 PM »
Main function updated as original was ignoring some IP addresses within the imported list.

Update History / 13 December 2017 : New Setting
« on: 13 December 2017, 03:48:08 AM »
Ability to set a user agent added.

phpLD Bugs & Errors / Undefined Errors in Logs
« on: 10 December 2017, 03:46:46 PM »
LAST UPDATED : 11th December 2017 @ 06:50

The default phpLD code, for all versions, contains hundreds of instances of incorrectly formatted code, resulting in 'Undefined 'type errors appearing in your server logs.  These include, but are not limited to :
   Undefined Variable
   Undefined Index
   Undefined Offset

While not adversely affecting the operation of your site, these errors can quickly fill up error logs, which in turn can slow site performance.

Only fix the errors if shown in your logs and do NOT just arbitrarily change the code of your site, just because they are shown here.

The attached file shows the errors you might see in your logs, the original code and what it should be changed to eliminate the errors.

While this list contains many errors that you may see, it is by no means complete and will be added to over time.

phpLD has many versions and code amendments within those versions, so it is impossible to list everything you may see. However, if your site shows any 'Undefined' type errors not listed below and we will endeavour to find you a solution.

Line Numbers shown may not match your installation
Please ensure the 'FIND' code is exactly matched with that shown and do not change if it is different.

phpLD Bugs & Errors / Unable to log into admin panel
« on: 08 December 2017, 06:01:42 PM »
There are a lot of reasons why this could be happening on your install, but most are related to the way your host has things set up and NOT to do with the phpLD script in any way.

If you are having issues logging into your admin panel, the following things will need to be checked :

  • Find our where your host keeps it's folder used to store temporary session data. This is usually a folder called 'tmp' but may be called something else on your host. It is usually stored outside your public_html folder and doesn't present any issues, but more and more lately, this folder is becoming inaccessible for scripts due to permission based errors or the script simply not finding that folder.  Try the following :
    • Create a 'tmp' folder inside your public_html location.  this is 100% secure, but if your admin login starts working after doing this, then you can move it outside of public_html and make the next edit.

    • Set your temporary folder location in your includes.config.php file by using 'ini_set' or 'set_include_path' (or amending the path if already there). Some hosts don't allow scripts to set the path, or may not allow the use of either of the commands, so you should ask your host how you can set the path to your temporary session folder.

      Example : ini_set('session.save_path', $_SERVER['DOCUMENT_ROOT'] . '/../tmp');

    • Make the folder world writable.  If outside public_html, then this is perfectly safe.

  • If the above does not resolve the issue, then check that the hashed passwords in your database PLD_USER table includes a {sha1} prefix, as a few hosts seem to have been removing this when transferring data.  Hashed passwords stored in the database should look something like the following :


    If any are missing {sha1} at the beginning of the character string, then logging into those accounts will not be possible.

  • Check that your PLD_USER table is not locked or crashed.  If it has, please run a 'Repair' from phpMyAdmin on that table.

  • Check your file and folder permissions.  Incorrect permission settings on some hosts can prevent logging in to user accounts on phpLD scripts. Usually, PHP folders should be set to 755 and files to 644.  Exceptions are include/config.php which should be set at 444 as an absolute maximum (for security).

    On some hosts, for phpLD to function properly, the temp/, temp/templates, temp/cache, temp/adodb folders should be set to 777, although this is quite rare these days.

You may need to to any or ALL of the above., but try them in the order you see them.  If you still can't get into admin after performing all of the above, you may need to speak to your host, espeically if you know it was working before and haven't changed anything prior to it stopping working, as they may have upgraded or changed something else that is affecting your site in another way.

phpLD Bugs & Errors / Re: Error on Admin Panel
« on: 07 December 2017, 03:16:11 PM »
I will respond a little later, as I am in the middle of applying a few security updates to one or two of my own sites. :)


phpLD Bugs & Errors / Re: Error on Admin Panel
« on: 07 December 2017, 02:57:52 PM »
100% Compatible with at least 5.6.  Not tested on PHP 7, but I expect it will be fine as most of the edits are related to MySQL / mySQLI code updates... if not, I will monitor and apply relevant updates if required.

But definitely DO NOT block errors on your site, as you may be hiding something that should be fixed!


phpLD Bugs & Errors / Re: Error on Admin Panel
« on: 07 December 2017, 02:52:11 PM »
Could be a lot of things . .

1) Firstly, check your error logs, as I bet it will say in there what it is. (Or stop supressing errors on your install!).  I am willing to bet it's a PHP and / or a mysqli depreciated code error.  If so, I can upgrade your site to be compatible with mysqli and later versions of PHP for a fixed fee of $35.00 (around 120 separate edits).

2)  Could be a java-script error.  Try a different browser.

3) COuld be a crashed table in your database.  Log into phpMyAdmin, check for crashed and / or locked tables and repair.


IP Banlist / Information for the IP Banlist mod.
« on: 06 December 2017, 02:15:09 AM »
This mod allows you to ban IP's from accessing your sites' contact page forms with a customisable error message, or if preferred, blocking IP addresses completely from your site and returning a permissions (403) based error to the user.

If you have multiple sites, this mod will use centrally located IP ban lists that you only need to uploaded to a single site, making it a simple process of making a single file edit to ban an IP address across as many sites as you own.

The mod can be configured to use two separate lists to ban IP addresses differently :
If only a single banlist is supplied, IP's added to that list will be banned from your contact form only.
If a secondary list is added to the mod settings in admin, any IP's added to that list will be banned site-wide.

When banned from your contact form, the mod allows for a customisable error message which is set in admin for each site.

The mod works independently from the Ban Control system built into admin, which is only supposed to block IP's from submitting listings.

Self Install : Free / $2.50 **
Professional Installation (per site) : $15.00
(Discounts for multiple site installs available on request).

Please use the contact form or Skype 'torquepoint' if you wish to purchase this mod.

phpLD version 4.1 to 4.2.2 (as self-install)
All other versions : Fully installed service only.

The banlists you create (in txt format), must be uploaded to a server that has cURL enabled.
Most hosts do allow this by default, but there are some that require you to enable cURL this in your control panel or PHP configuration files.  Please check that your site that you intend to host the ban-lists supports cURL connections.

Please note that mods for Beta or RC versions of phpLD are not supported, unless we install.

** Only available for free when a total purchase value of $10.00 or over has been made for any of our mods for self-install.


Update History / 06 December 2017 (General Release)
« on: 06 December 2017, 01:24:33 AM »
Mod released for phpLD versions 3.2 to 4.2.2

Update History / 26 November 2017
« on: 26 November 2017, 03:54:19 PM »
Correct a syntax error in the instructions :
{$smarty.const.DOC+ROOT} should read {$smarty.const.DOC_ROOT}

Hosting / Re: Installing Free SSL Certificates
« on: 05 May 2017, 10:04:19 PM »
= = UPDATE = =

Free SSL Certificates from Let's Encrypt have now been enabled as a feature in the hosting I provide without needing to perform any of the instructions outlined in the previous post.

Anyone using my hosting now has the ability to activate totally free certificates with AUTOMATIC renewal, simply by editing the settings for the domain in their control panel.

I will leave the instructions below for legacy reference only as it also covers some issues you may encounter when installing certificates from any provider.


phpLD Bugs & Errors / Re: Error while in payment page
« on: 09 April 2017, 01:34:37 PM »
I am glad that the problem was resolved in the end. 

For reference, to any other users reading this : It appears this was due to some server settings preventing data being saved to the database, specifically from the phpLD payment process.  On investigation, it was found that all coding in the installation files was correct and the data generated was correct, but would not save to the database table, which was also formatted correctly and in the correct state. By a process of elimination, it was then decided that the error could only be caused by either other non-standard scripts that were installed, clashing with the process or the hosting / server settings preventing certain data being transmitted to the database.

My suspicion is that the server was running a higher PHP version than the script was designed for; perhaps PHP 6, although this is unconfirmed.

Please note that I do have instructions on how to upgrade PHPLD scripts for use on PHP versions up to an including PHP 5.6, but anything beyond that is untested.  For PHP6, there have been a lot of changes and some further code the the phpld script uses will likely become depreciated. Therefore, as the most recent version of phpLD is at least 4 years old, I expect they will have problems running on PHP6 and beyond. 

Thanks to  suwandichen13 for the donation in return for the time spent. It is much appreciated.


phpLD Bugs & Errors / Re: Error while in payment page
« on: 05 April 2017, 08:10:12 AM »
Those are the names of the fields in your PLD_PAYMENT table that are having data saved to them when the payment process runs.  You should therefore check that all those fields exist.  If any are missing, then that is why the process is failing.  If they do exist, check that the table is not corrupted and run a fix from phpmyadmin of necessary.

And of course, if the payment fails at the database write stage, then how is anything going to be able to write to provide you a log in admin??!


phpLD Bugs & Errors / Re: Error while in payment page
« on: 04 April 2017, 08:27:10 PM »
Not literally '$arrayname'!!!   ???

'$arrayname' will be whatever the main data array name is called in payment.php. I can't recall without looking and I'm too busy to go digging around in my files, but you should be able to find it by looking at your own files..... it's probably something like $paymentdata or $pay_data.  Just add the prnt_array in the file after the last data variable has been assigned and it should output to your screen when you run the process.


phpLD Bugs & Errors / Re: Error while in payment page
« on: 03 April 2017, 08:56:48 PM »
It could be a lot of things.

1) Corrupt database tables.
2) Fields being saved not matching the tables in the database.
3) Depreciated code.

Probably #2

Easiest way to identify the error would be to edit the code so that the saved data is displayed on the screen [using print_array($arrayname) which you'll find in payment.php] and then run a test submit. Compare the data to the fields in the database and that should give you an idea where the error is occurring.


Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 »