If changing the CSS of your website is something you'd prefer not to do, we offer ad-hoc support tickets that are available in 15 minute blocks through our main business site — you can read more about that here. Generally though that is based on our staff being able to access the server in question, so if you're using a private development system (like WAMP, MAMP etc) you will probably have to do it yourself.
Having said that adding custom CSS to a Joomla template isn't that difficult, it really depends your template as to where the CSS should go.
If your template is based off the Gantry Framework created by RocketTheme then you will need to create a CSS file in the templates CSS folder as described here and add you custom CSS to it.
If your template is based off the T3 Framework you will need to follow these instructions.
If it's just a standard template you will generally want to add it to the end of the main `
The "JUser: :_load: Unable to load user with ID: XXX" is a common Joomla! 2.5 error for users that have upgraded a website from Joomla! 1.5 using the JUpgrade component (although it can also occur with out using JUpgrade). You can find pages of examples on Google from just the past year. However it can also occur if you have deleted a user that has checked out an item.
Basically it means that the item in question (it can occur with articles, modules menus, EasyTables or literally anything else in Joomla) has a user ID associated with it that doesn't exist in the website user database.
The good news is that it can be fixed, the bad news is that it could take a long time if you have a lot of content that is assigned to the old user ID.
Generally you will only see the message in the /administrator section of your Joomla! website when looking at one of the manager screens that shows you a list of items and their check out status (i.e. the padlock icon) or other user information about an item (like who created it).
To fix the problem check the item in if it's checkout to the non-existant user, or if it's created by a the non-existant user edit the item and change the creator. Of course you can also use Joomla!'s Global Check-in function to do a mass checking of items, but for invalid creator ID's it's a manual job. As we said, this could take a long time if you have a lot of content created with the old user ID.
If you have some expertise with SQL you could simply update all of the creator ID's with an appropriate script, but that is something that could wreck your site if you're not carefull, so we won't be putting those instructions up here.
Our publically available open source software (i.e. that found on the See People Softare website) is generally the result of a happy overlap with the needs of a commercial client of CPPL. Generally they have a need and the software we build for them is sufficiently general enough that it has public application.
- EasyTable for J! and EasyTable Pro!
- EasyStaging and EasyStaging Pro!
- EasyGitHub Include
- CommWeb for VM2
- ANZeGate for VM2
- NAB Direct for VM2
- NAB Direct for JoomDonation
- NAB Direct for AkeebaSubscriptions
- CommWeb Direct for AkeebaSubscriptions and
- ANZeGate for AkeebaSubscriptions
all came from.
New features are added (and therefore new versions created), as a result of:
- A Commercial development clients needs a specific feature added (e.g. Joomla! 3.5.x compatibility).
- If a See People client has a feature they need now, CPPL will add it for a fee.
- If the feature is already on the roadmap for that product and this simply brings it forward the fee is usually discounted in inverse proportion to how far forward it's being brought.
- If the feature isn't of use to the wider community, it won't generally make it into the public distribution and won't be subject to any discount.
- One of our developers has some "downtime"
- In this case the developer picks a feature from the products future feature list that they feel they can implement in the time they have availalbe and start work on it.
- Sometimes, they don't get it finished on the first go.
- The particular product has generated enough subscription revenue to pay for a feature on the list and we can assign a developer to implement it.
Why is it this way?
To put it simply, we have to pay staff, we have to feed our kids... just like you we need to make a living.
While people love and use our software on thousands and thousands of websites (going on the version check logs) the percentage that actually subscribe rather than downloading unofficial versions is very low (we estimate in excess of 98% of the Pro copies of our software are unofficial). Recently an *unofficial version* of EasyTable Pro! was used by someone to distribute a nasty payload, but what can you expect when you download software from dodgy Russian websites.
Visibility of the software on the JED also remains very low. Very few subscribers actually even vote for or leave a review for our software on the Joomla! Extensions Directory (far less than 1% in most cases), and actual subscribers are less than 1% of actual users.
While we love open source software, what really pays the bills around here is the commercial, proprietary work.
So, can you guess where this is going?
We can't make a hard and fast pronouncement about product X's release schedule as we generally don't know. We will tend to talk about products that are actively undergoing work (i.e. someone is pay for), but only when it is close to being released to the public.
Joomla!'s New Development Cycle
The Joomla team are aiming for a fixed release cycle. Every six months, the Joomla! Project tries to release a new minor or major version of Joomla! (Since version 1.7 they have been pretty close on meeting these self-set goals).
A key factor in this new cycle is that the "point zero" versions (e.g. Joomla! 3.0) are allowed to introduce changes that break existing software, and the code base is allowed to change until the "point
two three" version before being locked down in the final "point five" LTS (Long Term Support) version (e.g Joomla! 2.5).
This is a good thing™, in that it allows Joomla! (the CMS) to advance at a predictable pace and it means it won't stagnate like the long lived Joomla! 1.5 version did. The only downside is for small software developers and niche extensions that can't update as frequently as Joomla! breaks things.
In light of this cycle and the way our extensions come into existence and the ways they are funded most extensions are only going to be available for the LTS versions of Joomla! and generally in-line with the needs of the clients of CPPL.
If you're registered for the See People Software website then you're registered for the forums. To access the forums you will need to login first.
If you're not registered or logged in you can click on the "Register" menu in the main menu bar.
Due to the high volume of pornographic spam we have changed the forum registration process so that new registrations require administrator approval. You can read more about it in this forum thread.
How do I login?
To login to the forums you need register with the website. You can do this either from the Registration page or from any other pages in the website you can click on the "Register" menu item in the main menu bar.
How do I post to the support forums?
After logging in to the site, navigate to the forums section of the website.
If you're a current Support Subscriber you will see the additional "Subscribers Forum" as shown in this screenshot:
Click on the name of the forum you want to post in. Then once in the forum click on the "New Post" button as shown in the image below of the "Support Subscribers" forum.
When asking this question most users forget that their web server is a multi-user system.
The configuration for the
memory_limit of PHP running as an Apache module to server webpages has to take into consideration how many Apache process you can have at the same time on the machine (this is controlled the
MaxClients configuration option for Apache).
MaxClients is 100 and you have 2,000 MB or RAM, a very quick calculation will show that you should not use more than 20 MB *(because 20 MB * 100 clients = 2 GB or RAM, ie the total amount of memory your server has)* for the memory_limit value.
Add to this other software running on the server, like MySQL, mail servers, the operating system and Apache itself and you can easily run out of memory and have odd results.
When using the Joomla CMS memory usage can increase dramatically with a large number of extensions installed and a large amount of data to be managed.
Signs that you may be experiencing memory limit problems include
- pages not rendering completely
- components or extensions reporting memory errors
- partial content being returned and
- page timeouts on pages that use a lot of components/extensions.
The quickest way to solve a problem is to look for existing solutions. On this website that means the following:
- Read the articles about your particular software.
- Read the FAQ (Frequently Asked Questions) - we have lots of answers in there.
- Search the forums for error messages or appropriate keywords.
- Do not use the Forum's Private Message (PM) function - we don't check them
- Make sure you post in the "Subscribers" forum, they're actively monitored unlike the "Community" forums.
- Check your website is working correctly by turning on Joomla's DEBUG mode and setting error reporting to a suitable level (e.g. "Development")
If none of those help then login to the appropriate forum and post your question. When you post your question don't forget to provide context so people can provide the best answer - start with the things suggested below.
Free Software Users
If you have problems using any of the software on this website please use the FAQ's and user forums to try and resolve it.
Don't send us an email as this will not help you get an answer and it won't help other users who may be experiencing similar problems. Don't use the contact forms either as they go to sales. Email and contact forms only go to one address whereas our support forums are seen by many people making the chances of you getting a prompt answer much higher.
Read the FAQ's, search the forums and if you can't find an answer then post a question on the forums, remember the things suggested below.
Current Support Subscribers
If you're a paid support subscriber please use the subscribers forum which is monitored by our support staff. If it is urgent in addition to posting to the subscribers forum use our contact form, especially if it's out of normal business hours. Remember, the more information you provide us the more likely it is we'll be able to solve the problem, start with the things suggested below.
If you don't have a paid support subscription then you will have to use the community forums which aren't monitored by us but which we do visit occasionally.
When posting a question about any problems you may be experiencing the following things will be useful:
- version details for
- our software and
- things like Joomla, PHP, mySQL etc
- browser name, version & platform (eg. Firefox, Safari, Chrome and which platform Mac/Win)
- try alternative browser to see if it's a bad browser behaviour/plugin issue. (90% of errors come from old versions of IE on Windows.)
- URL showing the problem
- if no URL is available then a screen shot
- any error messages (please cut and paste them out of your browser into the forum, don't try to remember them and type them in.)
- turn on Joomla's debug mode and error reporting and then try to create the error again (also look at the debug output and copy and paste any relevant sections into your forum post.)
Don't use the Forum software's Private Message function (PM's)
This can't be said enough - don't use the PM function, it goes to one person only whereas we have multiple people watching the forums. We don't have the same people logging in every day so your PM may not be seen until they come back from holidays, a business trip or a pilgrimage!
Changes in forum group memberships can sometime cause login issues due to out of date cookies or cached information held by the browser.
If you have a problem logging into the forums please try the following suggestions to see if any of them resolve the problem:
- logout & then click the link Delete all board cookies. (It's also on the bottom of the main forum page). Login and see if that worked.
- Logout then try to login from the websites home page
- If you use your browser to automatically save and fill out passwords try turning that off and logging out and then back in.
- Try a different browser, ie. if you normally use IE7 try Firefox or Safari to login with.
- Finally if none of them have worked try resetting your password using options under the "Register" menu.
Install Suceeded & Failed? ( "couldn't delete file xxx_xxxxxx.xxx" )
Sometime Joomla will report an error during the installation of a component, plug-in or module, in these cases it often reports that the installation both suceeded and failed to move/delete one or more files. This error is actually the Joomla! Install mechanism reporting that it didn't have permission to delete the old file before moving the new one in place, i.e. your server isn't setup correctly. To correct this you will need to fix the file permissions for the old files or manually delete the old files — in either case please make absolutely sure you know what you're doing as you could break your website by deleting the wrong file or make it vunerable to hackers if you change the wrong file permissions.
You can read more about File permissions on docs.joomla.org:
- Where can you learn more about file permissions?
- What are the recommended file and directory permissions?
Install Failed ( "couldn't move file xxx_xxxxxx.xxx" )
Sometime Joomla will report an error during the installation of a component, plug-in or module, saying that it failed to move one or more files. This error is usually the result of the /tmp directories not being setup correctly (this can often happen after moving a site or when using an IIS server). To correct this you will need to check the gobal configuration and ensure that the settings for the temporary directory are correct.
You can read more about installing extensions on docs.joomla.org:
JFolder :: files: The path is not a directory.
During installation of new or updated software you can get this message. While the message is a little obscure in it's wording it generally means that Joomla! file handling system can't find the directory listed in the message.
JFolder::files: The path is not a directory. Path: /home/userac/public_html/administrator/components/com_easystagingpro
In the example message above the message literally means the Joomla!'s file handling functions can't find the directory com_easystagingpro, as this occurred during the install process it usually means that Joomla!'s com_installer function could not create the directory in the /administrator/components/. Generally in these cases it means that the file permissions for the /administrator/ directory have been changed to prevent changes (e.g. certain admin tools that provide enhanced Joomla! security will change the permissions on /administrator).
You can quickly check if Joomla! has write access to /administrator by selecting Site->System Information->Directory Permissions. In the directory list administrator/components should be Writable, if it is Unwritable then you will have to change it's permissions. If you're not sure how to do this please as your host or web developer.
If the directory is showing writable but you still get this message the next step is to look at any security software you have installed that may be affecting the process — typical causes are .htaccess files that have been added to /administrator to restrict access. You will need to follow your security softwares instructions and temporarily turn off the protections or make allowances for com_installer.
The other situation where we've encountered this is where clients have installed 3rd Party templates  and extensions that have mistakes in their XML files, in these cases you will need to contact the
I get this error when i try to install XXX: Error building admin menus
This is actually a common issue reported by Joomla! 1.6/1.7/2.5 users, and is caused by a problem the com_installer component (the part of Joomla! that actually installs extensions, templates etc).
The component actually installs properly, but the back-end access menu items are not visible. This can be easily resolved by re-installing the software.
N.B. This can occur after an update as well as on a new installation.
When PHP runs out of memory while running a large application ( like a CMS with lots of bells and whistles in a dynamic template ) you will see errors with the key phrases "Fatal Error" and "Allowed memory size of XXXXXX bytes exhausted".
Contributing causes include:
- a comparatively low memory_limit setting compared to the work you're asking the server to do.
- 64M is considered normal for dynamic eCommerce and CMS driven websites
- asking the server to process/unzip/compress a very large file
- over-loading your CMS/eCommerce/Web App with lots of extensions
The easiest solution is to increase PHP's memory_limit - depending on your hosting environment there are a variety of ways to do this - click here for a Google Search to get you started. If you have no idea how to do this the best solution will be to talk to your website provider.
Ok, first up file uploads for those that aren't clear are the following sorts of things:
- adding a picture on your computer to an aritcle (you upload the image file)
- installing a new component/plug-in/temple (these items are uploaded to your website)
- uploading data to a custom component (like PDF & JPGs to Flipbook or CSV files for use in EasyTable)
A file upload is literally the transmission of data from your computer to the web server that your website runs on.
Unlike normal activities like editing text or creating menus which send small amount of data to specific fields, file uploads send much larger amounts of data in a pre-packaged format. Files that can be uploaded can be a variety of types, common ones include:
- ZIP/GZ (compressed data files)
- JPG/PNG/GIF (images)
- SWF, AVI, MOV, MP3, MP4 (Flash, audio & video)
As file uploads are usually self contained packages they have to be treated with much more care. As such hosting services and most CMS software have limits on what can be uploaded. Some file restrictions that you might encouter include:
- no executable files
- to prevent virus transmission
- no script files
- like PHP
- Perl etc
- done to prevent hacking of the website
- no files over a specified size
- typically ranges from 0Mb to a user configurable number
- usually the better the host the bigger you can go
Generally the one that causes the most trouble with a CMS website is the maximum file size you're allowed to upload. In Joomla this is controlled by a PHP variable called upload_max_filesize.
The value this variable has is usually controlled by your hosting service at the cheap end of town and by yourself in the nicer hosting services.
What's my upload_max_filesize?
The default PHP value is 2M (2 megabytes), most hosting providers change it from this either up or down. There are a variety of ways to find your websites value:
- in a WHM/CPanel system
- Open the PHP Configuration icon and look for the line highlighted in image below.
- in Joomla! 1.5
- Select the menu "Help" -> "System Info" -> "PHP Information"
- Scroll down to the end of the PHP Core section to find the value of upload_max_filesize
- in Joomla! 2.5
- Select the menu "Site" -> "System Information" -> "PHP Information"
- Scroll down to the end of the PHP Core section to find the value of upload_max_filesize
- using a test PHP file
- create and upload a phpinfo() file to your server (if you don't know what this means don't do it)
- contact your hosting provider
How can I change my upload_max_filesize?
There are a range of ways including using your WHM access to change it, setting a php.ini file up and finally calling your hosting provider. We recommend you read about it because you can cause problems if you do it the wrong way.
Please beaware the changing your upload_max_filesizecan cause problems if you make it greater than or equal to your post_max_size (another PHP setting). Apart from the file you're uploading you need to allow room for the other form elements, so the size of the file + the size of other form elements (text fields, drop down items, selection boxes etc) must be less than your post_max_size.
As a starting point here's a Google search for you.
JInstaller::install: Failed to copy file
This is a common message that usually results from file or directory permissions on the hosting environment. The easiest way to check if the problem is being caused by permission issues is to use Joomla's built-in "System Info" option in the Help menu.
When you select the "System Info" option, then you are presented with a range of information tabs about your website and the Joomla installation.
As shown in this screenshot one of the tabs you can choose is called “Directory Permissions’ - for you to be able to successfully install components, plug-ins and templates then all of these directories listed should show as “Writable”. If they don't (the directory permission show as “Unwritable”) you will need to change the permissions for your Joomla installation.
How do I change the permissions for my Joomla installation?
First up - changing permissions can be dangerous. If you don't really understand permissions and ownership get the technical support staff at your hosting service to fix the permissions for you. Specifically the webserver will need read and write access to the Joomla installation, it will also need ownership or membership of a group that owns the websites directories.
Changing permissions will depend on your website hosting setup.
- If your host provides cPanel access you can use the “File Manager” to change the directory permissions.
- If your host provides Shell access you can use chmod and chown to set the permissions to 755 and the group owner to the webserver's group
- If your host has a custom control panel specific to them you may be best off opening a support ticket to get the problem resolved.
It's not my Permissions!
If your permissions are all showing as writable then the next most likely cause is that your Joomla installation is version 1.5.10 - a typical error in this case will look like this:
'/website/tmp/install_38bd786260b81/SomeComponent.install.php' does not exist.
Component Install: Could not copy PHP install file.
Joomla 1.5.10 had a slight change which causes this error to be thrown, it has been resolved in all subsequent versions. The simplest solution is to upgrade to a latter (and more secure) version of Joomla 1.5.
It's not my Permissions and it's not Joomla 1.5.10
If you've gotten this far and it hasn't worked the final thing to check is your “Global Configuration” for “FTP Settings”. If you have FTP enable/disbaled, flip the FTP option (set it to the opposite setting) and try again.
In our experience with our software/templates and with Third Party products these steps have resolved 99% of installation issues via the Joomla Installer.
See People Software is a brand of Craig Phillips Pty Ltd (CPPL).
CPPL's core business is:
- software development for:
- iPhone applications
- Joomla Extensions
- devloping new websites using Open Source solutions like Joomla!
- on-server configuration & support
- public/intranet website
- Managed Web Services
- Managed Websites
- Managed Services
- Service Monitoring
The best way to get us involved is to drop us a line via our contact form!
For support for our Software please see this FAQ
|EasyTable for J!||1.0.5a
(Click to download)
(Click to go to the download area)
|EOL — See below.|
1.4.0 is feature complete and failing any major issues will be the last version before the 1.5.0 Beta Release.
Please note that the version 1.3.0+ line is for Joomla! 2.5.18+ and 3.3.2+, for Joomla! 1.5 you must use the 1.0.0 version.
Please note that the version 1.2.0 line is for Joomla! 2.5, for Joomla! 1.5 you must use the 1.0.0 version.
Current version release notes.
1.0.0 is now EOL — See below.
(Click to go to the download area)
|This product is only to be used by experienced website developers, it is not intended to be used by people without a technical understanding of how Joomla!, MySQL and Rsync work.|
|EasyGitHub Include||1.0.0 for
1.0.0 for (Click to go to the download area)
(Click to go to the download area)
Aug. 2012: In line with the end of life for Joomla! 1.5, support for Joomla! 1.5 compatible versions is no longer available.