TDOC Support
Getting Support
There are two items in the TDOC Stable for Joomla. Both are very simple - they are:
- TDOC Facebook Display - mod_tdoc_fbk - a module which is designed to show a facebook page in a sidebar, and
- TDOC Google Map - {tdocgmap} - a plugin which is designed to show one or more kml files rendered in a GoogleMap by Google in your article or category.
We upgraded the tdocplus.co.uk domain to https: This has NOT broken the upgrade links for either of the two TDOC extensions.
Please email
- A description of the problem. Please include yur Joomla Version, and PHP Version.
- The address of your web site - so I can see the problem.
Google Map - Code Version 5.5
Development Update - 1st May 2026 - Email from GoogleMaps
Hello Google Maps Platform customer,
This communication informs you about the upcoming deprecation of the KmlLayer class in the Maps JavaScript API and provides the necessary resources for transitioning your applications to modern alternatives.
What you need to know
The KmlLayer functionality in the Maps JavaScript API will no longer be supported. This feature is deprecated as of today, and will be made unavailable in version 3.66 of the Maps JavaScript API, releasing in August 2026. You can keep using the KML Layer until May 2027, by explicitly using Maps JavaScript API versions that still support it.
Facebook Display
3rd May 2024 - With assistance form Robbie J, the module is now Joomla 5 Compatible at version 5.3.1.
5th January 2021 - The bug in Google Chrome is now fixed for Windows 11,10, and 8.
Sadly Chrome no longer upgrade for Windows 7 - so that remains broken.
We upgraded the tdocplus.co.uk domain to https: This has NOT broken the upgrade links for the extension - which work fine.
JCE Exploit 3rd June 2026
Google AI reports as follows:
The critical Joomla Content Editor (JCE) exploit (tracked as CVE-2026-48907) is not attributed to a single named hacker or group. Instead, it is actively being weaponized by unknown, automated threat actors and cybercriminal syndicates.
Because the security gap is highly severe with a CVSS score of 10.0 and public exploit code exists, threat actors are using automated scanners to hunt for unpatched sites.
How the Exploit Works
- The Flaw: The JCE plugin fails to enforce access controls during the profile import workflow.
- The Attack: Unauthenticated threat actors (meaning anyone with zero login credentials) can remotely create new editor profiles on your site.
- The Impact: This allows attackers to bypass security filters and upload arbitrary PHP files, giving them complete remote code execution (RCE) and full control of the web server.
How to Protect Your Site
- Update Immediately: The vulnerability impacts JCE versions 1.0.0 through 2.9.99.4. Update to JCE Pro version 2.9.99.5 (or higher), which patches the flaw.
- Check for Indicators of Compromise: Updating closes the entry point but does not clean a site that has already been compromised. Look for unauthorized users and rogue PHP files in your web-accessible directories.
- Monitor Official Alerts: The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has added this to its to its Known Exploited Vulnerabilities (KEV) Catalog due to the extent of the attacks.
You can read more about the flaw in the technical breakdown by SonicWall.
Other stuff
What JCE have said is here: https://www.joomlacontenteditor.net/news/jce-security-update-and-a-free-patch-for-older-sites
What happened to me:
- Problem with upgrading to Joomla 6.1.2. "administrator/components/com_joomlaupdate/extract.php" was inacessible..
- This then morphed into a collapse of the sites css - what a mess.
- Upgraded to 6.1.2 Ok apparently BUT the menu and all links then went.
- On JCE found that four new editor profiles had been added. Removed all of those . . . but the problems persisted.
- Found the "tmp" directory was full of stuff on two more sites.
- The solution to that was to empty, and rename it to "temp" - not forgetting to update the path.
- Admin Tools was unable to find and fix any of these.
- On one site the daily malware and virus scan picked up four files in a "tmp" directory
- 929929.php, ...svg, ...phtm, ...pht
- Cause: "file.put.contents.php.base64.decode"
What you need to do:
- Always take a backup using Akeeba Backup.
- Download the backup to your local pc
- Always immediately restore from the backup and check all is Ok.
- To recover I did the following:
- Deleted the site's database. Created a new database.
- Deleted everything in the public_html directory.
- Used a good backup, and updated it to 6.1.2, and updated all extensions.
- Uploaded that and ran kickstart.php. All went well and two sites restored.
- Made a backup, downloaded and tested that.
WAMP and Google Maps
This is a strange bug.
When running WAMP locally, by default it presents what it finds using "localhost" as opposed to "127.0.0.1".
The only difference is that the TDOC Google Maps plugin does not like the "localhost" option. So:
- This works: http://127.0.0.1/LP_510_c/information-on-the-park/printable-maps/walks-stag-current-course,
- This fails: http://localhost/LP_510_c/information-on-the-park/printable-maps/walks-stag-current-course, with the following message
Oops! Something went wrong.
This page didn't load Google Maps correctly. See the JavaScript console for technical details.
The JavaScript console states:Google Maps JavaScript API has been loaded directly without loading=async. This can result in suboptimal performance. For best-practice loading patterns please see https://goo.gle/js-api-loading js:236:281
Google Maps JavaScript API error: RefererNotAllowedMapError https://developers.google.com/maps/documentation/javascript/error-messages#referer-not-allowed-map-error js:144:68
Uncaught (in promise) TypeError: a.getDiv() is undefined
vna https://maps.googleapis.com/maps-api-v3/api/js/57/7/map.js:2
sb https://maps.googleapis.com/maps-api-v3/api/js/57/7/map.js:133
And you can make of that what you will !
TDOC Gmap with "page breaks"
The use of Page Breaks breaks TDOC Gmap