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 »
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.


phpLD Bugs & Errors / Re: I find something Weird.
« on: 27 March 2017, 03:36:09 PM »
Well, as I said, you already had Canonical code in your head, so if you added the code below you now have it twice in some places!

<meta name="revisit-after" content="1 day" />
<link rel="canonical" href="https://www.bloghints.com/detail/rs-trainings-601.php" />
<link href="https://fonts.googleapis.com/css?family=Open+Sans" rel="stylesheet">
<link href="https://fonts.googleapis.com/css?family=Raleway" rel="stylesheet">
<!-- Bootstrap core CSS -->
<link rel="stylesheet" type="text/css" href="/templates/Bloghints/bootstrap/css/bootstrap.min.css" />
<!-- IE10 viewport hack for Surface/desktop Windows 8 bug
<link rel="stylesheet" type="text/css" href="/templates/Bloghints/bootstrap/css/ie10-viewport-bug-workaround.css" />-->
<link href="/templates/Bloghints/style/font-awesome.min.css" rel="stylesheet" type="text/css" />
<link rel="stylesheet" type="text/css" href="/templates/Bloghints/style/main.css" />
<link rel="stylesheet" type="text/css" href="/templates/Bloghints/style/fileuploader.css" />
<link rel="canonical" href="https://www.bloghints.com/detail/rs-trainings-601.php" />
<meta name="generator" content="PHP Link Directory 4.2.2" />

It doesn't really matter though, but you just need to ensure that any canonical code you have matches the URL that you want each page to be seen as by the search-engines. It then doesn't really matter what the display URL is in the user's browser.


phpLD Bugs & Errors / Re: I find something Weird.
« on: 26 March 2017, 05:42:08 AM »
Correction to my previous post..... I was working on my XML Sitemap mod, so had that in mind when I replied. I meant to say . . .

My mod only uses the default URL's to SEO friendly version for the RSS pages themselves and NOT the content within them.  it doesn't add anything or take into account any custom code you may have added, as that would be impossible to ascertain.  It can certainly be customised though.


phpLD Bugs & Errors / Re: I find something Weird.
« on: 25 March 2017, 04:58:04 PM »
It is nothing to do with the mod.

It looks like you have custom coding adding the category path to URL's.  You need to change. or utilise the canonical URL's and properly redirect the details to the specific page you need.  The canonical URL you have coded in the source for the example page you give is https://www.bloghints.com/detail/rs-trainings-601.php

My category XML mod only uses the default URL's (as above) that you would set in admin using the default code.

As a side note, it's really not a good idea to add categories to details URL's. You may think it's good for SEO, but it has the opposite effect as the URL's usually end up far too long and the important part of the URL with the title will get dropped or ignored when a search engine assesses the page for relevant content.


Hosting / Installing Free SSL Certificates
« on: 10 February 2017, 11:58:52 AM »
IMPORTANT : This post relates to the hosting that we provide using the Hepsia Control Panel.  These instructions are meant as a guide only and not a definitive tutorial as changes in hosting terms or the provision of free certificates may change at any time.

If you encounter problems, I will assist for free, ONLY where time allows, but you should understand that you use these instructions at your own risk!

These instructions were correct at the time of posting / updating and were used exclusively to install the certificates at all my own sites, including this forum.

Last updated : 17 February 2017 at 16:12 (UK)

Now that Google have started penalising websites without SSL certificates (or rather, they say, giving sites with HTTPS a ranking boost), it is becoming important that you add them to your site.

Bruleo hosting offers great value certificates, but for those that cannot see the cost justification for your site, it is a relatively easy process to install fully functional free certificates provided by Let's Encrypt.

These certificates offer full TLS 1.2, AES with 128 bit encryption (High); ECDH with 256 bit exchange

Currently, the only draw-back with adding these free certificates is that they have a three month expiry, so would need to be renewed every 90 days.

Note : Many hosts will not allow you to install 3rd-party or free certificates as they want you to spend more money with them.  Most will tell you that you need to have a dedicated IP address, or even worse, a minimum of VPS hosting to install certificates: This is total rubbish as you do not need either (although a dedicated IP is recommended). If they tell you this, tell them to get lost and move to a host that doesn't lie. Unlike most hosts, and despite selling their own certificates and IP address (both of which I provide at cost), you are allowed install 3rd-party certificates on the hosting I provide using special IP addresses that are provided with each hosting account.  Of course, if you want a dedicated IP address, you can do that too!

The following may seem daunting, but all in all, it takes less than five minutes once you've logged in and got the relevant pages up that you need.

 It will be in four parts. Part #1 and #4 only need to be done once, but unfortunately, due to the current nature of free certificates, the rest will need to be done every 90 days (although this is being discussed at Let's Encrypt and may be extended in the future).

PART 1 (Create CSR for your site) :
1) Log into your Hepsia hosting Control Panel Go to 'My Domains' >> 'SSL Certificates'
2) Choose 'CSR Requests', then ''Generate CSR'.
3) Complete the form as required (use www.southsound.co.uk as Hostname as it will cover both www and non-www versions)
4) Once generated, copy the CSR and Private Key, using the icons under 'Actions'.
(Note : The email address you provide MUST be an account set up at your host and related to your domain, otherwise the generated certificate will not be valid.)

PART 2 (Prove site ownership and generate certificate) :
5) Go to https://www.sslforfree.com/ and enter your domain in the box and hit enter.
6) Chose Automatic or Manual Verification, depending on what you prefer. (Automatic might be quicker, but I don't like entering my FTP info on sites, so prefer the Manual method).
7) Follow the instructions.
8) Make Sure 'I Have My Own CSR' is ticked and paste in the CSR content you created in Step #4
9) Click 'Download SSL Certificate'.
(Note : If using manual verification, note that the first folder you will need to create contains a dot at the beginning of the name.)

PART 3 (Upload and install certificate) :
10) In your hosting Control Panel, choose 'My Domains >> Hosted Domains', then choose 'Edit Domain' (the cog icon next to your domain in the list).
11)  In the form that opens, under IP address, choose the IP displayed under 'Available Shared IP's for SSL's'
12) Choose 'Upload SSL Certificate' under 'Secure Socket Layer (SSL).
13) Paste in the Private Key and CSR content from step #4 above.
14) Paste in the 'Certificate' and CA Bundle from sslforfree.com in the other two fields.
15) All other fields can be left as they are, Click save, wait a few seconds and it should be done.

PART 4 (Redirecting http to https) :
Once you have installed, you will need to ensure that http' redirects to 'https'. Some hosts allow you to do this within the main hosting Control Panel, but if they do not, you will need to this in your main htaccess file by adding something like* the following code after 'RewriteEngine On' :
Code: [Select]
      RewriteCond %{HTTPS} off
      RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
(* Please note that there are a great many code variations that do the same thing. Depending on what other redirects you have in place [www to non-www for example], you may need to use different code, most of which can be found online.)

An example which should work in most cases to redirect http non-www to https www would be as follows  :
Code: [Select]
	## Redirect non-www to www taking into account SSL
        RewriteCond %{HTTPS} !on [OR]
        RewriteCond %{HTTP_HOST} !^www\.
        RewriteRule (.*) https://www.yourdomain.com%{REQUEST_URI} [L,R=301]

Extending on the above, another example would be like I have at www.gateuk.com where I redirect non-www to www pages AND redirect 'index.php' pages to the main domain with https :
Code: [Select]
	## Redirect non-www to www and redirect index.php taking into account SSL
RewriteCond %{HTTPS} !on [OR]
RewriteCond %{HTTP_HOST} !^www\.
RewriteRule (.*) https://www.gateuk.com%{REQUEST_URI} [L,R=301]
RewriteCond %{THE_REQUEST} ^[A-Z]{3,9}\ /index\.php\ HTTP/
RewriteRule ^index\.php$ https://www.gateuk.com/ [R=301,L]
You will need to research the exact code you need for your site, as everyone's exact requirements are different. DO NOT JUST BLINDLY COPY AND PASTE THIS TYPE OF CODE WITHOUT ENSURING IT WORKS FOR YOU!

a) If you have any directs calls to images or content on your site that use http, they will ALL need to be changed to https.  If you do not do them all, security warnings may show in visitor's browsers, with some browsers blocking access completely.  Also, Google will NOT recognise any sites with their latest updates that have any security warnings caused by these.  If you use any server third-party scripts stored on your server, you may need to edit these.  Some third-party ad providers (such as PaidOnResults), still use http for a lot of their banner code. If you use these, your site will suffer from security warnings. For example, if you include a banner on your site that is located on another site's server, that image must also be served though the https protocol. If the external site is not https, then the image will either not load, generate security warnings or prevent your entire site from loading. You will therefore need to consider either removing the banner entirely, or placing the image on your server.

In short, after changing to https, ANY resource used by your site that would ultimately be loaded onto a user's computer, will also need to be using https.

To see if your site fails anywhere, simply load your browser in Chrome, FF, Edge or IE and use any of the included developer resources in that browser and they will tell you exactly where to look. From personal experience, IE and Edge are best.

b) PHPLinkDirectory Users Only : Most, if not all default installations of the PHPLinkDirectory script have poor coding that do not allow for automatic detection of https, causing things like the listing submission process to fail following certificate installation.  For any identified code changes you may need to make following certificate installation, please see the following thread :
(Note : If you find any other problems following installation of SSL on our hosting AND using any version of the phpLD script above 3,2, let me know and if it is a problem caused by the default code, I will look into it and endeavour to find a fix!)

c) Do not forget to change any admin settings if you have them to reflect the new https URL.  For phpLD scripts for example, this would be in your admin 'Settings >> Site' section.  If you find that the https version of your site is loading without any formatting, this is probably the reason. (Note, some scripts contain URL settings in files).

a) Ensure you renew your certificate several days prior to the expiry date. Since the site needs to propagate DNS around the world, any change of certificate may take 24 hours or so before the certificate shows.  From experience with this hosting, it is unlikely to be more than a few minutes to fully propagate, but it is totally possible that it could take up to 72 hours.

b) If you complete your email etc in the main form for the certificate at sslforfree.com, they will send you a reminder one week before it expires.

c) It would be advisable to copy your Private Key & CSR and store them somewhere secure. That way, if the worst happens and you lose your site and need to restore, you should be able to these to reactivate any certificate you have already created. (I'm not sure how to do this just yet, but am advised elsewhere that it can be done!)

d) When creating the certificate at sslforfree.com, be sure to add both the www and non-www version of your domain. Sometimes, certificates for the www version will work with both, but it often depends on both the certificate authority, the hosting and how it is installed.  If you redirect non-www to www (or vica-versa) then this is not that important, as long as the redirect you use works for all pages and the certificate is created for the destination domain. (Note : It is recommended you do this type of redirect as it negates duplicate content issues.)

phpLD Bugs & Errors / Re: Error When Submit V4.2.2
« on: 08 February 2017, 03:11:01 AM »
Further to this problem, please see the following thread :

phpLD Bugs & Errors / Re: Error When Submit V4.2.2
« on: 06 October 2016, 01:00:56 AM »
I can say you do successful submit to it because the "Allow foreign submissions" option still "ON", as for captcha.php in my submit.tpl and i found this :
Then you probably need to talk to your host, or extend your default PHP and / or submit session as indicated before.

so, i think i don't need to change the protocol . . .
No need to change. Just make sure the URL in admin is set correctly.

After testing result failed, for now i will turn ON my "Allow foreign submissions" with no "Visual Confirmation"
Good luck.... your site will likely be hit by a ton of bots submitting.  Try using the Math option.

phpLD Bugs & Errors / Re: Error When Submit V4.2.2
« on: 05 October 2016, 05:24:43 PM »
If you are using SSL, you need to make sure all your images and file calls in your script use the https protocol.

Did you change the call to the captcha image file

Look in your submission page template and you will see an a href pointing to captcha.php./ It needs to be https.

However, if switching off the "Allow foreign submissions" allows submissions, it will definitely be related to your PHP or submit session session length, so you may need to talk to your host about that.

I also just submitted a test listing at your site successfully, so I would definitely say it has something to do with sessions if you are getting the error.


phpLD Bugs & Errors / Re: Error When Submit V4.2.2
« on: 04 October 2016, 10:35:24 PM »
Could be a few things . . .

1) You have another user session logged in when submitting. This can happen if you have admin logged in and are submitting as another user from the front.

2) You were logged in as a user, but your PHP session timed out.  Session length is set at hosting level and unless overridden, usually defaults to 24 minutes. It can usually be extended with a setting to your ini file and sometimes your htaccess (depending on your host's rules).

3) You took too long to submit after opening the page.  Submit sessions are set from the minute you enter the submit page and last for a fixed length of time (10 minutes I think) and is set to prevent multiple automated submissions.  This is usually more than long enough for most people, but it can be extended with a minor edit to the calculation in the script in file include/submit_session.php.  There is also a setting to turn of the 'foreign-script' restriction in admin, but I wouldn't recommended it if you don't want thousands of spam submissions in quick succession.

I suspect your reason is #1.


Update History / 05 Septeber 2016 - additions (v.1.4)
« on: 05 September 2016, 05:22:42 PM »
Version 1.4 released.

Now reports the number if empty categories (without any listings).

Widget Requests / Re: Category Cloud in Main Content Area
« on: 01 February 2016, 03:54:28 PM »
The title not appearing is due to the way the main template files are coded. 

Unfortunately, there is an error (missing code) in virtually all phpLD templates that causes this. If you look at the widget code for the widget templates in your main template folder and compare the formatting code in the vertical widget files to the main area ones, you should see what's needed.

There are a couple of other errors in the main widget code as well.  For example, the way it is coded to have divs inside list elements etc. This is not w3c compliant and can also cause list bullets to show in main areas.

Also, one of the main area widget code is incorrectly specified as the side widget code... can't remember which one without looking.

Assuming it's not been changed in your template, widget code for the main areas are contain in the following templates :



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 »