x Toggle Content
Toggle Content    Register or Login  -  November 23, 2017, 6:48 pm  
Toggle Content Commercial Themes
This is an opportunity for you to preview TCD commercial themes. All themes seen here can be purchased from the store.
Toggle Content User Info

Welcome Anonymous

Toggle Content Navigation
Toggle Content Project Status
Treasure Coast Designs & Web Hosting
If you are looking to create your own website here are the 3 things you need and in this order:

1. Domain Name - $10 to $20 (preferably with an ICANN accredited registrar)
2. Web Hosting - Between $50 and $1,000 annually. Generally $100-$200 for most people.
3. Web Design - Between $100 and $10,000 annually. Generally $300-$500 for most people.

Please make sure you have a domain name registered with an ICANN accredited domain name registrar. Network Solutions or GoDaddy are good choices. Avoid web hosting or web design companies that want to register your domain name for you. Many stories can be found online about good people losing their domain names because of 3rd-rate web hosts trying to pass themselves off as registrars. Take control of your own domain name from the start and go with a reputable registrar, you'll save yourself a lot of time and energy in the long run.

Here is a current list of ICANN accredited registrars.

Design Packages
HTML Website $300 PHP Website - $500 USD
• 3 pages designed by templating
• header graphic with company/personal logo
• footer graphic with TCD small footprint logo
• search engine friendly meta keywords
• designed with xhtml and css compliance
• time based maintenance fee for requested updates
• 5 pages designed by templating
• universal header graphic with company/personal logo
(faster pages)
• universal footer graphic with TCD small footprint logo
(faster pages)
• search engine friendly meta keywords
• designed with xhtml and css compliance
• time based maintenance fee for requested updates
Open-Source CMS Package - $700 USD Open-Source E-Commerce Package - $1000 USD
• DragonflyCMS, Joomla, PHP-Nuke, Mambo, or Wordpress
• Installation, Setup, Customization
• customized universal template
• web interface for content administration
• administrative training
• content creation training
• template design with xhtml and css compliance
• task based maintenance fee
• Zen-Cart Solution
• Installation, Setup, Customization
• up to 10 products upon initial setup
• web interface for product administration
• administrative training
• content creation training
• designed with xhtml and css compliance
• task based maintenance fee


If you have any questions or would like a customized package quote please Contact Us
Website secured with SSL/TLS
It's been a long time since the last announcement. I've long since stopped developing in PHP/MySQL but when it came time to play around with HTTPS SSL/TLS this was a good place to start. Because this site was coded so brilliantly to begin with more than a decade ago; the update process only took 15 minutes of actual code changes. Times are changing and this website is woefully outdated now by not relying on new and better techniques such as web sockets or AJAX. It's hard to argue with the speed of GET/POST vs more modern frameworks that rely heavily on memory hogging javascript.

A small Apache rewrite rule is required and ensuring that no images (including in news content) are linked to the old http url. Unfortunately this will break a lot of images but your users will be much better off in the long run under a secure roof.

SSL is nothing new but what is new is the concerted effort of browser developers to show all internet users the security of their website connection with a lock/unlock icon. There is currently a big push by many major websites and browsers to emphasize that a non-https website might not be somewhere you want to be.

The SSL secure lock icon is one of the first things you see in a browser when you visit a website now. This means any website without HTTPS in the future will be frowned upon by users and more importantly, search engines. Google announced last month that fully compliant HTTPS websites will be given search result prioritization over ones that are not. That's a pretty big deal in shaping the future of the web. All aboard the SSL train.

In order for a website to achieve a green locked icon (fully validated HTTPS) the admin of the site has a couple major changes to make. The most important task is to ensure the site is secured from externally loaded content (no more hotlinking images from another domain including the HTTP version of the same site, ouch). Effort must be put into changing all content links from HTTP to HTTPS. Lord help you if you have hardcoded URLs in your HTML/CSS, image galleries, links, scripts, etc.. as fixing them on your site could get quite tedious.

It's not impossible to abuse SSL as many previous iterations are now considered insecure and can be broken in real-time with modern computers. As computing power increases so will how much more bit encryption is required to stay ahead of the curve.

If you are a developer there are plenty of obvious ways to get around the rules for hosting mixed content and still have a green secure icon. I do not condone cheating, malicious scripting, selling user data, giving away user data, or running ad campaigns on your website from untrusted 3rd parties (Google and other well known advertisers excluded). Be wary of those who contact you to offer ad campaigns on your websites, 99% of the time they're up to no good and only want to use your website as a vector. Just because you see a green icon doesn't mean you're absolutely secure from prying eyes, viruses, or corrupt admins. The internet is definitely more secure than it was because of HTTPS but it's not a 100% guarantee of safe browsing on the internet. Stay safe out there.

I'm still around the internet, playing with new frameworks, and trying to make the internet a better place.

Compliance
Posted by Devon Friday, February 10, 2017 (15:43:52) comments? | Printer Friendly Page  Send to a Friend | Score: 0

Popular Online PayPal Fee Calculators Are Wrong
While developing our own in house PayPal module we came across an odd sort of mass miscalculation happening online.

PayPal Fee Calculators using incorrect calculations:
http://www.rolbe.com/paypal.htm
http://www.gregledet.net/ppfcm.html

The correct PayPal fee as of this date is (* 2.9% + .30).
The sites listed above use the calculation (+.30 * 2.9%) which of course yields a must different and ultimately incorrect result.

Because those 2 sites are the most visited sites for search keywords "PayPal Fee Calculator" they are unwittingly affecting thousands of people (or more). There are a lot of people sending more money than required for their purchases. This of course nets PayPal more money. Unfortunately there isn't any information online currently which describes the mistake (other than here).

This news is important to other web developers looking to make their own PayPal fee calculators and browsing for other general examples online. If one assumes the calculations on those sites are correct it makes PayPal look to be skimming money (more specifically each half or hundredth cent depending on decimal placement) from all customers. This is not the case and could potentially affect PayPal's reputation as a credible company. PayPal does indeed stick to the correct calculation they advertise.

To all developers out there; your calculations are correct and the sites listed above are incorrect. Don't waste precious time trying to debug your fee calculation scripts because you'll never solve the fictitious issue of the missing half cents. Wink

PayPal Fee Calculators using correct calculations:
http://thefeecalculator.com
http://alphapal.net/fee-calculator.php

The module we're building here will have a fee calculator built in and does use the correct calculation (as currently stipulated by PayPal). PayPal does change their rate from time to time so in the future developers will have to adjust their scripts accordingly.

World
Posted by Devon Thursday, September 16, 2010 (06:14:36) comments? | Printer Friendly Page  Send to a Friend | Score: 0

Speed Test Module 2.0
Here is a speed test that will allow you to easily understand what level of service or disservice your ISP is providing you.

TCD Speed Test Module
Tired of seeing speed tests that always give you the results in megabits? Well if you use the TCD Speed Test module it will not only give you a breakdown of your score but it will also convert it to every file format for you to easily understand in a nice graphical layout.



The reason I decided to output the scores in a variety of formats is because Megabits is very misleading and purposefully used by ISP's to make the general public think they are receiving more than they actually are. Everyone is familiar with Kilobytes and Megabytes so advertising speeds as 2Mb makes the public believe they are receiving very good speeds (as in 2 Megabytes) when in fact they are receiving 256KB. Megabits has no real world usage other than in advertising.

If you want to know what your speeds are without having to do your own conversions (in your head, on a calculator, or through a website) then use the TCD Speed Test. TCD Speed Test is a free service.

DragonflyCMS Addon
Posted by Devon Tuesday, August 17, 2010 (08:51:13) comments? | Printer Friendly Page  Send to a Friend | Score: 0

Denying IP Ranges with htaccess
When it comes to preventing unwanted visitors such as email harvesters, forum spammers, and otherwise generally bad bots; admins have been using the .htaccess file with a ruleset of deny from ip. That's fine for a case by case basis but say you want to deny an entire ip range for whatever reason you want.

That's where CIDR Notation comes into play. CIDR stands for Classless Inter-Domain Routing. It is a method of categorizing and allocating IP addresses for efficiently routing IP packets on the Internet.

Basically it's an amendment tacked onto an ip address. After DNS was created they knew the standard IPv4 range was not scalable enough. CIDR is an attempt to provide additional efficiency of packet routing to IP addresses within the same geographic area. The whole system was designed to be a temporary measure until a better solution (IPv6) could be implemented. Because CIDR has proven it's usefulness as an additional method for packet routing it is being worked on for IPv6 as well.

CIDR is not a perfect way to specify a range for IP deny but it can make the life of an admin much easier. Now we will go over some real world examples and how to save your htaccess file from getting bogged down with hundreds of IP Deny lines.

Here is an example of an IP Deny within .htaccess which bans a range of IP's from DotBot.

deny from 208.115.111.240
deny from 208.115.111.241
deny from 208.115.111.242
deny from 208.115.111.243
deny from 208.115.111.244
deny from 208.115.111.245
deny from 208.115.111.246
deny from 208.115.111.247
deny from 208.115.111.248
deny from 208.115.111.249
deny from 208.115.111.250
deny from 208.115.111.251
deny from 208.115.111.252
deny from 208.115.111.253
deny from 208.115.111.254
deny from 208.115.111.255

As you can see there are quite a few IP's that DotBot has at it's disposal. Now go over to Mikero.com's CIDR IP Calculator and plug in the IP ranges. It will spit out a very nicely formatted CIDR range to deny.

deny from 208.115.111.240/28

By the way, if you use Whois on some domains such as dotnetdotcom.org (DotBot's home), sometimes the registration details will display a CIDR address for you. That can make your life easier if they become a nuisence but in most cases using Whois on every IP is more work than it's worth. Most admins just stick with using ARIN for quick and painless IPv4 probing of visitors indexing their site.

That's it. All those deny lines are gone thanks to CIDR addressing. As mentioned earlier CIDR is not perfect. There are instances where you can't specify the exact range you want. The Mikero CIDR calculator will automatically show you the next largest range which includes the range you want. Sometimes, that can include a couple hundrend million more IP addresses than you want so it's definitely not a good idea to use it for that purpose. There is always a way around it though as I'll detail.

Let's say you want to ban ranges 85.0.0.0 to 89.255.255.255. If you are looking for an IP deny solution then you are probably familiar with using
deny from 85
deny from 86
deny from 87
deny from 88
deny from 89

In this instance CIDR is actually no good. What you have been doing is the easiest method. CIDR will output the following if you try to ban by that range.

Resulting network range (in CIDR notation): 80.0.0.0/4
I had to expand your range by 184549376 addresses, or 220%.

As you can see, CIDR couldn't calculate the exact range and had to expand out to the next possible range. Doing so included an additional 184549376 addresses. Not good. In this instance it's best to use the simple
deny from 85 method
OR
if you want to write that in CIDR notation it would be
deny from 85.0.0.0/8
deny from 86.0.0.0/8
deny from 87.0.0.0/8
deny from 88.0.0.0/8
deny from 89.0.0.0/8

Whenever you want an entire range from the first octect the CIDR notation is always /8:
192.0.0.0 to 192.255.255.255 = 192.0.0.0/8
65.0.0.0 to 65.255.255.255 = 65.0.0.0/8
and so on.


I don't pretend to understand CIDR Notation or calculations yet. What I have found is a very easy way to shorten .htaccess rules with the use of CIDR. Thanks to the excellent calculator by Mikero.com for providing an easy way for admins to learn more about CIDR.

Tutorial
Posted by Devon Saturday, March 14, 2009 (02:44:45) Read More... | 1 comment | Printer Friendly Page  Send to a Friend | Score: 0

Major Webhosts upgrade to PHP5 and MySQL5
Most web hosts have been slowly converting to PHP5 and MySQL5 over the course of the past 2 years. It seems as though most of the world is now running PHP5 and MySQL as the major hosts such as Site5 have completed the upgrades.

For those still running DragonflyCMS 9.1.2 with a newly upgraded PHP and MySQL you'll find many modules and functions will break especially the forums. 9.1.2 sites will still function but with a lot of errors which seem to come from nowhere. The culprit is when a webhost upgrades PHP, MySQL, and Apache.

For example, PHP functionality for dynamic signatures will break in PHP5 because ImgPNG compression is now 1-9 instead of 1-100. It's highly unlikely that anyone was using compession 9/100 with PHP4 because the image would be extremely degraded in quality. That's just one of many examples of code changes needed in PHP5. The above example does not affect DragonflyCMS directly but it's just an example of what can affect your code in making the PHP5/MySQL5 transition.

World
Posted by Devon Monday, February 23, 2009 (07:55:24) Read More... (1.47 KB) | comments? | Printer Friendly Page  Send to a Friend | Score: 0


1 2 3 ... 29 30 31
>


RSS-News
RSS-Downloads
RSS-Forums
RSS-KnowledgeBase
Valid CSS!
Valid HTML 4.01!

Site Search | Support | Contact | Payments | Link to Us
All TCD logos and trademarks in this site are property of TreasureCoastDesigns.com
Interactive software released under GNU GPL, Code Credits, Privacy Policy
TCD_Natural © T.C.D.