Reprinted from TechBulletinNews 2011
The legal altercation between WPblogmatic, Inc., Bert Tassoni, Andrew Hall and the producer of Buildablogstore (BABS), BloggingMaster LLC, has erupted over a PHP script, which uses WordPress as its main operating system. WordPress is open source code. WordPress is distributed under the GNU Public License, ensuring that the source code is usable free of charge to all involved users with the right to adjust as required.
The claims made by BloggimgMaster LLC and Peter Bresko, against WPblogmatic Inc., Bert Tassoni and Andrew Hall proved to be false and malicious and have resulted in a substantial Law Suit against both BloggimgMaster LLC (also known as BABS or BABS Pro) and Peter Bresko. The Superior Court Legal Action brought by BloggimgMaster LLC against WPblogmatic Inc., in 2010 has since been quashed and BloggimgMaster LLC has filed for Chapter 11 protection.
Both WPblogmatic and Buildablogstore (BABS) use a modified variation of WordPress to effect installation and setup. A specific Autoblogging plug-in is used to affect the management interface and the setup of affiliate posts.
The plug-in is constructed to automate the production of blogs and create posts of brands from a choice of affiliates like eBay, Amazon, Overstock, commission Junction, etc.
There is a tendency to assume that there are two elements: WordPress, and the active Plug-in. But they do not run by itself. They operate as one cohesive unit. They may not even operate in a sequential order. WordPress begins up, WordPress tells the plug-in to run its functions and register its hooks and filters, then WordPress runs a handful of queries, then WordPress calls the applicable plug-in PHP file, and afterwards the plug-in hooks into the queried WordPress data and uses WordPress functions to mobilize it, and then WordPress shuts down and finishes the request. On that obvious view, it looks like a multi-layered pastry. But the integration is even more amalgamated than the pastry analogy suggests.
It is erroneous to think of WordPress and a plug-in as different entities. As far as the code is concerned, they act as one relevant unit. The plug-in code doesn’t sit-on-top of WordPress. It is within it, in countless different locations, with diverse interdependencies. This creates a web of communal data framework and code all contained within a assembled memory space.
What this basically means is that a plug-in developer would need to completely remove any and all WordPress code before being able to lodge a copyright protection for the design of their plug-in. Plug-in code originally derives from WordPress and thus must be licensed under the GNU General Public License if it is distributed.
Both Mr. Bert Tassoni and Mr. Andrew Hall returned our phone call and stated that WPblogmatic Inc., early in 2010 acquired the GNU open source code online and spent considerable money employing its own American based coders to expertly enhance the code, create a absolutely new management interface and affirm the product genuinely worked.
Mr. Bert Tassoni and Mr. Andrew Hall further claimed that the end result is the best and most stable Autoblogging tool ever put on the market. WPblogmatic certainly has succeeded where Buildablogstore failed!
Whilst both PHP scripts use the same WordPress code as a foundation, the performance and management interface are completely different claim Tassoni and Andrew Hall. WPblogmatic drastically redesigned the product incorporating an open source code readily offered online.
Developers of Themes or Plug-Ins for WordPress should take note of this case study.