Your IP : 216.73.217.176
home/bechata/mp/wp-content/plugins/shortcodes-ultimate/languages/readme.txt 0000666 00000000205 15175314643 0023233 0 ustar 00 Translations have moved to
https://translate.wordpress.org/projects/wp-plugins/shortcodes-ultimate
Thank you for your contribution.
home/bechata/mp/wp-content/plugins/wp-google-maps/readme.txt 0000666 00000242501 15175415674 0020141 0 ustar 00 === WP Google Maps ===
Contributors: WPGMaps, NickDuncan, CodeCabin_, DylanAuty
Donate link: https://www.wpgmaps.com
Tags: google maps, maps, map, map markers, google map, google maps plugin, wp google maps, wp google map, map plugin, store locator, google map plugin, map widget, open layers, elementor map
Requires at least: 3.5
Tested up to: 5.8
Requires PHP: 5.3
Stable tag: trunk
License: GPLv2
The easiest to use Google maps plugin! Create a custom Google map or Store Locator with high quality markers containing categories, descriptions, images and links.
== Description ==
The easiest to use Google Maps and Open Layers Maps plugin!
Add a customized Google map or Store Locator to your WordPress posts and/or pages quickly and easily with the supplied shortcode. No fuss. No iFrames and super easy to use! Perfect for contact page maps, routes, maps showing delivery areas and any other use you can think of!
While the free version of WP Google Maps allows you to create a Google map with as many markers as you like, the Pro version allows you to do so much more!
Create Elementor Maps and map blocks easily with our WP Google Maps Elementor map block integration, straight out the box!
The [WP Google Maps Pro Version](https://www.wpgmaps.com/purchase-professional-version/) version allows you create custom Google maps with high quality markers containing locations, descriptions, images, categories, links and directions.
= Lite Version (Free) =
* The most popular Google Maps plugin on WordPress
* Choose between Google Maps or Open Layers Maps
* Super easy to use, no coding required!
* Create as many map markers as you need by simply typing in the address
* Responsive maps
* Elementor Map block
* Edit your map markers with the click of a button
* 9 popular map themes to choose from
* Create or add your own map theme
* Drag map markers to an exact location
* Add a map block to your page
* Google Maps Streetview supported
* UTF-8 character support
* Map widget functionality
* Full screen map functionality
* Support for localization
* Choose from four Google maps types: roadmap, terrain, satellite and hybrid
* Define your own width, height and zoom level for your map
* Add animations to your map markers!
* Store locator functionality
* Restrict a store locator search by country
* Add Polygons to your Map
* Add Polylines / Routes to your map
* Create a map in less than a 30 seconds!
* Right click to add a marker to your map
* No advertising or links
* Google Maps Autocomplete
* Google Maps Transport Layer
* Set the max zoom level for your map
* Serve your map marker data via your database or an XML file
* Compatible with caching plugins
* Compatible with Cloudfare
* Latest Google Maps API
* Latest OpenLayers API
= Professional Edition =
* Create multiple maps!
* Allow your visitors to get directions to your markers.
* Add descriptions, links and images to your map markers.
* Add categories to your map markers
* Filter markers by category
* Mashup multiple maps
* Add different marker icons, or your own icons to make your map really stand out!
* List your map markers in the four ways; basic list, basic table, carousel, advanced table
* Allow visitors to use their map location as the starting or ending point for the directions
* Choose between the Default Google Maps Infowindow and the new Modern Infowindow
* Export/Import your markers to a CSV file for quick editing.
* Link Fusion tables to your Google Maps
* Show your visitor's location on the Map
* Import KML/KMZ files to your map
* More advanced options for the Store Locator
* Allow users to use their map location for the store locator
* Store locator search by category
* Hide all map markers until a store locator search is done
* Move your marker list inside the map window
* Multiple map widget functionality
* Add retina-ready map marker icons
* WordPress Network friendly
* Get the [WP Google Maps Professional Edition](https://www.wpgmaps.com/purchase-professional-version/) for only $39.99
= Translations =
Get a free copy of the WP Google Maps Pro version in exchange for translating our plugin!
* English - default
* Russian (Alexandra Bondareva)
* German
* French (Arnaud Thomas)
* Polish (Michal Kotnowski)
* Finnish (Johanna Joutti)
* Dutch (Jan Wind)
* Hebrew (Gal Dotan)
* Danish (Patrick Jepsen)
* Italian (Tommaso Mori & Massimo Bregani)
* Croatian (Sven Kopun)
* Greek (Konstantinos Koukoulakis)
* Romanian (Cosmin Stroe)
* Spanish (Carmelo Villegas Cruz)
* Portuguese (Jose Antonio Ribeiro)
* Brazilian Portuguese (Roberto Costa)
* Turkish (Suha Karalar)
* Swedish (Martin Sleipner)
* Bulgarian (Lyubomir Kolev)
* Indonesian (Neno)
* Lithuanian
* Czechoslovakian^
^Language file needs to be updated
= Demos =
WP Google Maps Lite
* [Basic Google Map with Markers](https://www.wpgmaps.com/demo/basic-google-map-with-markers/)
* [Store Locator](https://www.wpgmaps.com/demo/wp-google-maps-store-locator-free-version/)
* [Polygons & Polyines/Routes](https://www.wpgmaps.com/demo/polygons-and-polylines/)
* [Google Maps Transit Layer](https://www.wpgmaps.com/demo/google-maps-transit-layer/)
* [Google Maps Traffic Layer](https://www.wpgmaps.com/demo/google-maps-traffic-layer/)
* [Google Maps Bicycle Layer](https://www.wpgmaps.com/demo/google-maps-bicycle-layer/)
WP Google Maps Pro
* [Google map with advanced markers](https://www.wpgmaps.com/demo/basic-map-and-markers/)
* [Marker listings - Simple](https://www.wpgmaps.com/demo/list-markers/)
* [Marker listings - Advanced](https://www.wpgmaps.com/demo/map-with-markers-listed-below-advanced/)
* [Google Maps Directions](https://www.wpgmaps.com/demo/directions/)
* [Responsive Map](https://www.wpgmaps.com/demo/responsive-maps/)
* [Marker Categories](https://www.wpgmaps.com/demo/marker-categories/) (Filtering)
* [Advanced Store Locator](https://www.wpgmaps.com/demo/store-locator/)
* [WP Google Maps Editor](https://www.wpgmaps.com/demo/screenshots-back-end/) (Back-end Screenshots)
* [Visitor Generated Markers](https://www.wpgmaps.com/demo/visitor-generated-markers/) - (WP Google Maps VGM Add-on)
* [Custom Map Styling](https://www.wpgmaps.com/demo/custom-map-styling/) (WP Google Maps Gold Add-on)
= Documentation =
* [Installing WP Google Maps](https://www.wpgmaps.com/documentation/installing-the-plugin/)
* [Creating your first map](https://www.wpgmaps.com/documentation/creating-your-first-map/)
* [Google Maps mashup (Pro)](https://www.wpgmaps.com/documentation/advanced-map-options/map-mashup/)
* [Exporting and importing map markers (Pro)](https://www.wpgmaps.com/documentation/exporting-and-importing-your-markers/)
* [Changing the Google Maps language](https://www.wpgmaps.com/documentation/changing-the-google-maps-language/)
* [Create a google map and marker using custom fields (Pro)](https://www.wpgmaps.com/introducing-maps-by-custom-fields/)
* [View all documentation](https://www.wpgmaps.com/documentation/)
= Troubleshooting =
* [My Google Map is not showing on my website](https://www.wpgmaps.com/documentation/troubleshooting/my-map-is-not-showing-on-my-website/)
* [My markers are not showing](https://www.wpgmaps.com/documentation/troubleshooting/my-markers-are-not-showing-on-my-map/)
* [View all troubleshooting articles](https://www.wpgmaps.com/documentation/troubleshooting/)
== Installation ==
= First time WP Google Maps user =
Thank you for choosing WP Google Maps! In order to create your Google map, simply activate the plugin and click on "Maps" in your left navigation menu.
Once the WP Google Maps page loads, set the options for your map (height, width, map type, zoom level etc) and then use your mouse to drag your Google map to your desired location and press the "Save map" button.
Copy and paste the shortcode into your post or page and WP Google Maps will automatically create the map on your page using the settings you chose above.
= Adding your first map marker =
To add a marker to your Google map, scroll to below the map in your admin section and enter the address or GPS location in the Address input field. Click "Add Marker" and WP Google Maps will add your marker to the address you specified.
= Setting up a Google Maps Store Locator =
In order to make use of WP Google Maps Store Locator functionality, simply click on the "Store Locator" tab in the map creation page and select "Yes"
== Frequently Asked Questions ==
= How do I get WP Google Maps Pro? =
Simply visit https://www.wpgmaps.com and purchase the WP Google Maps Professional Edition for $39.99 once off. Free updates and support included forever.
= I've installed the plugin, now what? =
Once installed and activated, a link should appear in your left navigation panel within your WP-ADMIN section. Click on the "WP Google Maps" link and follow the on screen instructions.
= How do I put a Google map on my page/post? =
In order to show your custom Google map on your page or post, simply copy the shortcode supplied and paste it into your page or post. WP Google Maps will automatically configure the map to the settings you selected in the map edit page.
= How do I add a map widget to my widget area? =
To add your map to your widgets area, simply go to Appearance->Widgets and drag the "WP Google Maps" Map Widget to your sidebar. You then edit the map widget to reflect the correct map.
== Screenshots ==
1. The "Lite" version of WP Google Maps.
2. The "Pro" version of WP Google Maps.
3. WP Google Maps Pro version: Users can get directions to your map markers
4. WP Google Maps Pro version: Add custom markers to your Google map
5. WP Google Maps Lite version: General settings page
6. WP Google Maps Pro version: General settings page
7. WP Google Maps Pro version: InfoWindow settings page
8. WP Google Maps Pro version: Advanced Google map options.
9. WP Google Maps Pro version: Map marker listing options
10. WP Google Maps Pro version: Export/Import your map markers
11. WP Google Maps Pro version: Responsive carousel map marker listing
12. WP Google Maps Lite version: Store Locator Settings
13. WP Google Maps Lite version: Store Locator Map
14. WP Google Maps Lite version: Map Widget
15. Select a theme for your map, or choose a theme from our theme library
== Upgrade Notice ==
= 8.1.13 =
Please update to 8.1.13 or above to ensure you are using the latest security enhancements.
= 8.1.12 =
Please update to 8.1.12 for PHP8 compatibility.
= 8.1.4 =
Please update to 8.1.4 to ensure a smooth user experience.
= 8.0.26 =
Please update to 8.0.26 or above to ensure you are using the latest security enhancements.
= 7.11.19 =
Please update to 7.11.18 or above to ensure you are using the latest security enhancements.
= 6.3.15 =
Please update your WP Google Maps version to 6.3.15 to ensure you are using the latest security enhancements.
== Changelog ==
= 8.1.15 - 2021-09-01 =
* Fixed issue where Avada Alert icons would not show due to our icon libraries loading in post/page editor
* Remove Klokantech 3D tileserver as this does not appear to be supported (OpenLayers)
* Added MapTiler Streets, Outdoor, Pastel, Basic (OpenLayers)
* Added indicator for most tilesets that require an API key (OpenLayers)
* Added preinit event delegate
* Added global initMaps method
* Added global onScroll method
* Added core integration for Real Cookie Banner integration
* Updated it_IT translation file (Thanks to Alessio Cornale)
* Updated Stamen Watercolor tileset to point to HTTP host (OpenLayers)
* Updated OpenPtMap tileset to point to HTTP host (OpenLayers)
= 8.1.14 - 2021-07-28 =
* Fixed issue where custom scripts (CSS & JS) would be html_entities encoded by the wp_kses_post function, causing custom scripts to run unpredictably
* Fixed issue where uncaught exception would cause errors to show on the frontend, although it is gracefully handled
* Fixed issue where carousel time placeholder had an unclosed attribute
* Resized credit images to standard sizes (Reduction in file size)
* Resized interface images and changed color spaces (Reduction in file size) (Thanks to lowwebtech on GitHub)
* Tested up to WordPress 5.8
= 8.1.13 - 2021-06-15 =
* Fixed issue where Authenticated Persistent XSS could be executed on any CRUD module. Uses wp_kses_post for cleanup. Applies to Markers, Polygons, Polylines and Shapes (Thanks to Visse)
* Fixed issue where Authenticated Persistent XSS could be executed on GDPR settings fields. This was resolved by adding wp_kses_post to all settings fields (Thanks to Visse)
* Updated security report credit for 8.1.12 withi changlog and readme files
= 8.1.12 - 2021-06-03 =
* Fixed issue where authenticated Stored Cross-Site Scripting could be executed in the map list (Thanks to Mohammed Adam)
* Fixed issue with translation file name for no_NO. Changed to nb_NO
* Fixed issue where some OpenLayers tilesets were loaded via http instead of https
* Fixed issue where legacy admin styles were force loaded in gutenberg editor. Reported for causing conflicts with SEOPress
* Fixed issue where checboxes within the admin area would show a white tick due to issues in the legacy admin stylesheet
* Fixed issue where 'no results' alert would show when resetting the store locator search
* Fixed issue where 'Store' post types in WP Store Locator would break due to our API loader take preference, as reported by plugin author
* Fixed issue where polygon info-windows would have quick edit link in map editor. This is not supported by polygons at the moment
* Fixed issue where map click event would fire when clicking on polygons in OpenLayers. This is due to pixel interpolation issues.
* Fixed issue where custom CSS would be added to the DOM multiple times
* Fixed issue where custom JS would be added to the DOM multiple times
* Fixed issue where global localized variables would be added to the DOM multiple times
* Fixed issue where create map page link would cause a fatal error due to a non-static method definition
* Fixed issue where included automcomplete styling would not appear as intended
* Removed 'Delete all maps' danger zone controller from the settings area as this does not apply to basic users
* Removed PHP8 disable functionality
* Removed chat link
* Added support for PHP8, this is a prelim pass but from tests works well. May be revisited in the future
* Added link to WPML integration documentation
* Added setting to disable tilt controls in the Google Maps option
* Added check for the 'lnglat' column, if it is present, it will be automatically pruned from the database as it is not supported or used
* Added general notices about features
* Added supporting polygon info-window placement style for OpenLayers
* Updated es_ES translation file (Thanks to Pedro Ponz)
= 8.1.11 - 2021-03-08 =
* Fixed issue with 'No results found' alert not showing in some cases
* Fixed issue where max/min zoom levels would not be respected
* Fixed issue with Fr translation file mi and km translations being prefixed wth '1'
= 8.1.10 - 2021-02-18 =
* Fixed issue where text JSON was not parsed with some caching solutions (Breeze for example)
* Fixed issue with spelling of 'Autoptimize' in advanced settings tab
* Fixed issue where compact/bare-bones/minimal user interace styles may not have an effect on some sites
* Fixed issue where multiple jQuery identification module would cause a failure in map initialization when finding embedded scripts
* Fixed issue where legacy store locator layout would use the JS Alert 'not found' message, instead of the message container in the DOM
* Fixed issue with 'miles away' spacing on store locator searches
* Fixed issue with switch styling which have inline 'notices'
* Fixed issue where the /features/ ajax fallback would fail due to the regex comparison
* Adjusted width of settings labels in map editor, for slightly improved interface layouts
* Added option to show/hide store locator distances
* Added notice to GDPR settings when Complianz is enabled, as they manage our GDPR settings internally instead. Settings are now disabled to reduce any confusion
* Added base upgrade hook for auto backup triggers in Pro add-on
* Added beta notice to "Only load markers within viewport"
= 8.1.9 - 2021-02-04 =
* Fixed issue where 'Hide Point of Interest' option was not available without the Pro add-on
* Added establishment suggestions to the Google Maps Autocomplete module
* Added basic Usercentrics integration. Thanks to the Usercentrics development team for additional technical documentation
= 8.1.8 - 2021-02-01 =
* Fixed an issue where OpenLayers Tile Server Key field would not be visible without the Pro add-on
* Fixed an issue where OpenLayers would not allow click event bubbling for features
* Fixed an issue with marker storage logic that would prevent the Pro add-on from removing gallery images
* Fixed an issue where the store locator would scroll to the map element, even when modern locator style is active
* Fixed an issue with the onApproveMarker event trigger in the marker panel
* Added pep.js to the dependencies of the plugin to support pointer events on iOS 12 devices
= 8.1.7 - 2021-01-26 =
* Fixed issue where you could not disable FontAwesome from loading on the frontend
* Fixed issue where FontAwesome V4 would be loaded when V5 should have been loaded
* Fixed issue where Datatables API extension would occur before datatables is initialized
* Fixed issue with polygon line opacity mutator not allowing for changes to take affect
* Fixed issue with the WPGMZA isFullscreen variable scope would resolve correctly
* Fixed issue where OpenLayers Geocoder would not respect country restirctions
* Fixed issue where primary stylesheets would not have a version number present, this caused issues with cache busting when updates are released
* Fixed issue where no max-width rule was applied to icon column in marker list within the admin area
* Added placeholder structure for owl carousel dependency settings
* Added 'color paste' buttons next to all color fields to allow for easy hex code pasting for specific components
* Added a failsafe for broken polydata (legacy) paths which will fail to resolve in some instances, which could break the features end point
* Added option to set a custom OpenLayers tile server URL if you prefer to do so, API field still applies if filled
= 8.1.6 - 2021-01-21 =
* Fixed issue where polyline opacity would not be respected
* Fixed issue where 'get_user_locale' would fail in some environments
* Fixed issue where 'approve' button would not fire relevant events with VGM add-on in place
* Fixed kml field storage issue
* Added styling classes to the danger zone to match UI
* Added a 405 DELETE fallback check to the REST API handlers
* Added scroll to feature panel when editing a feature
= 8.1.5 - 2021-01-19 =
* Removed the external reference for the live chat image and made it local
* Added new functionality to reset and/or delete your map, marker and shape data
* Fixed a conflict with instant.page ('i' and 'l' variable conflict)
* Fixed issue where modern interface style will not override the store locator styles for legacy maps
* Fixed issue where modern store locator was not responsive
* Fixed issue where olMarkers were attempting to access Google LatLng objects in some instances, this now uses LatLng Literals instead
* Fixed issue where text overlays would not have a minimum width, which caused text to appear strangely on the map
* Fixed issues with some store locator settings not being respected on the frontend
* Fixed issue where polygon settings may not be mutated by the polygon module
* Fixed issue with WP Rest Cache (by Acato) not caching the marker-listing end point correctly
* Fixed issue where map click event would not bubble correctly from native event dispatcher
* Added back marker position adjust mode and refined the functionality slightly. This was removed in an earlier version mistakenly
* Added a fallback for servers which do not support the DELETE request method via the RestAPI
* Added a close button to the live chat link in the map editor and map settings page
= 8.1.4 - 2021-01-14 =
* Fixed a bug that stopped the GDPR consent form to display if Open Layers was enabled
* Fixed a bug that broke the compatibility with the ComplianZ WordPress Plugin
* Fixed a bug with dataTables translations for Finnish
* Fixed a bug that caused "open_basedir restriction in effect" on some servers
* Fixed a bug that caused "Unparenthesized'a ? b : c ? d : e'is deprecated" to appear for some users
= 8.1.3 - 2021-01-13 - High priority =
* Fixed the bug where "miles away" or "km away" was not showing up on markers once a store locator search was done
* Fixed a bug that caused markers to not load in some instances
* Fixed an issue where the MapsEngineDialog would cause headers already sent error on some sites, causing a white screen on admin-post.php
* Fixed an issue where settings don't get sent to the frontend, such as the starting location of the map. Only occurs on some sites
* Added an option to add an OpenLayers TileServer API key for server that require an 'apikey' to be sent with requests
= 8.1.2 - 2021-01-11 - High priority =
* Fixed issue where polylines would not respect their stored configuration
* Fixed issue with V6 API dequeuer still running in V8, even though option was removed from core
* Fixed bug with open infow windows by default only opening 1 marker, usually the last one
* Fixed issue where bicycle, traffic and transport layers would be enabled for all users
* Fixed issue where legcay transport layer setting name would always be true on frontend
* Fixed issue with Finnish datatables language file being lowercase, crashing map list
* Fixed an issue where sometimes the settings area would produce a white page instead of redirecting back to settings
* Fixed an issue where you would not be able to edit shapes
* Fixed an issue where you would not be able to delete shapes
* Allowed for a one-click experience to swap over to Open Layers if you're not using a Google Maps API key in the map editor
* Added a new "Edit" button in the marker infowindow within the map editor
* Fixed a bug that cause "modern store locator" to not respect the setting
= 8.1.1 - 2021-01-07 - High priority =
* Fixed SVN issue
= 8.1.0 - 2021-01-07 - High priority =
* OpenLayers now fully supports shapes
* New, easy-to-use and highly efficient shape drawing tools
* New "batched marker loading" feature allows marker loading to be broken up into parts for a smoother loading experience with large amount of markers
* Hide Load Maps Engine API option when you select the OpenLayers map engine
* Fixed Store Locator Radii values not updating Default radius option
* Fixed OpenLayers Disable Zoom Controls not working
* New, searchable, paginated, sortable tables for polygons, polylines, heatmaps, circles and rectangles
* New Vector render mode setting for OpenLayers - Significantly improves performance with large amount of markers
* Map editor now "all-in-one" with all controls on a single page
* Map editor and settings page are now fully W3C and WCAG compliant
* Map editor and settings page are now using DOM for easy and flexible customisation
* Map editor and settings page now handle setting serialization dynamically
* Marker, polygon, polyline, heatmap, rectangle and circle panels now handle setting serialization dynamically
* All backend content, logic and presentation is now separate
* All miscellaneous JavaScript now fully modular and fully extensible
* AJAX loading fully supported
= 8.0.31 - 2020-12-22 - Medium priority =
* Added PHP 8 compatibility notice. PHP 8 is not currently supported, and the plugin will be disabled to prevent fatal errors in these cases. Support will be added soon
= 8.0.30 - 2020-12-17 - Medium priority =
* Adds DOMElement support for PHP 8
* Fixed GDPR message showing multiple times on some installations
* Fixed issue with undefined variables in polygon creator panel
* Fixed an issue with hiding POI locations in Google Maps Engine
= 8.0.29 - 2020-12-10 - High priority =
* Tested up to WordPress 5.6
* Added support for jQuery 3
= 8.0.28 - 2020-11-26 - Low priority =
* Tested the plugin with WP5.6 RC1 - All seems in order
* Modified the Google Places Autocomplete functionality to reduce the amount of API calls originating from basic users
= 8.0.27 - 2020-10-15 - Medium priority =
* Changes have been made to limit the amount of API calls we process for users using our API key (for new users). For more information please see https://www.wpgmaps.com/documentation/autocomplete-disabled/
= 8.0.26 - 2020-08-25 - High priority =
* Tested up to WordPress 5.5
* Patched a vulnerability, thank you WP.org for identifying it!
* Fixed a bug that stopped markers from being deleted on some WP installations (thank you Gary Boulter!)
* Fixed a bug where editing a marker would cause a JS error in some instances
= 8.0.25 :- 2020-06-12 :- Medium priority =
* Tested up to WordPress 5.4.2
* Fixed Google Autocomplete not working due to failed check in minified code
= 8.0.24 :- 2020-06-10 :- Medium priority =
* Added fallback for datatables when language file cannot be loaded
* Plugin now loads unminified version of text.js due to IE issues with minified version
* Notice is issued for users using expired Cloud API keys
* Fixed __isset returning false for ID on Crud class
* Fixed notice in Gutenberg module when passing array shortcode attributes
= 8.0.23 :- 2020-05-07 :- Medium priority =
* Added experimental integrity check class (currently unused)
* Added links to settings tabs in "No API key" message
* Tested up to WordPress 5.4.1
* Fixed IIS failing under certain conditions (+ now URL encoded for IIS servers in compressed path variables)
* Fixed lowercase finnish.json filename breaking DataTables on Finnish installations
= 8.0.22 :- 2020-04-07 :- Medium priority =
* Added tooltip to OpenLayer markers
* Removed calls to wpgmza_enqueue_fontawesome (deprecated)
* Added constants WPGMZA_PLUGIN_DIR_PATH and WPGMZA_PLUGIN_DIR_URL
* Corrected typo in class.map.php (scoreLocator)
* Added imageFolderURL to WPGMZA
* Corrected paths in legacy circle and rectangle PHP files
* Corrected Autoptimize typo
* Debug OpenLayers no longer bundled or supported
* Fixed "google is undefined" for users who had disabled legacy Pro, switched to OpenLayers and re-enabled legacy Pro
= 8.0.21 :- 2020-03-19 :- Medium priority =
* Developer Mode is now inaccessible
* Tested up to WordPress 5.4
* Removed experimental lnglat column
* Fixed 404 preventing circle and rectangle add/edit pages from working
* Fixed Cannot use 'in' operator to search for 'x' in undefined when pressing enter on OpenLayers modern style store locator
* Fixed ol.Sphere is not a constructor preventing OpenLayers store locator w/legacy radius from working correctly
* Fixed issues with map not displaying when no engine set (solves issues with Pro 6 map loading)
= 8.0.20 :- 2020-03-06 :- Medium priority =
* Re-factored store locator into new class
* Removed hard coded zoom level when editing marker
* Improved OpenLayers gesture handling UX to prevent browser zooming when Ctrl is pressed over map viewport when the gesture notice is visible
* WPGMZA.Distance.between now accepts latlng literals
* Updated bundled OpenLayers library to 6.2.1
* Fixed old marker not removed after editing location
* Fixed OpenLayers longitude not wrapping properly causing markers to disappear when moving outside -180 to +180
* Fixed UI style setting not changing
= 8.0.19 :- 2020-02-12 :- Medium priority =
* Fixed issue with modern store locator and large number of sub-categories
* Made zoom limit controls live
* Changed UI style dropdown to radio buttons and added descriptions
* All PO files rescanned to allow translation of new strings
* esc_html__ and esc_html_e added to PO keywords
* PO files now use relative paths
* Fixed escaping issues in PO files
= 8.0.18 :- 2020-02-06 :- Medium priority =
* Added center on marker button to the marker listing in the backend to center on marker location
* UX improvements to the map listing page
* UX improvements to the map editor page
* Fixed a bug with the "move marker location" feature
* Added sanitization calls to the move marker location feature
* Removed ol-debug.js and ol.js.map (reduced plugin size)
= 8.0.17 :- 2020-02-03 :- Medium priority =
* Google Maps API now loaded from maps.googleapis.com, including for Simplified Chinese locale
* Database installer now uses WordPress' character set and collation, rather than the databases default
* Fixed JavaScript error preventing OpenLayers InfoWindow from opening correctly
= 8.0.16 :- 2020-01-30 :- Medium priority =
* Added functionality to customize DataTables language strings in non-english locales
* Adjusted approval button permission callback to allow button access for the selected user access level
* Added error message popup for when Geocoding library is not enabled on map edit page
* Removed width limit on about text and legacy badge from Welcome Page
* Fixed greedy gesture handling not respected by OpenLayers
* Temporarily removed two finger panning for OpenLayers due to inconsistent behaviour across touch devices
* Fixed notice on welcome page
= 8.0.15 :- 2020-01-21 :- Medium priority =
* Added functionality to re-enable interactions in backend
* Added disabled_interactions_notice, interactions_enabled_notice, disabled_interactions_button to our strings file
* Re-branded logo and banner
* Renamed "Disable Two-Finger Pan" to "Greedy Gesture Handling"
* Updated screenshots on welcome page
* Updated Google Maps API instructional video link
* Added new banner to map edit page
= 8.0.14 :- 2020-01-13 :- Medium priority =
* Added Gesture Handling (Ctrl + Zoom and Two-finger pan) for OpenLayers
* "No Google Maps API key entered" message will no longer obscure map for new users
= 8.0.13 :- 2020-01-07 :- Low priority =
* Tested up to WordPress 5.3.2
* Relaxed "invalid route" check in RestAPI to allow external JSON to be used
* Database no longer specifies InnoDB as database engine, enabling support for MyISAM
* Database no longer specifies UTF-8 as character set for tables, the default for the database will be used
= 8.0.12 :- 2020-01-02 :- Medium priority =
* New event on window - ready.wpgmza. This fires when all modules are ready, but maps haven't started loading
* WPGMZA.LatLng.fromString is now static
* Removed console logging on theme panel when theme data is invalid
* WPGMZA.EventDispatcher can now unbind all event listeners with off / removeEventListener
* Fixed incompatibility with GTranslate due to no check for google.maps in MYMAP.init
* Fixed OpenLayers geocoder trying to geocode coordinates resulting in markers added by coordinates moving
* Fixed redirection loop after entering Google Maps API key into prompt on map edit page
* Fixed "Cannot read property 'markerFilter' of undefined" in modern-store-locator.js
* Fixed OpenLayers HTML marker in wrong position after refreshing and switching tabs during load
* Fixed infowindowclose.wpgmza being dispatched from the map, rather than the infowindow
* Fixed OpenLayers polyline not displayed
= 8.0.11 :- 2019-12-11 :- Medium priority =
* Added WPGMZA.LatLngBounds.prototype.toLiteral
* Rest API now removes trailing = on compressed path variable requests as certain security suites and servers would block this as Forbidden
* Increased map_title to 256 characters, fixes imports not working on files with long filenames
* Fixed user roles below admin cannot save map settings by correcting permissions check
* Fixed modern store locator always showing alert
* Fixed modern store locator "not found" alert blank
* Fixed experimental vector source layer markers firing multiple click events when their icons overlap
= 8.0.10 :- 2019-11-26 :- Medium priority =
* Added animated panning effect for OpenLayers infowindows, including a dynamic offset to make infowindows fully visible on click
* Removed var_dump from wp-google-maps-polylines.php
* Restricted include/exclude Maps API on page inputs to comma separated integers
* Changed default map alignment to "None"
* Dropped legacy store locator marker and circle code, module now controls this fully
* Fixed array shorthand parse error in PHP < 5.4
* Fixed getCurrentPosition only calling the supplied error callback function on the first failure
* Fixed autocomplete not initialising when global settings have not been saved
* Fixed shapes not being added when global settings have never been saved
* Fixed Store Locator setting "show bouncing icon" not working
* Fixed trashing a map redirects user to map edit page for the trashed map
* Fixed store locator circles too small when using miles as distance units
* Fixed store locator not found message not showing
= 8.0.9 :- 2019-11-12 :- Medium priority =
* Updated Dutch translations
* Changed Humanitarian tileserver URL to https://
* Added workaround for syntax error in class.marker.php on PHP versions 5.5 and below
* Fixed "No API key" error showing until the page is refreshed after entering API key in notice
* Fixed getCurrentPosition is not a function on setups which don't have this function on the navigator
* Fixed issue with OpenLayers circle fill color
= 8.0.8 :- 2019-11-04 :- Medium priority =
* Fixed AJAX fallback routes not registered for GET only REST routes
* Fixed some REST API routes 404ing with plain permalinks when route URL + is replaced with space
* Fixed ?skip_cache=1 breaking plain permalink REST URLs by detecting when query variables are in use
= 8.0.7 :- 2019-10-25 :- Medium priority =
* Tested up to WordPress 5.3
* Localized all remote images
* Separated all inline JavaScript and PHP
* Removed developer documentation
* Removed redundant files
* Removed legacy bundled jQuery
= 8.0.6 :- 2019-10-22 :- Low priority =
* Legacy UI style InfoWindow text width fix now only applies to Google Maps engine
* Google API script loader now adds data-usercentrics attribute
* InfoWindow now tracks open / closed state in this.state
* InfoWindow no longer dispatches infowindowclose.wpgmza event if already closed
= 8.0.5 :- 2019-10-17 :- Medium priority =
* Fixed additional "undefined" infowindow appearing when using XML cache
* Fixed XML cache not regenerated when POSTing to marker endpoint
= 8.0.4 :- 2019-10-15 :- Medium priority =
* Now tested up to WordPress 5.2.4
* Added REST endpoints for counting and removing duplicate markers
* Safeguards added to switch back to DB pull if execution time limit or memory limit is reached during XML cache generation
* Theme parser will now attempt to strip slashes before abandoning parsing
= 8.0.3 :- 2019-10-13 :- Medium priority =
* Added workaround for Enfold theme issue with Safari preventing map from loading
* Relaxed CRUD class to issue warning when ID is passed in with field data instead creating a new object
* Fixed edit marker button not working on map edit page
= 8.0.2 :- 2019-10-10 :- Medium priority =
* Fixed file not found on settings page when using OpenLayers engine
* Fixed translation strings not being applied
* Fixed dragging a marker also pans map when using OpenLayers
= 8.0.1 :- 2019-10-08 :- Medium priority =
* Fixed Warning: unserialize() expects parameter 1 to be string, array given
* Fixed restructured code preventing marker delete and approve buttons from working
* Fixed markers not being removed from map panel following deletion
= 8.0.0 :- 2019-10-07 :- Medium priority =
* New theme panel and theme editor
* New User Interface Style setting and variety of UI styles added
* Several user experience improvements
* Significant performance improvements and optimizations
* Significantly enhanced REST API
= 7.11.53 :- 2019-10-03 :- Low priority =
* Fixed "All" missing from datatables page size dropdown
* Fixed bundled translations only loaded on backend since 7.11.45
* Added polyfill for slice on Uint8Array, fixing issues with compressed path variables and IE
* Added no-op JS to wpgmza_data.js
* Added isFilterable property to Marker
* Removed .gitattributes from production build
= 7.11.52 :- 2019-09-24 :- Medium priority =
* Added Astra theme compatibilty module, fixes InfoWindows not opening with Astra theme
* Added fallback for older versions of WordPress where wp_doing_ajax is not present, fixes fatal error on WordPress < 4.7
= 7.11.51 :- 2019-09-19 :- Medium Priority =
* Fixed Modern Store Locator Radius causing Safari (mobile) to reload page
= 7.11.50 :- 2019-09-13 :- Medium priority =
* Fixed markers not visible in Internet Explorer when using OpenLayers (append is not a method)
= 7.11.49 :- 2019-09-10 :- Medium priority =
* Added warning when "Do not enqueue datatables" is selected, but dataTables library is not loaded
* Added comment to wpgmza_data.js to fix issues with empty files and Safari
* Altered "zero-results" message to "No results found for this address"
* Fixed skipNonceCheck flag being ignored when Live Tracking App is used
= 7.11.48 :- 2019-08-28 :- Low priority =
* Fixed polygons and polylines not displaying back end before global settings have been saved
* Increased link column to accept 2083 characters
= 7.11.47 :- 2019-08-09 :- Medium priority =
* Fixed map engine dialog submission not working
* Fixed WPGMZA.EventDispatcher not handing some native events over to DOM correctly
= 7.11.46 :- 2019-08-08 :- Medium priority =
* Fixed conflict with WooCommerce effecting checkout page on installations with debug notices turned on
* Fixed WPGMZA.getQueryParamValue matching location hash on last parameter
= 7.11.45 :- 2019-08-07 :- Medium priority =
* Added ABSPATH checks to .html.php files, class.settings.php and backwards_compat_v6.php
* Fixed add shape buttons disabled for Google when global settings have never been saved
* Fixed permissions issues when attempting to save global settings (HTTP error 401)
* Fixed permissions issues preventing users without manage_options capability from logging in
= 7.11.44 :- 2019-08-01 :- Low priority =
* Added REST API parameter skipNonceCheck for Live Tracking App
* Fixed map type settings not "live" in map edit page
* Fixed map type setting not reflected when map edit page initialises
= 7.11.43 :- 2019-07-31 :- Low priority =
* RestAPI now exposes registerRoute as a public function for add-ons to register REST API routes
* New action wpgmza_register_rest_api_routes added
= 7.11.42 :- 2019-07-30 :- Medium priority =
* Added checks for ABSPATH to all PHP modules
* Added a console warning when Array prototype has been improperly extended, which breaks for ... in loops
* Improved parameter sanitization
* Dropped deprecated usage tracking function
* Dropped unused GoogleGeocoder class
* Dropped old admin head function, added update notice for users running Pro < 5.24
* Fixed AJAX REST API POST calls always failing nonce security check
= 7.11.41 :- 2019-07-29 :- Medium priority =
* Fixed store locator not working in OpenLayers since 7.11.40 due to missing nonce
= 7.11.40 :- 2019-07-29 :- Medium priority =
* REST API security enhanced with additional per-route nonces
* getScrollAnimationOffset now accounts for WP admin bar height
* removeMarker now closes marker InfoWindow before removing it
* Fixed notice on map edit page on setups with E_NOTICE error display
* Fixed markers not removed from map panel following bulk delete
* Fixed GoogleHTMLOverlay is not a constructor when WPGMZA.settings.engine is null
= 7.11.39 :- 2019-07-25 :- Medium priority =
* Added code to update OpenLayers marker position following icon loading
* Fixed marker being off-position before user interaction on certain setups
* Fixed dataTables translations not working
* Fixed fatal error on map pages when GDPR notice filter returns an empty string
* Fixed category icon not respected in map panel when running Pro <= 6.*
= 7.11.38 :- 2019-07-22 :- Low priority =
* Removed advisory REST AJAX notice due to false positives
= 7.11.37 :- 2019-07-16 :- Low priority =
* Fixed polyline color control not "live" on polygon edit page
= 7.11.36 :- 2019-07-11 :- Low priority =
* Re-added admin-ajax fallback for when REST API is blocked
* Fixed Polyline color issue
= 7.11.35 :- 2019-07-08 :- High priority =
* Security vulnerabilities fixed (Thank you Plugin Review Team at WordPress.org and pluginvulnerabilities.com)
= 7.11.34 :- 2019-07-07 :- Medium priority =
* Fixed DataTable sort order unpredictable with mixture of numeric and non-numeric data
* Rolled back admin-ajax changes pending review
= 7.11.33 :- 2019-07-02 :- Low priority =
* Added admin-ajax fallback for when REST API is blocked
* Fixed characters such as accents showing as plain text HTML entities in DOMElement
* Fixed object must implement countable notice on QueryFragment
* Regenerated temporary API key
* Removed unreachable code
= 7.11.32 :- 2019-06-21 :- Low priority =
* Added mechanism to report 403 Forbidden on REST API, this is usually caused by security plugins blocking REST requests for non-logged in users
= 7.11.31 :- 2019-06-18 :- Low priority =
* Added checkbox to disable Autoptimize workaround for setups where the workaround prevents CSS aggregation
* DataTable module now uses RestAPI module to make AJAX requests
* Fixed "Permalink Manager Lite" breaking admin marker table when POST requests are used
* Fixed welcome screen not working
= 7.11.30 :- 2019-06-12 :- Medium priority =
* Added /decompress REST API endpoint for debugging compressed path variable requests
* Added integration with WP REST Cache by Acato
* Added Elias Fano encoding modules for efficient transmission of marker ID's on compressed path variable requests
* REST API module now no longer loads the entire WP REST API client side library
* Moved clearInterval on Google infowindow to before event is triggered, the event will no longer fire repeatedly if any attached listeners cause an error
* Fixed bulk delete not working
* Removed performance intensive regex checks on template_redirect. Short code flag is now set by short code callbacks
* Fixed notice in legacy-core.php when no map ID present on shortcode
* Fixed cannot use scalar value as array when localizing legacy current map ID global
* Fixed issues with older versions of Pro add-on and admin marker table
= 7.11.29 :- 2019-06-06 :- Low priority =
* Added support for compressed path variables on REST API module (experimental)
= 7.11.28 :- 2019-06-03 :- Medium priority =
* Added nonce to settings form on admin post action
* Fixed errors on PHP installations where documentElement is not a property on DOMDocument
= 7.11.27 :- 2019-05-29 :- Medium priority =
* Added keypress listener for enter on store locator for configurations which don't emit keydown
* Changed (experimental) compressed REST datatables GET request to use a cachable path variable rather than query string
* Fixed classes that subclass WPGMZA.AdvancedTableDataTable not having "Show X items" setting applied in Pro
* Fixed missing spatial function prefixes in WPGMZA\MarkerFilter::applyRadiusClause, now works with MySQL 8.*
* Fixed "no results found" not showing when new MarkerFilter returns zero results
* DataTables AJAX route no longer issues notice when used without a HTTP_REFERER
= 7.11.26 - 2019-05-22 :- Medium Priority =
* Tested with WordPress 5.2.1
* REST API only passes map ID to child classes of MarkerListing and AdvancedTable
* Fixed admin marker table not loading due to the above
= 7.11.25 - 2019-05-21 :- Low priority =
* Added CSS max width fix to override themes breaking OpenLayers markers
* Added WPGMZA.Text and WPGMZA.GoogleText modules
* Added experimental setting WPGMZA.settings.useCompressedDataTablesRequests
* Developer mode and SCRIPT_DEBUG will now enqueue OpenLayers unminified
* WPGMZA.LatLngBounds can now take an instance of WPGMZA.LatLngBounds in constructor arguments
* Renamed deletePolygon, deletePolyline to removePolygon, removePolyline etc. on WPGMZA.Map
* wpgmaps_check_shortcode no longer sets short_code_active to false
* Fixed links not clickable in Pro InfoWindows
* Fixed issue with WPGMZA.LatLngBounds around 180th meridian
* Fixed various typos
* Fixed error where _gdprCompliance on Plugin class would be empty for Gutenberg integration
= 7.11.24 :- 2019-05-20 :- Medium priority =
* Store Locator module no longer triggers a filter update when the address was not found
= 7.21.23 =
* Tested with WordPress 5.2
* Added more robust error handling for missing files and failed initialisations (when NOT in developer mode)
* Fixed LatLngBounds issue with 180th meridian
* Fixed "undefined" in map edit page infowindows
= 7.11.22 :- 2019-05-08 :- Low priority =
* Added the ability to toggle auto night mode as well as a theme
* Added a min height to backend map so that it does not break when height is set to 100%
* Added shift-click range selection to admin marker table
* Added code to automatically regenerate readme.txt changelog
* Fixed ModernStoreLocator creating OpenLayers store locator when engine setting is null and defaulting to Google
* Fixed beforeunload listener always bound on map edit page (fixed Save Changes? prompt shown even if no changes were made)
* Dropped logging in ScriptLoader module
= 7.11.21 :- 2019-04-16 :- Low priority =
* Added serializeFormData to DOMDocument and DOMElement
* Added new event for InfoWindows - domready.wpgmza
* Added new function WPGMZA.extend for shorthand extension of modules
* Added warning when WPGMZA.RestAPI.call is called (as opposed to WPGMZA.restAPI.call)
* Implemented factory method for map settings page JS module
* Changed RestAPI to not throw an error when a call is aborted
* Changed DB version checks to use global version string (this module is currently not used)
* Fixed missing comma in DB installation code preventing marker table from being created (this module is currently not used)
= 7.11.20 :- 2019-04-09 :- Low priority =
* Added Mexican Spanish (es_MX) translations
* Added revert back to DB pull when XML folder not present
* Updated PO files from sources
* Fixed rectangles not working when using v6 of Pro
= 7.11.19 :- 2019-04-02 :- Low priority =
* Readme.txt Upgrade Notice updated
* Fixed markers sometimes off position when using OpenLayers
= 7.11.18 :- 2019-04-02 :- High priority =
* Fixed potential REST API exploit (affects 7.11.00 - 7.11.17 - with thanks to Thomas Chauchefoin)
= 7.11.17 :- 2019-04-02 :- Low priority =
* Added shortcode attribute classname
* Fixed Custom CSS classes in Gutenberg editor not being applied
= 7.11.16 :- 2019-03-28 :- Low priority =
* Added Catalan translation files
* Added hide POI logic to WPGMZA.GoogleMap
* Added new global setting WPGMZA.settings.hide_points_of_interest
= 7.11.15 :- 2019-03-25 :- Medium priority =
* Added caching warning to GDPR Compliance settings panel
* Added check for wp.components in Gutenberg module
* Renamed Croation translations to correct -hr.* suffix
* Fixed incorrect logic causing unapproved markers to appear in Pro marker listings
* Relaxed "combined file would be blank" from exception to an admin notice when in the WordPress environment
= 7.11.14 :- 2019-03-14 :- Low priority =
* Added convenience function WPGMZA.getQueryParamValue
* Most PHP now uses isInDeveloperMode() rather than referencing the setting directly
* Fixed setting developer mode cookie would set developer mode in database
= 7.11.13 :- 2019-03-11 :- Low priority =
* Fixed adding "select" function to Array prototype colliding with "select" event listener for markers
* Fixed sorting direction not respected in AjaxTable following 7.11.11 changes
= 7.11.12 :- 2019-03-08 :- Low priority =
* Removed debugging code from class.query.php
* Fixed mismatched setting name for Store Locator distance units causing "miles" to be ignored
= 7.11.11 :- 2019-03-07 :- Low priority =
* Allowed LatLngBounds to wrap around 180th meridian, Gold now clusters correctly on wide or zoomed out maps
* Altered AjaxTable to treat text fields containing numeric data as numeric, giving more natural sort order on those fields
* Fixed wildcard not being used when no fields passed to Query
* Fixed notices and inconsistencies with Elementor integration
= 7.11.10 :- 2019-03-05 :- Low priority =
* Changed Google Maps API error handler to render in a panel rather than in a modal dialog
* Removed "In light of recent GDPR regulation" admin notice
* Fixed clicking listen item outside link has no effect on map edit page tabs
= 7.11.09 :- 2019-02-28 :- Medium priority =
* Added disableInfoWindow to map objects which is used by InfoWindow.prototype.open
* Added LatLng.fromCurrentPosition
* Added warning and explanation when Google Maps is selected but API loader is not allowed to load the API
* Non-standard jQuery versions now issue console warning rather than cancelling map initialisation
* Map element now fires infowindow close event
* Fixed infowindow close event firing after infowindow element removed
= 7.11.08 :- 2019-02-25 :- Medium priority =
* Google Maps API error dialog is now shown when in developer mode
* Fixed missing link on "No API Keys" message in Google Maps API error dialog
* Fixed "undefined" InfoWindow opening
* Removed 100px minimum width from InfoWindows
= 7.11.07 :- 2019-02-22 :- Medium priority =
* Added Distance class
* Added property storeLocatorDistanceUnits to WPGMZA\Map
* Fixed Spatial function prefix not applied for version 8 due to wrong operator
* Fixed MarkerFilter radius clause ignoring store locator distance units setting
* Removed console.log call in GoogleMarker setVisible
= 7.11.06 :- 2019-02-20 :- Low priority =
* WPGMZA.RestAPI.prototype.call now returns xhr
* Improved modern store locator UX by switching reset button back to search button when text is inputted into address field
* Fixed "disable double click zoom" logic flipped
* Fixed undefined notice in AjaxTable breaking carousel marker listing in Pro when display_errors is true
* Fixed bulk delete not working due to removed legacy function
= 7.11.05 :- 2019-02-15 :- Medium priority =
* Improved WP Migrate DB integration by adding our plugin to their whitelist when WP Migrate DB is activated
* Re-added data-wpgmza-datatable-options attribute to datatables
* Fixed encoding issues in marker listing caused by UTF-8 to HTML entities conversion not being used
= 7.11.04 :- 2019-02-13 :- Medium priority =
* Added extra functions to LatLngBounds to support upcoming Gold patch (extendByPixelMargin, contains)
* Added Caltopo to tile servers
* Added Latvian translation
* Shortcode attributes are now passed to map element through data-shortcode-attributes
* DataTables loads unminified in developer mode
* DataTables no longer enqueued twice on map edit page
* DataTables translation re-applied following new AJAX implementation
* Changed wrong text domains in translation functions in tile-server-fieldset.html.php
= 7.11.03 :- 2019-02-06 :- Low priority =
* DataTables issue no longer present when running Developer Mode
* Fixed "display all" breaking admin marker table
* Fixed "Map Type" not being applied
= 7.11.02 :- 2019-01-31 :- High priority =
* Added override method to Settings module so settings are overridable without altering database
* Fixed fatal error in legacy-core.php when running older versions of Pro without Custom Fields
= 7.11.01 :- 2019-01-30 :- Medium priority =
* Fixed undefined notice in AjaxTable when using Pro marker listings
* Fixed legacy Google error message breaking Gutenberg editor when no key is present
* Fixed legacy compatibility issue with Global Settings module
= 7.11.00 :- 2019-01-30 :- Medium priority =
* Added new GlobalSettings module
* Optimized marker tables and listings giving significant performance boost when viewing marker listings, editing, adding and deleting markers
* Nominatim Cache now records country restriction
* Improved robusticity of data-settings attribute handling
* Added WPGMZA.LatLng.prototype.toLatLngLiteral
* Added check for jQuery slider in wpgmaps_tabs.js
* Added check for WordPress REST API and notices where that is not present
* Removed 5,000 marker live edit limit following performance optimizations
* Deprecated redundant WPGMZA_SETTINGS option
* Moved all code from main PHP file to legacy-core.php
* Checks for namespace, DOMDocument and WP REST API added in main file, a warning is issued if these are missing rather than a fatal error
* Fixed undefined index wpgmza_settings_marker_pull on new installations
* Fixed country restriction broken in OpenLayers
* Fixed interaction controls (disable pan, double click zoom and mousewheel) ignored in OpenLayers due to wrong scope
* Fixed zoom limits not respected in OpenLayers
* Fixed zoom limits incorrectly interpreted by Google
* Fixed "minZoom cannot exceed maxZoom" breaking Google maps when settings are reversed
* Fixed country restriction not respected by OpenLayers
= 7.10.58 :- 2019-01-18 :- Low priority =
* Added code to catch Geocoding Service errors in GoogleAPIErrorHandler
* Fixed wrong database prefix in wpgmaps_return_markers when running on a multisite installation
= 7.10.57 =
* Corrected year in 7.10.56 changelog
= 7.10.56 :- 2019-01-09 :- Medium Priority =
* Added function WPGMZA.Distance.between
* Removed code to disable TLS verification in WPGMZA\GoogleGeocoder
= 7.10.55 :- 2018-12-27 :- Medium priority =
* Changed GoogleMap fitBounds to accept a WPGMZA.LatLngBounds
* Changed OLMap fitBounds to accept a WPGMZA.LatLngBounds
* Fixed WPGMZA.LatLngBounds setting individual coordinates to LatLngs
* Fixed WPGMZA.GoogleMap.fitBounds not working with native LatLngBounds
= 7.10.54 :- 2018-12-20 :- Medium priority =
* Fixed default OpenLayers tiles being fetched over relative URL
= 7.10.53 :- 2018-12-17 :- Medium priority =
* Added missing file /html/tile-server-fieldset.html.php
= 7.10.52 :- 2018-12-14 :- Low priority =
* Fixed undefined errors when running Elementor
* Fixed "Cannot read property 'wpgmza_iw_type' of undefined" preventing infowindow opening
* Fixed missing spatial prefix on Marker::update_latlng
* Added class wpgmza-gdpr-compliance to GDPR compliance notice parent div
* Dynamic content removed from translation strings, printf now used instead
= 7.10.51 :- 2018-12-11 :- Low priority =
* Added tile server URL setting for OpenLayers
* Fixed Google vertex context menu preventing OpenLayers engine loading in developer mode
* Fixed Gutenberg integration module always loading scripts on front end
= 7.10.50 :- 2018-12-10 :- Low priority =
* Added blank alt attribute to OpenLayers marker img element
* Updated WP version supported to 5.0
= 7.10.49 :- 2018-12-05 :- Low priority =
* Improved Gutenberg integration (new buttons added)
= 7.10.48 :- 2018-12-03 :- Low priority =
* Added a check for wp.editor in Gutenberg JS module
* Fixed InfoWindow not initialized before open called when using marker open by default setting
* Fixed WPGMZA.OLMap returning zoom one level too far in (fixes map zooms in one level on save)
= 7.10.47 :- 2018-11-22 :- Low priority =
* Removed all redundant calls to getPlace
* Places AutoCompletes now only request the "name" and "formatted_address" fields
* Changed "Create an API key now" link
= 7.10.46 :- 2018-11-20 :- Medium priority =
* Fixed store locator circle and radius not displayed when no markers are present
* Fixed browser compatibility code causing Gutenberg dependency failure
* Google API version is now fixed at "Quarterly" (solves RetiredVersion notice)
* Unified store locator circle and radius logic for both XML and DB marker pull
* All PHP classes and methods now have documentation blocks
* Server side documentation added in /docs/php
* Client side documentation added in /docs/js
= 7.10.45 :- 2018-11-12 :- Medium priority =
* Fixed places autocomplete not initializing with modern store locator
* Fixed conflict with Autoptimize with large amounts of data by bypassing CSS optimization where shortcode is present
* Enter key now triggers search on modern store locator
= 7.10.44 :- 2018-11-05 :- Medium priority =
* Fixed Modern Store Locator Circle not working when Google Maps geometry library not loaded
* Fixed legacy-map-edit-page.js not enqueued when Gold add-on activated (with Pro >= 7.10.30)
* Fixed store locator circle color settings not respected in OpenLayers
* Improved unresolved dependency report, now reports requirements
= 7.10.43 :- 2018-10-31 :- High priority =
* Improved previous security fix
= 7.10.42 :- 2018-10-25 :- High priority =
* Closed potential XSS vulnerability in PHP_SELF on map edit page
= 7.10.41 :- 2018-10-24 :- Medium priority =
* Changed exception to notice when v8 dependencies are missing (fixes issue with Pro < 7.10.37 in developer mode)
= 7.10.40 :- 2018-10-17 :- Medium priority =
* Added temporary fix for Gutenberg module dependencies preventing wpgmaps.js from loading when in Developer Mode
* Fixed Infowindow not opening on touch device when using "hover" action
= 7.10.39 :- 2018-10-15 :- High priority =
* Fixed JS error when Gutenberg framework not loaded
= 7.10.38 :- Medium priority =
* Gutenberg integration
* Added factory class
* Added DIVI compatibility fix
* Added new table name constants
* Adjusted script loader to support external dependencies
* Fixed trailing slash breaking rest API routes on some setups
* Fixed wpgmza_basic_get_admin_path causing URL wrapper not supported
= 7.10.37 :- 2018-09-27 :- Medium priority =
* Fixed undefined variable on iOS breaking store locator
* Fixed edit marker using REST API not working when API route has two slashes
* Fixed map not appearing with particular versions of dataTables where the packaged version is not used
= 7.10.36 :- 2018-09-25 :- Medium Priority =
* Fixed change in 7.10.35 causing problems with OLMarker click event, preventing infowindow opening
* Dropped .gitignore which was causing deployment issues, now using .gitattributes to ignore minified files
= 7.10.35 :- 2018-09-20 :- Medium priority =
* Added links to new API troubleshooting documentation to Google Maps API Error dialog
* Fixed marker dispatching click event after drag when using OpenLayers
* Fixed map dispatching click event after drag when using OpenLayers
* Fixed map editor right click marker appearing multiple times
* Fixed map editor right click marker disappearing after map drag
* Fixed modern store locator circle crashing some iOS devices by disabling this feature on iOS devices
* Fixed gesture handling setting not respected when theme data is set in
= 7.10.34 :- 2018-09-17 :- Low priority =
* Added descriptive error messages when Google API is required but not loaded
* Added "I agree" translation to German files
* Added getPluginScripts to Scriptloader module
* jQuery 3.x document ready compatibility
* Changed wpgmza_google_api_status to be passed via wp_localize_script to prevent redirection issues in some circumstances
* Prevented UGM e-mail address being transmitted in WPGMZA_localized_data
* Removed redundant locationSelect dropdown
= 7.10.33 :- 2018-09-05 :- Medium priority =
* Fixed OpenLayers InfoWindow not opening
= 7.10.32 :- 2018-08-31 :- Medium priority =
* Fixed redundant setting wpgmza_gdpr_enabled causing "user consent not given" to be flagged erroneously
= 7.10.31 :- 2018-08-30 :- Medium priority =
* Fixed NaN zoom level causing Google Maps to hang
= 7.10.30 :- 2018-08-29 :- Medium priority =
* Fixed "Access to undeclared static property" on some PHP versions
* Fixed google-maps-api-error-dialog.html.php does not exist
= 7.10.29 =
* Improved return_polygon_array function making edit polygon page more robust
= 7.10.28 :- 2018-08-20 :- Low priority =
* Fixed engine being switched to OpenLayers following saving settings on a fresh install
* Added CSS fix for recent Google UI changes for MacOS / iOS + Safari
= 7.10.27 :- 2018-08-17 :- Low priority =
* Added wpgmza_xml_cache_generated filter
* Added wpgmza_xml_cache_saved action
* Improved return_polyline_array function making edit polyline page more robust
* Fixed Google API loading before consent given when "Require consent before load" checked
= 7.10.27 :- 2018-08-17 :- Low priority =
* Added wpgmza_xml_cache_generated filter
* Added wpgmza_xml_cache_saved action
* Improved return_polyline_array function making edit polyline page more robust
* Fixed Google API loading before consent given when "Require consent before load" checked
= 7.10.26 :- 2018-08-15 :- Low priority =
* Improved Google API error handling back end, module issues more comprehensive alerts
* GoogleAPIErrorHandler moved to /js/v8/google-api-error-handler.js
* Added CSS fix for recent Google UI changes (Buttons in triplicate)
= 7.10.25 :- 2018-08-10 :- Low priority =
* Fixed "Undefined variable" notice
= 7.10.24 :- 2018-07-31 :- Low Priority =
* Added regex callback for class autoloader for installations where token_get_all is not available
* Added spatial function prefix to spatial data migration function
* Added lat and lng properties to GoogleGeocoder result (for Pro 5 & UGM compatibility)
* Altered Map module to deserialize other_settings and merge into the map settings object
* Altered parent:: to \Exception:: in CSS selector parser
* Fixed version detection for MySQL 8
= 7.10.23 :- 2018-07-23 :- Low priority =
* Fixed REST API endpoint URL incorrect for installations in subfolders
* Fixed WPGMZA\Parent not found
* Added PHP version requirement 5.3 to readme.txt
= 7.10.22 :- 2018-07-18 :- Medium priority =
* Added filter wpgmza_localized_strings
* Added beginnings for REST API
* Added scroll animation when edit marker is clicked
* Fixed UTF-8 characters not being decoded into PHPs native charset before passing them to loadHTML in GDPR compliance module
* Fixed edit marker button not re-enabled following unsuccessful geocode
= 7.10.21 :- 2018-07-09 :- Medium priority =
* Added MySQL version check and dropped ST_ function prefixes for versions < 8.0
* Fixed markers not appearing front end and back end marker table empty for servers running old MySQL versions
= 7.10.20 :- 2018-07-05 :- Low priority =
* Added hook for new GDPR tab content
* Added JavaScript for VGM GDPR controls
* Fixed WPGMZA\DOMDocument::saveInnerBody not saving text nodes
= 7.10.19 - 2018-07-05 :- Medium Priority =
* Added new event "userlocationfound" dispatched from WPGMZA.events
* Added fall back to convert UTF-8 to HTML entities on installations without multibyte functions available
* Changed GDPR settings UI, removed redundant compliance setting, added default notice
* Fixed media="1" attribute not validating
* Fixed nominatim geocoder not giving expected response to callback
* Fixed ScriptLoader module always enqueuing FontAwesome 4.*
* Fixed debug code breaking WP Migrate DB integration
* Fixed custom fields blank in marker listing
* Replaced deprecated MySQL functions with ST_ functions
* Replaced deprecated jQuery(window).load functions
* Removed Google autocomplete when using OpenLayers
* Removed protocol from marker icons / fixed marker icons disappear after switching to https://
= 7.10.18 - 2018-07-02 :- Medium Priority =
* Fixed GDPR back end warning appearing when GDPR compliance is enabled
= 7.10.17 - 2018-06-29 :- Medium Priority =
* Fixed country restriction broken in store locator
* Added dismissable admin GDPR warning when GDPR compliance has been switched off
* Fixed GDPR settings blank by default on some installations
= 7.10.16 - 2018-06-21 :- Medium priority =
* Fixed global settings lost
* Fixed whitespace matched in version variable
= 7.10.15 - 2018-06-14 :- Medium priority =
* Fixed GDPR consent notice bypassed when "prevent other plugins and theme enqueueing maps API" is not set
= 7.10.14 - 2018-06-14 :- Medium priority =
* Fixed incompatibilities with UGM
= 7.10.13 - 2018-06-13 :- Low priority =
* Fixed can't save Modern Store Locator
* Fixed store locator reset not working
* Fixed disabling map controls not working
* Fixed store locator radio button
= 7.10.12 - 2018-06-12 :- Low priority =
* Handed FontAwesome loading over to ScriptLoader module
* Deprecated global function wpgmza_enqueue_fontawesome
* Fixed circles and rectangles only working on map ID 1
= 7.10.11 - 2018-06-08 :- Low priority =
* Fixed JS error when passing non-string value to document.write
* Temporary workaround for "Unexpected token % in JSON"
* API consent no longer required on back-end
= 7.10.10 - 2018-06-01 :- Medium Priority =
* Adding setting "Prevent other plugins and theme loading API"
= 7.10.09 - 2018-06-01 :- Medium Priority =
* Fixed unterminated comment warning
* Fixed map edit page creating Google places autocomplete when engine is set to OpenLayers
* Fixed icon not draggable in edit marker location page
= 7.10.08 - 2018-05-31 :- Medium Priority =
* Fixed cannot edit marker in Basic only
= 7.10.07 - 2018-05-31 :- Medium Priority =
* Fixed issue where map engine was different on back end
= 7.10.06 - 2018-05-31 :- Medium Priority =
* Added "require consent before API load" to GDPR settings
= 7.10.05 - 2018-05-30 :- Low Priority =
* Fixed Using $this when not in object context when using older PHP version
* Fixed google sometimes not defined when selected engine is OpenLayers
* Fixed can't edit GDPR fields
= 7.10.04 - 2018-05-30 :- Medium Priority =
* Fixed geocode response coordinates not interpreted properly
* Italian translation updated
= 7.10.03 - 2018-05-30 :- High Priority =
* Fixed InfoWindow not opening when max width set in
* Fixed $this not in context inside closure when using older PHP versions
* Fixed Gold add-on clustering settings blank
* Altered map engine selection dialog
= 7.10.02 - 2018-05-29 =
* Engine defaults to Google Maps
= 7.10.01 - 2018-05-29 :- Medium Prority =
* Fixed undefined index notice in GDPR module
= 7.10.00 - 2018-05-29 :- Medium Priority =
* Added new Javascript modules
* Added new PHP modules
* Class AutoLoading implemented
* OpenLayers / OpenStreetMap integration
* Fixed Edit Marker Position not working with Pro 6.*
* Fixed some strings not being translated in German
* JS Minification
* Added "Developer mode"
= 7.0.05 =
* Added GoogleMapsAPILoader module which now controls Google Maps API enqueueing and relevant settings
* Added integration with WP Migrate DB to handle spatial types
* Added support for shortcodes in marker description
* Bug fixes
= 7.0.04 - 2018-05-07 =
* Fixed PHP notice regarding store locator default radius
= 7.0.03 - 2018-04-20 =
* Improved spatial data migration function to be more robust
* Fixed undefined index use_fontawesome
= 7.0.02 - 2018-04-15 =
* Added option to select FontAwesome version
* Fixed bug with circle data array
= 7.0.01 - 2018-04-11 =
* Switched to WebFont / CSS FontAwesome 5 for compatibility reasons
* Fixed JS error in for ... in loop when adding methods to Array prototype
* Fixed FontAwesome CSS being enqueued as script
* Added functionality to fit map to bounds when editing shapes
= 7.0.00 - 2018-04-04 =
* Added arbitrary radii control to Maps -> Settings -> Store Locator
* Added modern store locator look and feel
* Added modern store locator radius
* Added custom JS field in Maps -> Settings -> Advanced
* Added spatial types to marker table
* Added Google API Error handler and alert
* Added code to display custom fields in infowindow when Pro is installed
* Fresh install "My First Map" defaults to modern store locator and radius
* Relaxed theme data parsing
* Disabled Street View, zoom controls, pan controls and map type controls on fresh installs
= 6.4.08 - 2018-01-14 - Medium priority =
* Update Google Maps API versions to include 3.30 and 3.31
* On first installation, users are now taken to the welcome page
* Updated contributors
* Updated credits page
* Fixed broken support links
* Got things ready for the new Version 7 that is on its way
= 6.4.07 - 2018-01-08 - Low priority =
* Added a deactivation survey to gain insight before moving to Version 7
* Tested on WP 4.9.1
= 6.4.06 - 2017-09-07 - Medium Priority =
* Bug Fix: Zoom level is not respected when saving
= 6.4.05 - 2017-06-13 - Medium priority =
* Fixed the bug that caused JS errors to show up in the map editor
* Fixed a bug that caused the XML File option (for markers) to cause issues when trying to add a marker in the backend
* Allowed users to hide the subscribe feature in the plugins page
* New feature: Bulk delete markers
* Autocomplete now works when adding markers
* Autocomplete now works for the store locator on the front end
* Fixed a bug that caused the map to not load in the map editor for new installations
= 6.4.04 - 2017-06-08 - Low priority =
* Tested on WordPress 4.8
* Refactored the admin JS code
= 6.4.03 - 2017-02-17 - Low priority =
* Added the ability for affiliates to make use of their affiliate IDs in the pro links
* Added better SSL support
* Added shortcode support for XML marker files
= 6.4.02 - 2017-01-20 - Low priority =
* Removed an echo that was incorrectly placed
= 6.4.01 - 2017-01-20 - Low priority =
* Added the ability for users to subscribe to our mailing list
= 6.4.00 - 2017-01-11 - Low priority =
* Documented all PHP functions
* Added an option to set default store locator address
* Full screen map functionality added
* Fixed a bug that caused custom css to be incorrectly escaped
* Fixed the bug that caused the "save marker" button to not revert when an address couldnt be geocoded
* Added caching notices to notify users to clear their cache when a marker is added or edited or when map settings were changed
* Estonian translation added
* Fixed the incorrect locale setting with the Google Maps API
* Fixed a bug that caused the admin style sheet to load on all admin pages
* Added the ability to change the gesture input
* Fixed a bug that caused PHP warnings when a polygon or polyline had no polydata
* Fixed a bug that caused non-utf8 characters within an address to cause the insertion of the marker to fail
= 6.3.20 - 2016-09-27 =
* Fixed a big that prevented the map from loading in a widget
* Refactored code used to load the Google Maps API and Script files
= 6.3.19 - 2016-09-21 =
* Fixed a bug that caused some maps to not load markers on page load
= 6.3.18 - 2016-09-15 =
* Chinese support - when your language is set to Chinese (ZN_cn), the map will now load from maps.google.cn
* Hebrew language code fixed when accessing the Google Maps API in Hebrew
* Added support for the KML layer to be visible when adding/editing polygons or polylines
* Fixed a bug with the store locator not using miles when selected
* Moved up to versions 3.25 and 3.26 of the Google Maps JavaScript API
* Datatables updated
* When a marker is deleted, the view does not reset
* User javascript has been ported over to a JavaScript file
* A minimifed and unminified version of the user-side JS file is now included - The minifed version is used by default
* You can now set the zoom level via the shortcode. Example: [wpgmza id='1' zoom=8]
* Fixed a PHP warning on the error log page
= 6.3.17 - 2016-08-07 - Medium priority =
* Added a temporary Google Maps JavaScript API key for users so that the UX is not negatively affected on the user's first attempt at using the plugin.
* Added a check to the front end to only display the map if there is an Google Maps JavaScript API key saved
* Fixed bugs that caused PHP warnings within the store locator
* UX improvements to the welcome page
* Fixed a bug that caused a JS error as a result of the previous versions new tab support
= 6.3.16 - 2016-08-02 - Low priority =
* API key is now used on the edit polyline page
* Removed the resizing script that caused the map to flicker on mobile devices
* Added additional tab support (tri-tabs-nav span)
* Fixed a bug in the store locator country restriction list
= 6.3.15 - 2016-07-31 - High priority =
* Security patches
* Code refactoring
= 6.3.14 - 2016-07-13 - High priority =
* Many security patches - thank you Gerard Arall
* Bug fix - trim whitespace before and api the Google Maps API key
* Additional tab support added
* Corrected PHP noticess
= 6.3.13 - 2016-07-05 - Medium priority =
* Revised Maps API Dequeue Script Added
* Remove Style dequeue script as this was causing UI conflicts
* Added option to disable Maps API from being loaded on front end
= 6.3.12 - 2016-06-27 - Medium priority =
* Modified the API key notification to make it simpler and more intuitive
= 6.3.11 - 2016-06-24 - Medium Priority =
* Small activation bug fixed
* all polygons and polylines are now viewable when editing or creating a new polygon or polyline
* Notifications of Google Maps API key requirements
= 6.3.10 - 2016-05-03 - Low priority =
* Added event listeners for both jQuery and accordions so that the map can init correctly when placed in a tab or accordion
* Added checks to stop themes and plugins from loading the Google Maps API over and above our call to the API on pages that contain the map shortcode
* Fixed an SSL issue with the marker URL (Thank you David Clough)
* Fixed a bug that caused the CSS file to be loaded on all front end pages
* Added SSL support to the jQuery CDN file
= 6.3.09 - 2016-04-15 - High priority =
* Deprecated google maps api 3.14 and 3.15, added 3.23 and 3.24
= 6.3.08 - 2016-04-14 - Medium Priority =
* Provides a workaround for users experiencing issues with their maps loading after updating to WordPress 4.5
= 6.3.07 - 2016-04-13 - Low Priority =
* Tested on WordPress 4.5
* You can now use your own Google Maps API key for your maps
= 6.3.06 - 2016-04-04 - Low Priority =
* Indonesian Translation added - Thank you Neno
* Swedish Translation added - Thank you Martin Sleipner
* Bulgarian Translation added - Thank you Lyubomir Kolev
* Google Maps API sensor removed from API call
= 6.3.05 - 2016-01-14 - Low priority =
* Multiple tab compatibility added
= 6.3.04 - 2016-01-04 - Low priority =
* Tested with WP 4.4
= 6.3.03 - 2015-11-19 - Low Priority =
* Fixed a bug that caused the map to not display when a theme was not selected
= 6.3.02 - 2015-11-06 - Low priority =
* A new theme directory has been created - this allows you to use any map theme or style that you want simply by copying and pasting it's data
= 6.3.01 - 2015-10-06 - Low priority =
* Added 3 new google map custom themes
* Corrected internationalization
* iPhone map marker styling fix
* Fixed an autocomplete bug
* All WP Google Maps language files have been updated
= 6.3.00 - 2015-09-02 - Low priority =
* Added 5 map themes to the map editor
* Added a native map widget so you can drag and drop your maps to your widget area
* Minor bug fixes
* Language files updated
* Turkish translation added - thank you Suha Karalar
= 6.2.3 - 2015-08-20 - High priority =
* Included the latest version of datatables to fix the bug experienced with the new jQuery being included in WordPress 4.3
* Updated datatables.responsive to 1.0.7 and included the minified version of the file instead
* Fixed a few styling bugs in the map editor
= 6.2.2 - Security Update - 2015-07-27 - High Priority =
* Security patch
* Tested with WP 4.2.3
= 6.2.1 - Security Update - 2015-07-13 - High Priority =
* Security enhancements to the map editor page, map javascript, marker categories and front end code
= 6.2.0 - Liberty Update - 2015-06-24 - Medium Priority =
* Security enhancements (map editor, marker location, map settings)
* Weather has been removed (deprecated by Google Maps)
* Major bug fix (Google Map places bug) - caused the map markers not to show if the map store locator was not enabled
* Fixed a bug that caused the jQuery error message to display briefly before the map loaded
* Fixed a bug that caused the max map zoom to default back to 3
= 6.1.10 - 2015-06-10 - High priority =
* XSS security patch
* Security enhancements
* Fixed a bug that didnt allow you to add a map marker if there were no markers to start with
= 6.1.9 - 2015-06-01 - Low priority =
* Fixed french translation bug
= 6.1.8 - 2015-05-27 - Low priority =
* Greek translation added - Thank you Konstantinos Koukoulakis
* Added the Google Maps autocomplete functionality to the "add marker" section of the map editor
* Added the Google Maps autocomplete functionality to the Store Locator
= 6.1.7 - 2015-04-22 - Low priority =
* json_encode (extra parameter) issue fixed for hosts using PHP version < 5.3
= 6.1.6 - 2015-04-17 - Low priority =
* Rocketscript fix (Cloudfare)
* Dutch translation added
* Main translation file updated
= 6.1.5 - 2015-03-16 - High priority =
* Timthumb removed
* New support page added
* You can now restrict your store locator search by a specific country
* Bug fix in map editor
* SSL bug fix
* Usability Improvements when right clicking to add a marker on the map.
= 6.1.4 - 2015-02-13 =
* Safari bug fix
* Fixed issues with map markers containing addresses with single quotes
* You can now set the max zoom of your google map
= 6.1.3 - 2015-01-19 =
* IIS 500 server error fix
* Small map bug fixes
* Brazilian portuguese language file updated
* Activation error fixes
= 6.1.2 2015-01-19 =
* Code improvements (PHP warnings)
* Tested in WordPress 4.1
= 6.1.1 2014-12-19 =
* Code improvements
= 6.1.0 2014-12-17 =
* Added an alternative method to pull the marker data
= 6.0.32 =
* Comprehensive checks added to the Marker XML Dir field
= 6.0.31 2014-11-28 =
* Category bug fix
= 6.0.30 2014-11-26 =
* Added a check for the DOMDocument class
* Removed the APC Object Cache warning
* Added new strings to the PO file
= 6.0.29 =
* New option: You can now show or hide the Store Locator bouncing icon
* New feature: Add custom CSS in the settings page
* Code improvements
= 6.0.28 =
* Enfold / Avia theme conflict resolved (Google Maps API loading twice)
* Better marker file/directory control
* Italian translation added (Tommaso Mori)
= 6.0.27 - 2014-09-29 =
* French translation updated by Arnaud Thomas
* Security updates (thank you www.htbridge.com)
* Fixed the bug that wouldnt allow you to select the Google maps API version
* Code improvements (PHP warnings)
* Google Map Store Locator bug fix - map zoom levels on 300km, 150km and 75km were incorrect
= 6.0.26 =
* Attempting to fix the "is_dir" and "open_basedir restriction" errors some users are experiencing.
* Updated timthumb to version 2.8.14
* Altered all instances of "is_dir" in timthumb.php (causing fatal errors on some hosts) and replace it with 'file_exists'
= 6.0.25 =
* Removed the use of "is_dir" which caused fatal errors on some hosts
= 6.0.24 =
* Added extra support for folder management and error reporting
* Code improvements (PHP Warnings)
* Better polygon and polyline handling
* Hebrew translation added
= 6.0.23 =
* Added extra support for corrupt polyline and polygon data
= 6.0.22 =
* Fixed incorrect warning about permissions when permissions where "2755" etc.
* Add classes to the google map store locator elements
= 6.0.21 =
* Backend UI improvement
* You can now right click to add a marker to the map
* New markers can be dragged
* Polygons and polylines now have labels
* Small bug fixes
= 6.0.20 =
* You can now set the query string for the store locator
= 6.0.19 =
* Fixed a bug that caused the marker file to be recreated on every page load in some instances.
* Fixed a marker listing display bug (iPhone)
* Now showing default settings for marker path and URL
* Removed the "map could not load" error
* Fixed a bug that when threw off gps co-ordinates when adding a lat,lng as an address
= 6.0.18 =
* You can now select which roles can access the map editor
= 6.0.17 =
* Minor update: PO files updated
= 6.0.16 =
* You can now choose which folder your markers are saved in
* Better error reporting for file permission issues
= 6.0.15 =
* Small bug fixes
* Map marker location bug fix
* Russian translation added by Borisa Djuraskovic
= 6.0.14 =
* Code improvements
* Added option for selecting Celsius or Fahrenheit with the Google Maps weather layer
= 6.0.13 =
* Fixed PHP warnings and the plugin is now PHP 5.5 compatible
= 6.0.12 =
* Fixed a google map marker XML file location bug
= 6.0.11 =
* Small bug fix on the WP Google Maps welcome page
= 6.0.10 =
* Tested on WP 3.9
* Fixed a bug that only displayed two map marker categories for the store locator (pro)
* Added the option to select which Google Map API version you would like to use. There were issues when using Google Map API v3.15 (lines were created on the map for no reason. The default is now Google Map API V3.14)
* 6.0.9
* Maps now automatically work in Tabs without having to add any code
* Added a "zoom level" slider to the Google map settings
* Added a check for GoDaddy Wordpress hosting and the APC object cache due to the issues that arise while using it
* Fixed a polyline bug
* Added "stroke opacity" options to polygons
* Added a warning when users want to use % for the map height
* 6.0.8
* Fixed a Mac Firefox style issue with the WP Google Maps Store Locator
* Fixed a function error in the polyline functions file
* 6.0.7
* Upgrading of plugin is now handled correctly
* 6.0.6
* Multisite bug fixes
* XML marker file bug fixes (thank you Endymion00)
* 6.0.5
* Markers are now stored in the uploads folder
* Small bug fixes
* 6.0.4
* Performance update
* 6.0.3
* Small bug fix
* 6.0.2
* Style bug fix
* 6.0.1
* Small bug fix
* 6.0.0
* Fixed a map width bug with the datatables layout. Now falls in line with the map width.
* Added more options to the map settings page
* Fixed a bug that forced a new geocode on every marker edit, even if the address wasnt changed
* Updated TimThumb from 2.8.11 to 2.8.13
* You can now choose for your map InfoWindows to open from mouse click or hover
* Better error handling when the map cannot show due to conflicts or JS errors
* Fixed the bug that caused high memory usage
* Major bug fixes
* 5.24
* Bug fix - The map style changed the style of your theme.
* 5.23
* Add animations to your map markers (lite)
* Choose to have the infowindow open by default (lite)
* Add the bicycle and traffic layer to your map (lite)
* Substantial coding improvements and bug fixes
* 5.22
* Fixed the marker sort order bug
* 5.21
* Fixed a bug that if clicking the "add maker" button produced an error, the "add marker" button would disappear.
* 5.20
* Categories can now be hidden from the marker list
* German translation added thanks to Matteo Ender
* 5.19
* Fixed a styling bug with Firefox
* Fixed the bug that caused all markers to be lost upon upgrading
* 5.18
* Added improved styling to the address in the map infowindow
* 5.17
* Fixed update bug
* 5.16
* Plugin now checks to see if the Google Maps API is already loaded before trying to load it again
* Fixed some SSL bugs
* 5.15
* Added marker category functionality
* Added Google Map Mashup functionality
* Fixed small bugs
* Added backwards compatibility for older versions of WordPress
* Replaced deprecated WordPress function calls
* Added Spanish translation - Thank you Fernando!
* 5.14
* The map plugin now uses the new media manager
* Fixed some styling conflicts
* Added missing strings to localization
* Updated to the latest Timthumb version
* 5.13
* Fixed a small bug
* 5.12
* Removed deprecated code
* 5.11
* Added SSL bug fixes
* Fixed a bug that wasnt allowing users to edit the exact location
For more, please view the WP Google Maps site
home/bechata/mp/wp-content/plugins/wp-super-cache/readme.txt 0000666 00000171566 15175466470 0020142 0 ustar 00 # WP Super Cache #
* Contributors: donncha, automattic
* Tags: performance, caching, wp-cache, wp-super-cache, cache
* Tested up to: 5.7.2
* Stable tag: 1.7.4
* Requires at least: 3.1
* Requires PHP: 5.2.4
* License: GPLv2 or later
* License URI: https://www.gnu.org/licenses/gpl-2.0.html
A very fast caching engine for WordPress that produces static html files.
## Description ##
This plugin generates static html files from your dynamic WordPress blog. After a html file is generated your webserver will serve that file instead of processing the comparatively heavier and more expensive WordPress PHP scripts.
The static html files will be served to the vast majority of your users:
* Users who are not logged in.
* Users who have not left a comment on your blog.
* Or users who have not viewed a password protected post.
99% of your visitors will be served static html files. One cached file can be served thousands of times. Other visitors will be served custom cached files tailored to their visit. If they are logged in, or have left comments those details will be displayed and cached for them.
The plugin serves cached files in 3 ways (ranked by speed):
1. Expert. The fastest method is by using Apache mod_rewrite (or whatever similar module your web server supports) to serve "supercached" static html files. This completely bypasses PHP and is extremely quick. If your server is hit by a deluge of traffic it is more likely to cope as the requests are "lighter". This does require the Apache mod_rewrite module (which is probably installed if you have custom permalinks) and a modification of your .htaccess file which is risky and may take down your site if modified incorrectly.
2. Simple. Supercached static files can be served by PHP and this is the recommended way of using the plugin. The plugin will serve a "supercached" file if it exists and it's almost as fast as the mod_rewrite method. It's easier to configure as the .htaccess file doesn't need to be changed. You still need a custom permalink. You can keep portions of your page dynamic in this caching mode.
3. WP-Cache caching. This is mainly used to cache pages for known users, URLs with parameters and feeds. Known users are logged in users, visitors who leave comments or those who should be shown custom per-user data. It's the most flexible caching method and slightly slower. WP-Cache caching will also cache visits by unknown users if supercaching is disabled. You can have dynamic parts to your page in this mode too. This mode is always enabled but you can disable caching for known users, URLs with parameters, or feeds separately. Set the constant "DISABLE_SUPERCACHE" to 1 in your wp-config.php if you want to only use WP-Cache caching.
If you're not comfortable with editing PHP files then use simple mode. It's easy to set up and very fast.
### Recommended Settings ###
1. Simple caching.
2. Compress pages.
3. Don't cache pages for known users.
4. Cache rebuild.
5. CDN support.
6. Extra homepage checks.
Garbage collection is the act of cleaning up cache files that are out of date and stale. There's no correct value for the expiry time but a good starting point is 1800 seconds.
Consider deleting the contents of the "Rejected User Agents" text box and allow search engines to cache files for you.
Preload as many posts as you can and enable "Preload Mode". Garbage collection of old cached files will be disabled. If you don't care about sidebar widgets updating often set the preload interval to 2880 minutes (2 days) so all your posts aren't recached very often. When the preload occurs the cache files for the post being refreshed is deleted and then regenerated. Afterwards a garbage collection of all old files is performed to clean out stale cache files.
Even with preload mode enabled cached files will still be deleted when posts are modified or comments made.
### Development ###
* Active development of this plugin is handled [on GitHub](https://github.com/Automattic/wp-super-cache).
* Translation of the plugin into different languages is on the [translation page](https://translate.wordpress.org/projects/wp-plugins/wp-super-cache).
### Documentation ###
If you need more information than the following, you can have a look at the [Developer documentation](https://odd.blog/wp-super-cache-developers/).
#### Preloading ####
You can generate cached files for the posts, categories and tags of your site by preloading. Preloading will visit each page of your site generating a cached page as it goes along, just like any other visitor to the site. Due to the sequential nature of this function, it can take some time to preload a complete site if there are many posts.
To make preloading more effective it can be useful to disable garbage collection so that older cache files are not deleted. This is done by enabling "Preload Mode" in the settings. Be aware however, that pages will go out of date eventually but that updates by submitting comments or editing posts will clear portions of the cache.
#### Garbage Collection ####
Your cache directory fills up over time, which takes up space on your server. If space is limited or billed by capacity, or if you worry that the cached pages of your site will go stale then garbage collection has to be done. Garbage collection happens on a regular basis and deletes old files in the cache directory. On the advanced settings page you can specify:
1. Cache timeout. How long cache files are considered fresh for. After this time they are stale and can be deleted.
2. Scheduler. Setup how often garbage collection should be done.
3. Notification emails. You can be informed on garbage collection job progress.
There's no right or wrong settings for garbage collection. It depends on your own site.
If your site gets regular updates, or comments then set the timeout to 1800 seconds, and set the timer to 600 seconds.
If your site is mostly static you can disable garbage collection by entering 0 as the timeout, or use a really large timeout value.
The cache directory, usually wp-content/cache/ is only for temporary files. Do not ever put important files or symlinks to important files or directories in that directory. They will be deleted if the plugin has write access to them.
#### CDN ####
A Content Delivery Network (CDN) is usually a network of computers situated around the world that will serve the content of your website faster by using servers close to you. Static files like images, Javascript and CSS files can be served through these networks to speed up how fast your site loads. You can also create a "poor man's CDN" by using a sub domain of your domain to serve static files too.
[OSSDL CDN off-linker](https://wordpress.org/plugins/ossdl-cdn-off-linker/) has been integrated into WP Super Cache to provide basic CDN support. It works by rewriting the URLs of files (excluding .php files) in wp-content and wp-includes on your server so they point at a different hostname. Many CDNs support [origin pull](https://www.google.com/search?hl=en&q=%22origin+pull%22). This means the CDN will download the file automatically from your server when it's first requested, and will continue to serve it for a configurable length of time before downloading it again from your server.
Configure this on the "CDN" tab of the plugin settings page. This is an advanced technique and requires a basic understanding of how your webserver or CDNs work. Please be sure to clear the file cache after you configure the CDN.
#### REST API ####
There are now REST API endpoints for accessing the settings of this plugin. You'll need to be authenticated as an admin user with permission to view the settings page to use it. This has not been documented yet but you can find all the code that deals with this in the "rest" directory.
#### Custom Caching ####
It is now possible to hook into the caching process using the add_cacheaction() function.
Three hooks are available:
1. 'wp_cache_get_cookies_values' - modify the key used by WP Cache.
2. 'add_cacheaction' - runs in phase2. Allows a plugin to add WordPress hooks.
3. 'cache_admin_page' - runs in the admin page. Use it to modify that page, perhaps by adding new configuration options.
There is one regular WordPress filter too. Use the "do_createsupercache" filter
to customize the checks made before caching. The filter accepts one parameter.
The output of WP-Cache's wp_cache_get_cookies_values() function.
WP Super Cache has its own plugin system. This code is loaded when WP Super Cache loads and can be used to change how caching is done. This is before most of WordPress loads so some functionality will not be available. Plugins can be located anywhere that PHP can load them. Add your own plugin either:
* by putting your plugin in the wp-content/plugins/wp-super-cache-plugins directory, or
* by calling wpsc_add_plugin( $name ) where $name is the full filename and path to the plugin. You only need to call that function once to add it. Use wpsc_delete_plugin( $name ) to remove it from the list of loaded plugins.
The cookies WP Super Cache uses to identify "known users" can be modified now by adding the names of those cookies to a list in the plugin configuration. Use wpsc_add_cookie( $name ) to add a new cookie, and wpsc_delete_cookie( $name ) to remove it. The cookie names also modify the mod_rewrite rules used by the plugin but I recommend using Simple mode caching to avoid complications with updating the .htaccess file.
The cookie name and value are used to differenciate users so you can have one cookie, but different values for each type of user on your site for example. They'll be served different cache files.
See [plugins/searchengine.php](https://github.com/Automattic/wp-super-cache/blob/4cda5c0f2218e40e118232b5bf22d227fb3206b7/plugins/searchengine.php) as an example I use for my [No Adverts for Friends](https://odd.blog/no-adverts-for-friends/) plugin.
### Troubleshooting ###
If things don't work when you installed the plugin here are a few things to check:
1. Is wp-content writable by the web server?
2. Is there a wp-content/wp-cache-config.php ? If not, copy the file wp-super-cache/wp-cache-config-sample.php to wp-content/wp-cache-config.php and make sure WPCACHEHOME points at the right place.
3. Is there a wp-content/advanced-cache.php ? If not, then you must copy wp-super-cache/advanced-cache.php into wp-content/. You must edit the file and change the path so it points at the wp-super-cache folder.
4. If pages are not cached at all, remove wp-content/advanced-cache.php and recreate it, following the advice above.
5. Make sure the following line is in wp-config.php and it is ABOVE the "require_once(ABSPATH.'wp-settings.php');" line:
`define( 'WP_CACHE', true );`
6. Try the Settings->WP Super Cache page again and enable cache.
7. Look in wp-content/cache/supercache/. Are there directories and files there?
8. Anything in your php error_log?
9. If your browser keeps asking you to save the file after the super cache is installed you must disable Super Cache compression. Go to the Settings->WP Super Cache page and disable it there.
10. The plugin does not work very well when PHP's safe mode is active. This must be disabled by your administrator.
11. If pages are randomly super cached and sometimes not, your blog can probably be viewed with and without the "www" prefix on the URL. You should choose one way and install the [Enforce www preference](http://txfx.net/code/wordpress/enforce-www-preference/) plugin if you are using an old WordPress install. The latest versions redirect themselves (you should always be running the latest version of WordPress anyway!)
12. Private Server users at Dreamhost should edit wp-content/wp-cache-config.php and set the cache dir to "/tmp/" if they are getting errors about increasing CPU usage. See this [discussion](https://wordpress.org/support/topic/145895?replies=42) for more.
13. File locking errors such as "failed to acquire key 0x152b: Permission denied in..." or "Page not cached by WP Super Cache. Could not get mutex lock." are a sign that you may have to use file locking. Edit wp-content/wp-cache-config.php and uncomment "$use_flock = true" or set $sem_id to a different value. You can also disable file locking from the Admin screen as a last resort.
14. Make sure cache/wp_cache_mutex.lock is writable by the web server if using coarse file locking.
15. The cache folder cannot be put on an NFS or Samba or NAS share. It has to be on a local disk. File locking and deleting expired files will not work properly unless the cache folder is on the local machine.
16. Garbage collection of old cache files won't work if WordPress can't find wp-cron.php. If your hostname resolves to 127.0.0.1 it could be preventing the garbage collection from working. Check your access_logs for wp-cron.php entries. Do they return a 404 (file not found) or 200 code? If it's 404 or you don't see wp-cron.php anywhere WordPress may be looking for that script in the wrong place. You should speak to your server administator to correct this or edit /etc/hosts on Unix servers and remove the following line. Your hostname must resolve to the external IP address other servers on the network/Internet use. See http://yoast.com/wp-cron-issues/ for more. A line like "127.0.0.1 localhost localhost.localdomain" is ok.
`127.0.0.1 example.com`
17. If old pages are being served to your visitors via the supercache, you may be missing Apache modules (or their equivalents if you don't use Apache). 3 modules are required: mod_mime, mod_headers and mod_expires. The last two are especially important for making sure browsers load new versions of existing pages on your site.
18. The error message, "WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed!" appears at the end of every page. Open the file wp-content/advanced-cache.php in your favourite editor. Is the path to wp-cache-phase1.php correct? This file will normally be in wp-content/plugins/wp-super-cache/. If it is not correct the caching engine will not load.
19. Caching doesn't work. The timestamp on my blog keeps changing when I reload. Check that the path in your .htaccess rules matches where the supercache directory is. You may have to hardcode it. Try disabling supercache mode.
20. If supercache cache files are generated but not served, check the permissions on all your wp-content/cache/supercache folders (and each of wp-content cache and supercache folders) and wp-content/cache/.htaccess. If your PHP runs as a different user to Apache and permissions are strict Apache may not be able to read the PHP generated cache files. To fix you must add the following line to your wp-config.php (Add it above the WP_CACHE define.) Then clear your cache.
`umask( 0022 );`
21. If you see garbage in your browser after enabling compression in the plugin, compression may already be enabled in your web server. In Apache you must disable mod_deflate, or in PHP zlib compression may be enabled. You can disable that in three ways. If you have root access, edit your php.ini and find the zlib.output_compression setting and make sure it's "Off" or add this line to your .htaccess:
`php_flag zlib.output_compression off`
If that doesn't work, add this line to your wp-config.php:
`ini_set('zlib.output_compression', 0);`
22. The "white screen of death" or a blank page when you visit your site is almost always caused by a PHP error but [it may also be caused by APC](http://www.johnberns.com/2010/03/19/wp-super-cache-blank-page-problem-fixed/). Disable that PHP extension if you have trouble and replace with eAccelerator or Xcache.
23. After uninstalling, your permalinks may break if you remove the WordPress mod_rewrite rules too. Regenerate those rules by visiting the Settings->Permalink page and saving that form again.
24. If your blog refuses to load make sure your wp-config.php is correct. Are you missing an opening or closing PHP tag?
25. Your front page is ok but posts and pages give a 404? Go to Settings->permalinks and click "Save" once you've selected a custom permalink structure. You may need to manually update your .htaccess file.
26. If certain characters do not appear correctly on your website your server may not be configured correctly. You need to tell visitors what character set is used. Go to Settings->Reading and copy the 'Encoding for pages and feeds' value. Edit the .htaccess file with all your Supercache and WordPress rewrite rules and add this at the top, replacing CHARSET with the copied value. (for example, 'UTF-8')
`AddDefaultCharset CHARSET`
27. Use [Cron View](https://wordpress.org/plugins/cron-view/) to help diagnose garbage collection and preload problems. Use the plugin to make sure jobs are scheduled and for what time. Look for the wp_cache_gc and wp_cache_full_preload_hook jobs.
18. The error message, "WP Super Cache is installed but broken. The constant WPCACHEHOME must be set in the file wp-config.php and point at the WP Super Cache plugin directory." appears at the end of every page. You can delete wp-content/advanced-cache.php and reload the plugin settings page or edit wp-config.php and look for WPCACHEHOME and make sure it points at the wp-super-cache folder. This will normally be wp-content/plugins/wp-super-cache/ but you'll likely need the full path to that file (so it's easier to let the settings page fix it). If it is not correct the caching engine will not load.
19. If your server is running into trouble because of the number of semaphores used by the plugin it's because your users are using file locking which is not recommended (but is needed by a small number of users). You can globally disable file locking by defining the constant WPSC_DISABLE_LOCKING, or defining the constant WPSC_REMOVE_SEMAPHORE so that sem_remove() is called after every page is cached but that seems to cause problems for other processes requesting the same semaphore. Best to disable it.
20. Set the variable $htaccess_path in wp-config.php or wp-cache-config.php to the path of your global .htaccess if the plugin is looking for that file in the wrong directory. This might happen if you have WordPress installed in an unusual way.
## Installation ##
Install like any other plugin, directly from your plugins page but make sure you have custom permalinks enabled. Go to the plugin settings page at Settings->WP Super Cache and enable caching.
### How to uninstall WP Super Cache ###
Almost all you have to do is deactivate the plugin on the plugins page. The plugin should clean up most of the files it created and modified, but it doesn't as yet remove the mod_rewrite rules from the .htaccess file. Look for the section in that file marked by SuperCache BEGIN and END tags. The plugin doesn't remove those because some people add the WordPress rules in that block too.
To manually uninstall:
1. Turn off caching on the plugin settings page and clear the cache.
2. Deactivate the plugin on the plugins page.
3. Remove the WP_CACHE define from wp-config.php. It looks like `define( 'WP_CACHE', true );`
4. Remove the Super Cache mod_rewrite rules from your .htaccess file.
5. Remove the files wp-content/advanced-cache.php and wp-content/wp-cache-config.php
6. Remove the directory wp-content/cache/
7. Remove the directory wp-super-cache from your plugins directory.
### If all else fails and your site is broken ###
1. Remove the WP_CACHE define from wp-config.php. It looks like `define( 'WP_CACHE', true );`
2. Remove the rules (see above) that the plugin wrote to the .htaccess file in your root directory.
3. Delete the wp-super-cache folder in the plugins folder.
4. Optionally delete advanced-cache.php, wp-cache-config.php and the cache folder in wp-content/.
## Frequently Asked Questions ##
### How do I know my blog is being cached? ###
Go to Settings -> WP Super Cache and look for the "Cache Tester" form on the easy settings page. Click "Test Cache" and the plugin will request the front page of the site twice, comparing a timestamp on each to make sure they match.
If you want to do it manually, enable debugging in the plugin settings page and load the log file in a new browser tab. Then view your blog while logged in and logged out. You should see activity in the log. View the source of any page on your site. When a page is first created, you'll see the text "Dynamic page generated in XXXX seconds." and "Cached page generated by WP-Super-Cache on YYYY-MM-DD HH:MM:SS" at the end of the source code. On reload, a cached page will show the same timestamp so wait a few seconds before checking.
If Supercaching is disabled and you have compression enabled, the text "Compression = gzip" will be added. If compression is disabled and the page is served as a static html file, the text "super cache" will be added. The only other way to check if your cached file was served by PHP script or from the static cache is by looking at the HTTP headers. PHP cached pages will have the header "WP-Super-Cache: Served supercache file from PHP". WPCache cached files will have the header, "WP-Super-Cache: Served WPCache cache file". You should also check your cache directory in wp-content/cache/supercache/hostname/ for static cache files.
If the plugin rules are missing from your .htaccess file, the plugin will attempt to serve the super cached page if it's found. The header "WP-Super-Cache: Served supercache file from PHP" if this happens.
The pagespeed module for Apache may cause problems when testing. Disable it if you notice any problems running the cache tester.
### How do I disable Supercaching? ###
If you only want to use the WP-Cache engine then edit your wp-config.php or create an mu-plugin that sets the constant 'DISABLE_SUPERCACHE' to 1.
### WP-Cache vs Supercache files ###
All cache files are stored in wp-content/cache/supercache/HOSTNAME/ where HOSTNANE is your domain name. The files are stored in directories matching your site's permalink structure. Supercache files are index.html or some variant of that, depending on what type of visitor hit the blog. Other files are named wp-cache-XXXXXXXXXXXXXXXXX.php. Associated meta filesnames start with "meta". Those files contain information about the cached file. These files are generated by the "WPCache caching" engine in the plugin.
### Will comments and other dynamic parts of my blog update immediately? ###
Comments will show as soon as they are moderated, depending on the comment policy of the blog owner. Other dynamic elements on a page may not update unless they are written in Javascript, Flash, Java or another client side browser language. The plugin really produces static html pages. No PHP is executed when those pages are served. "Popularity Contest" is one such plugin that will not work.
### Will the Super Cache compression slow down my server? ###
No, it will do the opposite. Super Cache files are compressed and stored that way so the heavy compression is done only once. These files are generally much smaller and are sent to a visitor's browser much more quickly than uncompressed html. As a result, your server spends less time talking over the network which saves CPU time and bandwidth, and can also serve the next request much more quickly.
### How do I make certain parts of the page stay dynamic? ###
Note: this functionality is disabled by default. You will have to enable it on the Advanced Settings page.
There are 2 ways of doing this. You can use Javascript to draw the part of the page you want to keep dynamic. That's what Google Adsense and many widgets from external sites do and is the recommended way. Or you can use a WP Super Cache filter to do the job but you can't use mod_rewrite mode caching. You have to use the "simple" delivery method or disable supercaching.
WP Super Cache 1.4 introduced a cacheaction filter called wpsc_cachedata. The cached page to be displayed goes through this filter and allows modification of the page. If the page contains a placeholder tag the filter can be used to replace that tag with your dynamically generated html.
The function that hooks on to the wpsc_cachedata filter should be put in a file in the WP Super Cache plugins folder unless you use the late_init feature. An example plugin is included. Edit [dynamic-cache-test.php](http://svn.wp-plugins.org/wp-super-cache/trunk/plugins/dynamic-cache-test.php) to see the example code.
There are two example functions there. There's a simple function that replaces a string (or tag) you define when the cached page is served. The other example function uses an output buffer to generate the dynamic content. Due to a limitation in how PHP works the output buffer code MUST run before the wpsc_cachedata filter is hit, at least for when a page is cached. It doesn't matter when serving cached pages. See [this post](https://odd.blog/y/6j) for a more technical and longer explanation.
To execute WordPress functions you must enable the 'Late init' feature on the advanced settings page.
### How do I delay serving the cache until the "init" action fires? ###
Cached files are served before almost all of WordPress is loaded. While that's great for performance it's a pain when you want to extend the plugin using a core part of WordPress. Enable 'Late init' mode on the Advanced settings page and cached files will be served when "init" fires. WordPress and it's plugins will be loaded now.
### Why don't WP UserOnline, Popularity Contest, WP Postratings or plugin X not work or update on my blog now? ###
This plugin caches entire pages but some plugins think they can run PHP code every time a page loads. To fix this, the plugin needs to use Javascript/AJAX methods or the wpsc_cachedata filter described in the previous answer to update or display dynamic information.
### Why do my WP Super Cache plugins disappear when I upgrade the plugin? ###
WordPress deletes the plugin folder when it updates a plugin. This is the same with WP Super Cache so any modified files in wp-super-cache/plugins/ will be deleted. You can put your custom plugins in a different directory in a number of ways. You can define the variable $wp_cache_plugins_dir in wp-config.php or wp-content/wp-cache-config.php and point it at a directory outside of the wp-super-cache folder. The plugin will look there for it's plugins. Or if you distribute a plugin that needs to load early you can use the function `wpsc_add_plugin( $filename )` to add a new plugin wherever it may be. Use `wpsc_delete_plugin( $filename )` to remove the plugin file. See [#574](https://github.com/Automattic/wp-super-cache/pull/574/) or [this post](https://odd.blog/2017/10/25/writing-wp-super-cache-plugins/) on writing WP Super Cache plugins.
### What does the Cache Rebuild feature do? ###
When a visitor leaves a comment the cached file for that page is deleted and the next visitor recreates the cached page. A page takes time to load so what happens if it receives 100 visitors during this time? There won't be a cached page so WordPress will serve a fresh page for each user and the plugin will try to create a cached page for each of those 100 visitors causing a huge load on your server. This feature stops this happening. The cached page is not cleared when a comment is left. It is marked for rebuilding instead. The next visitor within the next 10 seconds will regenerate the cached page while the old page is served to the other 99 visitors. The page is eventually loaded by the first visitor and the cached page updated. See [this post](https://odd.blog/2009/01/23/wp-super-cache-089/) for more.
### Why doesn't the plugin cache requests by search engine bots by default? ###
Those bots usually only visit each page once and if the page is not popular there's no point creating a cache file that will sit idle on your server. However you can allow these visits to be cached by removing the list of bots from "Rejected User Agents" on the Advanced settings page.
### A category page is showing instead of my homepage ###
A tiny proportion of websites will have problems with the following configuration:
1. Uses a static page for the front page.
2. Uses /%category%/%postname%/ permalink structure.
Sometimes a category page is cached as the homepage of the site instead of the static page. I can't [replicate the problem](https://wordpress.org/support/topic/237415/page/2?replies=38) but a simple solution is to use the "Simple" mode. You can also enable "Extra homepage checks" on the Advanced Settings page.
### Why do I get warnings about caching from http://ismyblogworking.com/ ###
"Your blog doesn't support client caching (no 304 response to If-modified-since)."
"Your feed doesn't support caching (no 304 response to If-modified-since)"
Supercache doesn't support 304 header checks in Expert mode but does support it in Simple mode. This is caching done by your browser, not the server. It is a check your browser does to ask the server if an updated version of the current page is available. If not, it doesn't download the old version again. The page is still cached by your server, just not by your visitors' browsers.
Try the Cacheability Engine at http://www.ircache.net/cgi-bin/cacheability.py or https://redbot.org/ for further analysis.
### How should I best use the utm_source tracking tools in Google Analytics with this plugin? ###
That tracking adds a query string to each url linked from various sources like Twitter and feedreaders. Unfortunately it stops pages being supercached. See [Joost's comment here](https://odd.blog/remove-unused-utmsource-urls/#comment-672813) for how to turn it into an anchor tag which can be supercached.
### The plugin complains that wp-content is writable! htdocs is writable! ###
It's not good when the web server can write to these directories but sometimes shared hosting accounts are set up in this way to make administration easier. Use `chmod 755 directory` to fix the permissions or find the permissions section of your ftp client. This [Google search](https://www.google.com/search?sourceid=chrome&ie=UTF-8&q=ftp+fix+directory+permissions+755) will lead you to more information on this topic and there's also [this codex page](https://codex.wordpress.org/Changing_File_Permissions) too. Unfortunately some hosts require that those directories be writable. If that's the case just ignore this warning.
### How do I delete the WP_CACHE define from wp-config.php? ###
Load your desktop ftp client and connect to your site. Navigate to the root (or the directory below it) of your site where you'll find wp-config.php. Download that file and edit it in a text editor. Delete the line `define( 'WP_CACHE', true );` and save the file. Now upload it, overwriting the wp-config.php on your server.
### How do I delete the Super Cache rules from the .htaccess file? ###
Load your desktop ftp client and connect to your site. You may need to enable "Show hidden files" in the preferences of the ftp client. Navigate to the root of your site where you'll find the .htaccess file. Download that file and edit it in a text editor. Delete the lines between "# BEGIN WPSuperCache" and "# END WPSuperCache" and save the file. Now upload it, overwriting the .htaccess file on your server.
### How do I change file permissions? ###
This [page](https://codex.wordpress.org/Changing_File_Permissions) on the WordPress Codex explains everything you need to know about file permissions on your server and various ways of changing them.
### Why do I get load spikes when new posts are made? ###
You may have the "clear all cached files when new posts are made" option set. Clearing those files can take time plus your visitors will now be visiting uncached pages. Are you using Google Analytics campaign tracking with utm_source in the url? Those pages aren't cached. See the question, "How should I best use the utm_source tracking tools in Google Analytics with this plugin" above for how to use them properly.
Cached pages have to be refreshed when posts are made. Perhaps your server just isn't up to the job of serving the amount of traffic you get. Enable the "cache rebuild" feature as that may help.
### How many pages can I cache? ###
The only real limit are limits defined by your server. For example, EXT2 and EXT3 allow a maximum of 31,999 sub directories so if you have a flat permalink structure (like /%POSTNAME%/) and more than 32,000 posts you may run into problems. Likewise, if you run a multisite network and have more than 31,999 sites (blogs) you won't be able to cache all of them. Realistically if you had that many active sites you wouldn't be running on one server.
### I can see that the www version of my site is cached separately. How do I stop that? ###
WordPress should redirect to the canonical URL of your site but if it doesn't, add this to your .htaccess above the Supercache and WordPress rules. Change example.com to your own hostname.
`RewriteCond %{HTTP_HOST} www.example.com$ [NC]`
`RewriteRule ^(.*)$ https://example.com/$1 [L,R=301]`
### How do I serve cached mobile pages to clients on small screens like phones and tablets? ###
Your theme is probably responsive which means it resizes the page to suit whatever device is displaying the page. If it's not responsive, you'll have to use a separate mobile plugin to render a page formatted for those visitors. The following plugins have been tested but YMMV depending on mobile client. You'll have to enable mobile browser support as well on the Advanced settings page.
* [Jetpack's Mobile Theme Module](https://wordpress.org/plugins/jetpack/)
* [WPTouch](https://wordpress.org/plugins/wptouch/)
* [WordPress Mobile Edition](https://wordpress.org/plugins/wordpress-mobile-edition/)
* [WordPress Mobile Pack](https://wordpress.org/plugins/wordpress-mobile-pack/) (can't have "Don't cache pages for known users." enabled)
## Changelog ##
### 1.7.4 ###
* Make config file path configurable, props @sebastianpopp #755
* Stop a very rare/difficult attack when updating wp-config.php, props @guyasyou for reporting. #780
* Add textbox to add tracking parameters to ignore when caching. props @markfinst, @radex02 #777
* Add "Rejected Cookies" setting to the advanced settings page. #774
### 1.7.3 ###
* Sanitize the settings that are written to the config file #763
* Fix the display of "direct cached" example urls in some circumstance. #766
### 1.7.2 ###
* Fixed authenticated RCE in the settings page. Props @m0ze
* Small bug fixes.
### 1.7.1 ###
* Minor fixes to docs. #709 #645
* Fixed typo on cache contents page. #719
* Fixed array index warning. #724
* Updated yellow box links. #725
### 1.7.0 ###
* Added "wpsc_cdn_urls" filter to modify the URLs used to rewrite URLs. #697
* Fixed CDN functionality for logged in users. #698
* Disable settings that don't work in Expert mode. #699
* Don't enable mobile support by default, but it can still be enabled manually. #700
* Change "admin bar" to "Toolbar". Props @garrett-eclipse. #701
* Show settings enabled by "easy" settings page. #703
### 1.6.9 ###
* Improve the variables and messaging used by advanced-cache.php code. #687
* Add a warning message to the debug log viewer. #688
* Disable raw viewing of the debug log. #691
* Clean up the debug log. #692 #694
* Added wpsc_update_check() in 9659af156344a77ae247dc582d52053d95c79b93.
### 1.6.8 ###
* Added new constants, WPSC_SERVE_DISABLED (disable serving of cached files) and WPSC_SUPERCACHE_ONLY (only serve supercache cache files). #682 and #672
* Hide get_post() warning on some sites. #684
* Check if WPCACHEHOME is set correctly before maybe updating it. #683
* Remove object cache support as it never worked properly. #681
* Add "logged in users" to the "do not cache for users" setting and rename that setting to "Cache Restrictions" #657
### 1.6.7 ###
* wp_cache_setting() can now save boolean values since many of the settings are bools. #676
* Check if $super_cache_enabled is true in a less strict way because it might be '1' rather than true. #677
### 1.6.6 ###
* Fix problems with saving settings. Returns false ONLY when there's an issue with the config file, not when the setting isn't changed. Change other code to cope with that, including updating WPCACHEHOME (#670)
* When saving settings rename the temporary config file correctly, and delete wp-admin/.php if it exists. (#673)
* Fix adding WPCACHEHOME to wp-config.php when advanced-cache.php is not found and wp-config.php is RO. (#674)
### 1.6.5 ###
* Check advanced-cache.php was created by the plugin before modifying/deleting it. (#666)
* When saving settings, save blank lines. Fixes problems with WP_CACHE and WPCACHEHOME in wp-config.php. Related to #652. (#667)
* Update outdated code and use is_multisite() (#600)
* Fix the delete cache button in the Toolbar. (#603)
* Code cleanup in #602
* Use get_post_status instead of post_status (#623)
* Fixes button - Update Direct Pages (#622)
* Removes apache_response_headers and uses only headers_list (#618)
* Function is_site_admin has been deprecated (#611)
* Fixes action urls in wp_cache_manager (#610)
* Remove the link to the HibbsLupusTrust tweet. (#635)
* Don't load wp-cache-config.php if it's already loaded (#605)
* PHPCS fixes and optimization for plugins/domain-mapping.php (#615)
* Introduces PHP_VERSION_ID for faster checking (#604)
* Fixes regex and optimizes ossdl-cdn.php (#596)
* Only update new settings and use a temporary file to avoid corruption. (#652)
* Serve cached files to rejected user agents, don't cache them. (#658)
* Combine multiple headers with the same name (#641)
* Open ‘Delete Cache’ link in same window (#656)
* Promote the Jetpack Site Accelerator on the CDN page. (#636)
### 1.6.4 ###
* Changes between [1.6.3 and 1.6.4](https://github.com/Automattic/wp-super-cache/compare/1.6.3...1.6.4)
* Fixes for WP-CLI (#587) (#592)
* Bumped the minimum WordPress version to 3.1 to use functions introduced then. (#591)
* Fixes to wpsc_post_transition to avoid a fatal error using get_sample_permalink. (#595)
* Fixed the Toolbar "Delete Cache" link. (#589)
* Fixed the headings used in the settings page. (#597)
### 1.6.3 ###
* Changes between [1.6.2 and 1.6.3](https://github.com/Automattic/wp-super-cache/compare/1.6.2...1.6.3)
* Added cookie helper functions (#580)
* Added plugin helper functions (#574)
* Added actions to modify cookie and plugin lists. (#582)
* Really disable garbage collection when timeout = 0 (#571)
* Added warnings about DISABLE_WP_CRON (#575)
* Don't clean expired cache files after preload if garbage collection is disabled (#572)
* On preload, if deleting a post don't delete the sub directories if it's the homepage. (#573)
* Fix generation of semaphores when using WP CLI (#576)
* Fix deleting from the Toolbar (#578)
* Avoid a strpos() warning. (#579)
* Improve deleting of cache in edit/delete/publish actions (#577)
* Fixes to headers code (#496)
### 1.6.2 ###
* Fixed serving expired supercache files (#562)
* Write directly to the config file to avoid permission problems with wp-content. (#563)
* Correctly set the .htaccess rules on the main site of a multisite. (#557)
* Check if set_transient() exists before using it. (#565)
* Removed searchengine.php example plugin as it sets a cookie to track users. Still available [here](https://github.com/Automattic/wp-super-cache/blob/4cda5c0f2218e40e118232b5bf22d227fb3206b7/plugins/searchengine.php). (#567)
* For advanced users only. Change the vary and cache control headers. See https://github.com/Automattic/wp-super-cache/pull/555 (#555)
### 1.6.1 ###
* Fix the name of the WP Crontrol plugin. (#549)
* Handle errors during deactivation/uninstall by email rather than exiting. (#551)
* Add a notice when settings can't be updated. (#552 and #553)
### 1.6.0 ###
* Fix issues in multisite plugin (#501)
* Fixes wp-cli plugin deactivate/activate (#499)
* Cleanup - change quotes. (#495)
* $htaccess_path defines the path to the global .htacess file. (#507)
* Fix 'cannot redeclare gzip_accepted()' (#511)
* Correct the renaming of tmp_wpcache_filename (removed unnecessary slash in path) which caused renaming to fail. (#516)
* Add check for Jetpack mobile theme cookie (#515)
* Optimize wp_cache_phase2 and create wpsc_register_post_hooks (#508)
* WPCACHEHOME has a trailing slash (#513)
* Cleanup cache enable/disable and update_mod_rewrite_rules (#500)
* Post Update now clears category cache (#519)
* Various fixes for saving the debug page form (#542)
* Expert-caching and empty parameters, like ?amp, should not serve cached page (#533)
* Tiny Yslow description fix (#527)
* Add ipad to mobile list (#525)
* Hide opcache_invalidate() warnings since it's disabled some places. (#543)
* Check that HTTP_REFERER exists before checking it. (#544)
* Replace Cron View" with WP Crontrol because it's still updated. (#546)
* adding hook (wp_cache_cleared) for full cache purges (#537)
### 1.5.9 ###
* Fixed fatal error if the debug log was deleted while debugging was enabled and a visitor came to the site.
* Fixed the dynamic caching test plugin because of PHP7 changes. Dynamic cache mode must be enabled now.
* Lots of WordPress coding style formatting fixes to the code.
* All changes: https://github.com/Automattic/wp-super-cache/compare/1.5.8...1.5.9
### 1.5.8 ###
* PHP 7 fixes. (#429)
* Fix debug comments checkbox. (#433)
* Only register uninstall function in admin pages to save queries. (#430)
* Check that wp-cache-phase1.php is loaded before saving settings page. (#428)
* If a url has a "?" in it then don't delete the associated cache. It'll delete the whole cache after stripping out ?... part. (#427 & #420)
* Allow static functions in classes to be used in cacheactions. (#425)
* Don't make AJAX requests anonymous. (#423)
* Fixed link to chmod explanation. (#421)
* Add more escaping to the CDN settings page. (#416)
* Use SERVER_PROTOCOL to determine http protocol. (#412 & #413)
* If preload stalls only send one email per day, but do display an admin notice. (#432)
* Fixed more PHP warnings in #438 and #437
* Hide mod_rewrite warnings for Nginx users. #434
### 1.5.7.1 ###
* If the HTTP HOST is empty then don't use it in strpos to avoid a PHP warning. (#408)
* Don't preload posts with permalinks that contain rejected strings. (#407)
* Generate a list of archive feeds that can be deleted when the site is updated. Also fixes corrupted config file issue and fatal error with older versions of WordPress. (#403)
### 1.5.7 ###
* Fix fatal error in plugins/searchengine.php (#398)
### 1.5.6 ###
* REST API: Added /plugins endpoint to handle the plugins settings page. (#382)
* Minor changes to indentaion and spaces to tabs conversion (#371) (#395)
* Don't set $wp_super_cache_comments here as it's not saved. (#379)
* realpath() only works on directories. The cache_file wasn't set correctly. (#377)
* Fix problem deleting cache from Toolbar because of realpath() (#381)
* Use trigger_error() instead of echoing to the screen if a config file isn't writeable. (#394)
* Added the "wpsc_enable_wp_config_edit" filter to disable editing the wp-config.php (#392)
* Fix some PHP notices when comments are edited/published/maintained. (#386)
* Minor changes to description on plugins page. (#393)
### 1.5.5 ###
* Catch fatal errors so they're not cached, improve code that catches unknown page types. (#367)
* Fix caching on older WP installs, and if the plugin is inactive on a blog, but still caching, give feeds a short TTL to ensure they're fresh. (#366)
* When preloading don't delete sub-directories, or child pages, when caching pages. (#363)
* Avoid PHP warnings from the REST API for settings that are not yet defined. (#361)
* Added missing settings to the config file. (#360)
### 1.5.4 ###
* Fix messages related to creating advanced-cache.php (#355, #354)
* Deleting the plugin doesn't need to delete the cache directory as it's already done on deactivation. (#323)
* Disable Jetpack mobile detection if Jetpack Beta is detected. (#298)
* Add more checks on directories to make sure they exist before deleting them. (#324)
* Add siteurl setting to CDN page for users who have WordPress in it's own directory. (#332)
* Don't enable and then not save debug comments when toggling logging. (#334)
* Show plugin activity html comments to users who disable caching for logged in users. (#335)
* Better notifications on Preload page, and redo sql to fetch posts. Added "wpsc_preload_post_types_args" filter on post visibility, and wpsc_preload_post_types filter on post types used. (#336)
* Use a cached feed if it is newer than the last time a post was updated. (#337)
* Better define a sitemap (#340) but when the content type is unknown add more checks to find out what it is. (#346)
* Save cache location correctly on the advanced settings page. (#345)
* Make sure the debug log exists before toggling it on/off to ensure the http auth code is added to it.
* Return the correct cache type to the REST API. Ignore supercache enabled status. (#352)
* Fix cache contents in REST API showing double count of supercache files. (#353)
* Move the nonce in the CDN page back into a function. (#346)
* Use realpath to compare directories when loading the sample config file to account for symlinked directories. (#342)
* Other minor changes to html or typos
(Numbers are [pull requests](https://github.com/Automattic/wp-super-cache/pulls) on Github.)
### 1.5.3 ###
* Fix a critical bug that caused unlink to be run on null while deleting the plugin.
### 1.5.2 ###
* Add a trailing slash to home path. Fixes problems with finding the .htaccess file.
* Delete WPCACHEHOME and WP_CACHE from wp-config.php when plugin deactivated.
* Check that WPCACHEHOME is the right path on each load of the settings page.
* Load the REST API code without using WPCACHEHOME.
* Fixed mobile browser caching when using WP-Cache caching.
* Fixed directory checks on Windows machines.
* Reverted CDN changes in 1.5.0 as they caused problems in older "WordPress in a separate directory" installs.
* Added note to CDN page when site url != home url. Site owners can use a filter to adjust the URL used.
* Stop preload quicker when requested while preloading taxonomies.
* Added more information for when updating the .htaccess file fails.
* "Served by" header is now optional. Enable it by setting $wpsc_served_header to true in the config file.
### 1.5.1 ###
* Don't use anonymous functions in REST API
* Check that REST API Controller is available before loading the REST API.
* Don't use multibyte string functions because some sites don't have it enabled.
### 1.5.0 ###
* REST API settings endpoints.
* Simplified settings page.
* WP-Cache files reorganised.
* Caching of more http headers.
* Lots of bug fixes.
### 1.4.9 ###
* Fixed bug when not running sem_remove after sem_release. See https://github.com/Automattic/wp-super-cache/issues/85
* Fixed a PHP error impacting PHP 7.1.
* Fixed a bug where we cached PUT and DELETE requests. We're treating them like POST requests now.
* Delete supercache cache files, even when supercache is disabled, because mod_rewrite rules might still be active.
* Updated the settings page, moving things around. [#173](https://github.com/Automattic/wp-super-cache/pull/173)
* Make file locking less attractive on the settings page and fixed the WPSC_DISABLE_LOCKING constant so it really disables file locking even if the user has enabled it already.
* Added a WPSC_REMOVE_SEMAPHORE constant that must be defined if sem_remove() is to be used as it may cause problems. [#174](https://github.com/Automattic/wp-super-cache/pull/174)
* Added a "wpsc_delete_related_pages_on_edit" filter that on returning 0 will disable deletion of pages outside of page being edited. [#175](https://github.com/Automattic/wp-super-cache/pull/175)
* Fixed plugin deleting all cached pages when a site had a static homepage. [#175](https://github.com/Automattic/wp-super-cache/pull/175)
* Make sure $cache_path has a trailing slash [#177](https://github.com/Automattic/wp-super-cache/pull/77)
* Remove flush() [#127](https://github.com/Automattic/wp-super-cache/pull/127) but also check if headers are empty and flush and get headers again. [#179](https://github.com/Automattic/wp-super-cache/pull/179)
* Add fix for customizer [#161](https://github.com/Automattic/wp-super-cache/pull/161) and don't cache PUT AND DELETE requests [#178](https://github.com/Automattic/wp-super-cache/pull/178)
* Check for superglobals before using them. [#131](https://github.com/Automattic/wp-super-cache/pull/131)
### 1.4.8 ###
* Removed malware URL in a code comment. (harmless to operation of plugin but gets flagged by A/V software)
* Updated translation file.
### 1.4.7 ###
* Update the settings page for WordPress 4.4. layout changes.
### 1.4.6 ###
* Generate the file cache/.htaccess even when one exists so gzip rules are created and gzipped pages are served correctly. Props Tigertech. https://wordpress.org/support/topic/all-website-pages-downloading-gz-file-after-latest-update?replies=36#post-7494087
### 1.4.5 ###
* Enhancement: Only preload public post types. Props webaware.
* Added an uninstall function that deletes the config file. Deactivate function doesn't delete it any more.
* Possible to deactivate the plugin without visiting the settings page now.
* Fixed the cache rebuild system. Rebuild files now survive longer than the request that generate them.
* Minor optimisations: prune_super_cache() exits immediately if the file doesn't exist. The output of wp_cache_get_cookies_values() is now cached.
* Added PHP pid to the debug log to aid debugging.
* Various small bug fixes.
* Fixed reset of expiry time and GC settings when updating advanced settings.
* Removed CacheMeta class to avoid APC errors. It's not used any more.
* Fixed reset of advanced settings when using "easy" settings page.
* Fixed XSS in settings page.
* Hide cache files when servers display directory indexes.
* Prevent PHP object injection through use of serialize().
### 1.4.4 ###
* Fixed fatal error in output handler if GET parameters present in query. Props webaware.
* Fixed debug log. It wasn't logging the right message.
### 1.4.3 ###
* Security release fixing an XSS bug in the settings page. Props Marc Montpas from Sucuri.
* Added wp_debug_log(). Props Jen Heilemann.
* Minor fixes.
### 1.4.2 ###
* Fixed "acceptable file list".
* Fixed "Don't cache GET requests" feature.
* Maybe fixed "304 not modified" problem for some users.
* Fixed some PHP warnings.
### 1.4.1 ###
* Fixed XSS in settings page. Props Simon Waters, Surevine Limited.
* Fix to object cache so entries may now be deleted when posts updated. (object cache still experimental)
* Documentation updates and cleanup of settings page.
### 1.4 ###
* Replace legacy mfunc/mnclude/dynamic-cached-content functionality with a "wpsc_cachedata" cacheaction filter.
* Added dynamic-cache-test.php plugin example wpsc_cachedata filter plugin.
* Delete post, tag and category cache when a post changes from draft to publish or vice versa. Props @Biranit.
* Update advanced-cache.php and wp-config.php if wp-cache-phase1.php doesn't load, usually happening after migrating to a new hosting service.
* Misc bugfixes.
### 1.3.2 ###
* Any mfunc/mclude/dynamic-cached-content tags in comments are now removed.
* Dynamic cached content feature disabled by default and must be enabled on the Advanced Settings page.
* Support for the mobile theme in Jetpack via helper plugin on script's Plugins tab.
### 1.3.1 ###
* Minor updates to documentation
* Fixed XSS in settings page.
### 1.3 ###
* mfunc tags could be executed in comments. Fixed.
* More support for sites that use the LOGGED_IN_COOKIE constant and custom cookies.
### 1.2 ###
* Garbage collection of old cache files is significantly improved. I added a scheduled job that keeps an eye on things and restarts the job if necessary. Also, if you enable caching from the Easy page garbage collection will be enabled too.
* Editors can delete single cached files from the Toolbar now.
* Fixed the cached page counter on the settings page.
* Some sites that updated to 1.0 experienced too much garbage collection. There are still stragglers out there who haven't upgraded but that's fixed now!
* Supercached mobile files are now used as there was a tiny little typo that needed fixing.
* If your site is in a directory and you saw problems updating a page then that should be fixed now.
* The deactivate hook has been changed so your configuration isn.t hosed when you upgrade. Unfortunately this will only happen after you do this upgrade.
* Some sites use custom cookies with the LOGGED_IN_COOKIE constant. Added support for that.
* Added support for WPTouch Pro, but it appears to be flaky still. Anyone have time to work on that? I don.t.
* Some sites had problems with scheduled posts. For some reason the plugin thought the post was in draft mode and then because it only checked the same post once, when the post magically became published the cache wasn.t cleared. That.s fixed, thanks to the debug logging of several patient users.
* And more bug fixes and translation updates.
### 1.1 ###
* Use $_SERVER[ 'SERVER_NAME' ] to create cache directories.
* Only create blogs cached directories if valid requests and blogs exist.
* Only clear current blog's cache files if navigation menu is modified
* Added clean_post_cache action to clear cache on post actions
* Removed garbage collection details on Contents tab
* Added wp_cache_check_mobile cacheaction filter to shortcircuit mobile device check.
* Don't delete cache files for draft posts
* Added action on wp_trash_post to clear the cache when trashed posts are deleted
* Show a warning when 304 browser caching is disabled (because mod_rewrite caching is on)
* New check for safe mode if using less that PHP 5.3.0
* Added wp_supercache_remove_cookies filter to disable anonymous browsing mode.
* Fixed garbage collection schedule dropdown
* Fixed preload problem clearing site's cache on "page on front" sites.
* Fix for PHP variable not defined warnings
* Fixed problem refreshing cache when comments made as siteurl() sometimes didn't work
* Preloading of taxonomies is now optional
* Domain mapping fixes.
* Better support for https sites. Remove https:// to get cache paths.
* Added AddDefaultCharset .htaccess rule back in and added an option to remove it if required.
* Added multisite plugin that adds a "Cached" column to Network->Sites to disable caching on a per site basis.
* Added WPTouch plugin to modify browser and prefix list in mobile detection code. Added support for that plugin's exclude list.
* Fixed cache tester
* Filter the tags that are used to detect end-of-page using the wp_cache_eof_tags filter.
* Removed debug level from logging as it wasn't helpful.
* Removed mention of wp-minify.
### 1.0 ###
* Removed AddDefaultCharset .htaccess rule
* Fixed problem with blogs in a folder and don't have a trailing slash
* New scheduling of garbage collection
* Added a "Delete cache" link to Toolbar to delete cache of current page.
* Updated documentation
* Sorry Digg, Stephen Fry power now!
* Updated translations
* Preload taxonomies and all post types except revisionsand nav menu items
* Fixed previews by logged in users.
* Added option to make logged in users anonymous
* Use WP 3.0 variables to detect multisite installs
* Hash filenames so files are served from the same CDNs
### 0.9.9.9 ###
* Fixed typo, is_front_page.
* Serve repeated static files from the same CDN hostname.
* Updated translations.
* Make supercache dir lowercase to avoid problems with unicode URLs.
* Add option to skip https loaded static content.
* Remove 5 second check on age of existing cache files. Should help with posts that get lots of comments and traffic.
* Lots of bugs fixed.
### 0.9.9.8 ###
* CDN updates: can be switched off, multiple CNAMEs.
* Uninstall process improved. It removes generated files and fixes edited files.
* Cached dynamic pages can now be stored in Supercache files and compressed.
* 1and1 Webhosting fix (/kunden/)
* Remove log by email functionality as it caused problems for users who were inundated by email
* Many more minor fixes and changes.
### 0.9.9.6 ###
* Fixed problem serving cached files with PHP
* Added support for 304 "file not modified" header to help browser caching. (PHP caching only)
* Added French & German translations, updated Italian translation and fixed translation strings.
* Sleep 4 seconds between preload urls to reduce load on the server
* Updated docs and FAQs.
### 0.9.9.5 ###
* Disable compression on on easy setup page. Still causes problems on some hosts.
* Remove footerlink on easy setup page.
* Don't delete mod_rewrite rules when caching is disabled.
* Don't stop users using settings page when in safe mode.
### 0.9.9.4 ###
* Settings page split into tabbed pages.
* Added new "Easy" settings page for new users.
* New PHP caching mode to serve supercached files.
* Mobile support fixes.
* Added Domain mapping support plugin.
* Added "awaiting moderation" plugin that removes that text from posts.
* Terminology change. Changed "half on" to "legacy caching".
* Fixed cache tester on some installs of WordPress.
* Updated documentation
* Added $wp_super_cache_lock_down config variable to hide lockdown and directly cached pages admin items.
* Preloaded checks if it has stalled and reschedules the job to continue.
* Serve the gzipped page when first cached if the client supports compression.
* Lots more bug fixes..
### 0.9.9.3 ###
* Fixed division by zero error in half on mode.
* Always show "delete cache" button.
* Fixed "Update mod_rewrite rules" button.
* Minor text changes to admin page.
### 0.9.9.2 ###
* Forgot to change version number in wp-cache.php
### 0.9.9.1 ###
* Added preloading of static cache.
* Better mobile plugin support
* .htaccess rules can be updated now. Added wpsc_update_htaccess().
* Fixed "page on front" cache clearing bug.
* Check for wordpress_logged_in cookie so test cookie isn't detected.
* Added clear_post_supercache() to clear supercache for a single post.
* Put quotes around rewrite rules in case paths have spaces.
### 0.9.9 ###
* Added experimental object cache support.
* Added Chinese(Traditional) translation by Pseric.
* Added FAQ on WP-Cache vs Supercache files.
* Use Supercache file if WP-Cache file not found. Useful if mod_rewrite rules are broken or not working.
* Get mobile browser list from WP Mobile Edition if found. Warn user if .htaccess out of date.
* Make sure writer lock is unlocked after writing cache files.
* Added link to developer docs in readme.
* Added Ukranian translation by Vitaly Mylo.
* Added Upgrade Notice section to readme.
* Warn if zlib compression in PHP is enabled.
* Added compression troubleshooting answer. Props Vladimir (http://blog.sjinks.pro/)
* Added Japanese translation by Tai (http://tekapo.com/)
* Updated Italian translation.
* Link to WP Mobile Edition from admin page for mobile support.
### 0.9.8 ###
* Added Spanish translation by Omi.
* Added Italian translation by Gianni Diurno.
* Addded advanced debug code to check front page for category problem. Enable by setting $wp_super_cache_advanced_debug to 1 in the config file.
* Fixed wordpress vs wordpress_logged_in cookie mismatch in cookie checking function.
* Correctly check if WP_CACHE is set or not. PHP is weird.
* Added wp_cache_clear_cache() to clear out cache directory.
* Only show logged in message when debugging enabled.
* Added troubleshooting point 20. PHP vs Apache user.
* Fixed problem deleting cache file.
* Don't delete cache files when moderated comments are deleted.
### 0.9.7 ###
* Fixed problem with blogs in folders.
* Added cache file listing and delete links to admin page.
* Added "Newest Cached Pages" listing in sidebox.
* Made admin page translatable.
* Added "How do I make certain parts of the page stay dynamic?" to FAQ.
* Advanced: added "late init" feature so that plugin activates on "init". Set $wp_super_cache_late_init to true in config file to use.
* Disable supercaching when GET parameters present instead of disabling all caching. Disable on POST (as normal) and preview.
* Fixed problem with cron job and mutex filename.
* Warn users they must enable mobile device support if rewrite rules detected. Better detection of when to warn that .htaccess rules must be updated (no need when rewrite rules not present)
* Advanced: Added "wpsupercache_404" filter. Return true to cache 404 error pages.
* Use the wordpress_test_cookie in the cache key.
* Show correct number of cache files when compression off.
* Fixed problem with PHP safe_mode detection.
* Various bugfixes and documentation updates. See Changelog.txt
### 0.9.6.1 ###
* Move "not logged in" message init below check for POST.
* Add is_admin() check so plugin definitely can't cache the backend.
* Add "do not cache" page type to admin page.
### 0.9.6 ###
* Add uninstall.php uninstall script.
* Updated cache/.htaccess rules (option to upgrade that)
* Added FAQ about category and static homepage problem.
* Add wp_cache_user_agent_is_rejected() back to wp-cache-phase2.php
* Show message for logged in users when caching disable for them.
* Check filemtime on correct supercache file
### 0.9.5 ###
* Show next and last GC times in minutes, not local time.
* Don't serve wp_cache cache files to rejected user agents. Supercache files are still served to them.
* If enabled, mobile support now serves php cached files to mobile clients and static cached files to everyone else.
* Added checks for "WPSC_DISABLE_COMPRESSION" and "WPSC_DISABLE_LOCKING" constants to disable compression and file locking. For hosting companies primarily.
* Added check for DONOTCACHEPAGE constant to avoid caching a page.
* Use PHP_DOCUMENT_ROOT when creating .htaccess if necessary.
### 0.9.4.3 ###
1. Added "Don't cache for logged in users" option.
2. Display file size stats on admin page.
3. Clear the cache when profile page is updated.
4. Don't cache post previews.
5. Added backslashes to rejected URI regex list.
6. Fixed problems with posts and comments not refreshing.
## Upgrade Notice ##
Security and new feature release. Security issue is very difficult to perform but you should upgrade.
home/bechata/mp/wp-content/plugins/wp-file-manager/readme.txt 0000666 00000036470 15177143214 0020252 0 ustar 00 === File Manager ===
Contributors: mndpsingh287
Tags: wp-file-manager, elfinder,file manager, ftp, wp-filemanager,file manager, wp-filemanager, Upload Files, WP File Manager, File Manage, Edit Files, Delete Files, FTP, filemanager, wpfilemanager, ftp, file transfer, update, create, delete, view, rename, editor, Cpanel, Control Panel, Admin, Shortcode, explorer, file explorer, filemanager
Requires at least: 4.0
Tested up to: 5.8
Requires PHP: 5.2.4
Stable tag: 7.1.2
License: GPLv2 or later
License URI: http://www.gnu.org/licenses/gpl-2.0.html
file manager provides you ability to edit, delete, upload, download, copy and paste files and folders.
== Description ==
#### File Manager allows you to edit, delete, upload, download, zip, copy and paste files and folders directly from the Wordpress backend. Don’t bother with FTP to manage and move your files from location to location. The most powerful, flexible, and easiest Wordpress file management solution ever built!
https://www.youtube.com/watch?v=CiLkRDVlL2o
= Key Features in File Manager free Version Plugin =
Key Features in the Free File Manager plugin include:
* **Operations**: Various operations with files and folders on a remote server (copy, move, upload, create folder/file, rename, edit, delete, etc.)
* **Move/Copy**: Admin can Move/Copy files with Drag & Drop. Also includes multi file selection.
* **Archives**: Admin can create, archive and extract files(zip, rar, tar, gzip).
* **File Size**: Admin/User can upload any size files.
* **File Type**: Control what files can be uploaded and what file can be downloaded.
* **Code Editor**: File Manager comes with a built in integrated development environment (IDE) - New Feature
* **Syntax Checker**: File Manager now can complete code reviews before saving files to ensure your site will not go down when updating code. Reviewing code for errors has never been so easy! - New Feature
* **Multiple Themes**: Multiple File Manager Themes Available – New Feature
* **Get Info**: All file details, properties, information is now available by simply right clicking a file and selecting Get Info - New Feature
* **Share Files by Email**: With File Manager you can easily and quickly share files by Email. Simply right click a file and press share, that’s it! - New Feature
* **Private Folder**: Available only for File Manager Pro Edition
* **Shortcode**: Available only for File Manager Pro Edition
* **Root Directory**: Quickly and easily edit your root path directory. With this feature you can access files inside and outside of Wordpress
* **PDF Support**: Preview PDF files easily
* **Built-in Trash**: Delete files by moving them to trash
* **File View**: Icon and list view both available for easy navigation
* **Preview Support**: Easily preview common file types including media (video, audio, mp3, thumbnails, etc)
* **Search**: Search functionality is built directly into File Manager making it simple to find your files.
* **Shortcut Support**: Common shortcuts are available in File Manager
* **Automatic File Resize**: automatically resize files once uploaded.
* **Responsive UI**: File Manager works on tablet and mobile devices
* **Browsing History**: File and folders browsing history
* **Trash function**: Move to Trash Folder Feature
* **PDF Preview**: PDF Preview feature available
* **FTP/SFTP Support**: Alternative to FTP or Cpanel
* **File Preview**: preview for common MIMEs and file types
* **Directory Size**: Calculate directory size
* **Icon View**: List and Icons view available for files and files
* **Keyboard shortcuts**: Keyboard shortcuts available e.g. copy,paste,drag & drop
* **Drag and drop**: File Drag & Drop file upload function available
* **Functions Toolbar**: Rich context menu and file manager functions toolbar
* **Thumbnails**: Thumbnails for all types of image files
* **Upload to Media Library**: We have now included the ability to enable images, pdf's, and zip files to be uploaded to you folders and as well be available via the native Wordpress Media Library
* **Backup/Restore**: Backup and restore themes files, plugins files,uploads folder and db data on server.
* **Multi Languages Added**
= Key Features in File Manager Pro Editions =
* **File Type:** Control what files can be uploaded and what file can be downloaded.**
* **Operations:** Various operations with files and folders on a remote server (copy, move, upload, create folder/file, rename, edit, delete etc.)
* **Shortcode:** Available with custom attributes for frontend.
* **Private Folder:** Admin can give access of same and different folder to different users roles and different users.
* **Move/Copy:** Admin can Move/Copy files with Drag & Drop.
* **Archives:** Admin can create/extract files(zip, rar, tar, gzip).
* **File Size:** Admin/User can control file upload size.
* **Fullscreen View:** Admin can control code editor fullscreen view.
* **Editor**: There are a lots of themes available for code editor. Admin can control code editor themes.
* **Hide Files/Folder:** Here admin is able to hide files and folders for user roles and for users.
* **File Type:** Control what files can be uploaded and what file can be downloaded.
* **User Role:** admin is able to control file operations and hide and lock Files and Folders for user roles .
* **Users:** admin is able to control file operations and hide and lock Files and Folders for particular user .
* **High performance:** High performance server backend and light client UI.
* **File system:** Local file system storage drivers.
* **Edit file:** User can edit text files and images.
* **Frontend Access:** User can access frontend using shortcode.
* **Admin Email Notifications.** Admin will get a Notification whenever a file is updated.
* **Admin Email Notifications.** Admin will get a Notification whenever a file is Downloaded.
* **Admin Email Notifications.** Admin will get a Notification whenever a file is Edited.
* **Google Drive Integration** drag drop, copy paste all other operations between file manager and google drive.
* **Dropbox Integration** drag drop, copy paste all other operations between file manager and dropbox.
> <strong>[Buy Pro Version](https://filemanagerpro.io/product/file-manager/?utm_source=Wordpress.org&utm_medium=Website&utm_campaign=File%20Manager%20Pro)</strong> with various features & support.
> <strong>[Contact us](https://filemanagerpro.io/contact/?utm_source=Wordpress.org&utm_medium=Website&utm_campaign=File%20Manager%20Pro)</strong> for Support Only Pro Version Users.
> <strong>[Documentation](https://filemanagerpro.io/documentation/?utm_source=Wordpress.org&utm_medium=Website&utm_campaign=File%20Manager%20Pro)</strong> Click Here.
> <strong>[Addons](https://filemanagerpro.io/addons/?utm_source=Wordpress.org&utm_medium=Website&utm_campaign=File%20Manager%20Pro)</strong> with various features & support.
**[Upgrade to Pro Version](https://filemanagerpro.io/product/file-manager/?utm_source=Wordpress.org&utm_medium=Website&utm_campaign=File%20Manager%20Pro)**
= Premium Addons =
<strong>[File Manager Google Drive](https://filemanagerpro.io/product/file-manager-google-drive/?utm_source=Wordpress.org&utm_medium=Website&utm_campaign=File%20Manager%20Pro)</strong> provides you ability to edit, delete, upload, download, copy and paste files and folders in Google Drive.
<strong>[File Manager OneDrive](https://filemanagerpro.io/product/file-manager-one-drive/?utm_source=Wordpress.org&utm_medium=Website&utm_campaign=File%20Manager%20Pro)</strong> provides you ability to edit, delete, upload, download, copy and paste files and folders in OneDrive from File Manager.
<strong>[File Manager Dropbox](https://filemanagerpro.io/product/file-manager-dropbox/?utm_source=Wordpress.org&utm_medium=Website&utm_campaign=File%20Manager%20Pro)</strong> provides you ability to edit, delete, upload, download, copy and paste files and folders in dropbox.
<strong>[File Manager Box](https://filemanagerpro.io/product/file-manager-box/?utm_source=Wordpress.org&utm_medium=Website&utm_campaign=File%20Manager%20Pro)</strong> provides you ability to edit, delete, upload, download, copy and paste files and folders in Box.
<strong>[File Manager AWS S3](https://filemanagerpro.io/product/file-manager-aws-s3/?utm_source=Wordpress.org&utm_medium=Website&utm_campaign=File%20Manager%20Pro)</strong> provides you ability to edit, delete, upload, download, copy and paste files and folders in AWS S3 bucket.
<strong>[File Manager Git](https://filemanagerpro.io/product/file-manager-git/?utm_source=Wordpress.org&utm_medium=Website&utm_campaign=File%20Manager%20Pro)</strong> Github integration for file manager.
<strong>[File Manager Slack](https://filemanagerpro.io/product/file-manager-slack/?utm_source=Wordpress.org&utm_medium=Website&utm_campaign=File%20Manager%20Pro)</strong> Slack incoming webhook integration to file manager.
<strong>[File Manager Google Cloud](https://filemanagerpro.io/product/file-manager-google-cloud/?utm_source=Wordpress.org&utm_medium=Website&utm_campaign=File%20Manager%20Pro)</strong> provides you ability to edit, delete, upload, download, copy and paste files and folders in Google Cloud bucket.
== Installation ==
1. Upload the `wp-file-manager` folder to the directory `/wp-content/plugins/`.
2. Activate the plugin using the 'Plugins' menu in WordPress.
== Frequently asked questions ==
= Can we make zip of any folder or file and download it ? =
Yes, You can archive any files and folders as zip then simple download it. Please view screenshots.
== Support ==
* If any problem occurs, please contact us at https://filemanagerpro.io/contact/
## How to use
1. First Activate Plugin.
2. Then Click on " WP File Manager " menu. Then do with files what you want to do.
== Screenshots ==
1. File Manager File View Screen.
2. Make a folder or file archive as zip.
3. Download archived zip file.
4. PRO: In File Manager Pro version user is able to give accessibility to user roles by just one click and Control File upload size.
5. PRO: In File manager pro version admin is able to control file operations for user roles and also hide any file and folder. Admin also lock any file to prevent from edit.
6. PRO: In File manager pro version admin is able to control file operations for particular user and also hide any file and folder. Admin also lock any file to prevent from edit.
7. PRO: Admin can control code editor fullscreen view & code editor themes.
8. PRO: Code editor fullscreen view with selected theme.
9. PRO: Private Folder Access
10. File Manager with Multiple Languages
11. File Manager with Multiple Themes - Light Theme
12. Dark Theme View
13. Grey Theme View
14. Window 10 Theme View
15. Edit Root Directory Path
== Changelog ==
= 7.1.2 (20th July, 2021) =
* Checked compatibility with wordpress 5.8
* Fixed minor bugs
* Checked compatibility with Query Monitor plugin
* Updated Translations
= 7.1.1 (30th March, 2021) =
* Checked compatibility with wordpress 5.7
= 7.1 (18th Feb, 2021) =
* Fixed Cross site scripting (XSS) issue
= 7.0 (8th Feb, 2021) =
* Confliction issue fixed with wordpress 5.6 version
* Fixed download backups links not works on some servers issue
* Fixed PHP warnings issue
* Add support to tiff extension images
= 6.9 (1st Sept, 2020) =
* Security issue fixed
= 6.8 (31st Aug, 2020) =
* Fixed design compatibility issues with wordpress 5.5 version
= 6.7 (20th Aug, 2020) =
* Fixed issue of deprecated function of jquery
* Updated messages text
= 6.6 (18th Aug, 2020) =
* Updated Translations
* Added media title to the uploaded file when Files Upload to Media Library is enabled
= 6.5 (18th Jun, 2020) =
* Security Fix
= 6.4 (25th May, 2020) =
* $ confliction fixes
= 6.3 (22nd May, 2020) =
* Files extract issues fixes
= 6.2 (15th May, 2020) =
* jQuery confliction fixes
= 6.1 (14th May, 2020) =
* Compatibility issues
= 6.0 (14th May, 2020) =
* Google doc preview feature added and Library Updates - Major Update
= 5.9 (13th APR, 2020) =
* Fixed Errors Deprecated Unparenthesized
= 5.8 (31st MARCH, 2020) =
* Tested with Wordpress 5.4 version.
= 5.7 (23rd JAN, 2020) =
* Media library js fixes
= 5.6 (14th JAN, 2020) =
* Media library option fixes
= 5.5 (2nd DEC, 2019) =
* Unparenthesized issue fixes.
= 5.4 (16th AUGUST, 2019) =
* Minor fixes and added logs demo screenshots.
= 5.3 (20th AUGUST, 2019) =
* Rate us bar repetition removed.
= 5.2 (12th JULY, 2019) =
* Security fixes addressed by wordpress.
= 5.1 (11th JULY, 2019) =
* Security fixes.
= 5.0 (10th JULY, 2019) =
* Search outline issue fixed, Restore feature bugs fixes
= 4.9 (8th JULY, 2019) =
* Media library multiple file extensions allowed, backup feature admin authorized issue fixes
= 4.8 (13th MAY, 2019) =
* Minor fixes
= 4.7 (13th MAY, 2019) =
* Files and Database backup - restore feature added
= 4.6 (18th APR, 2019) =
* Elfinder Library Updated, Security Fixes
= 4.5 (17th APR, 2019) =
* PHP 7 issues fixes
= 4.4 (22nd FEB, 2019) =
* Extract issue fixed
= 4.3 (21st FEB, 2019) =
* Syntax checker feature removed for now
= 4.2 (21st FEB, 2019) =
* elFinder Library Updated
= 4.1 (21st JAN, 2019) =
* Syntax Error Feature Added
= 4.0 (10th JAN, 2019) =
* Http API fixes
= 3.9 (10th JAN, 2019) =
* CURL issue fixes
= 3.8 (20th DEC, 2018) =
* php 7.2 warnings fixes
= 3.7 (3rd DEC, 2018) =
* Header issue fixed
= 3.6 (3rd DEC, 2018) =
* Security Fixes
= 3.5 (3rd DEC, 2018) =
* Zip extract issue fixes
= 3.4 (30th Nov, 2018) =
* Minor Fixes
= 3.3 (30th Nov, 2018) =
* Library updated
= 3.2 (20th Oct, 2018) =
* CompaNovle with php 7.3 and wordpress 5.0
= 3.1 (17th Sep, 2018) =
* Security fixes and design fixes
= 3.0 (5th Sep, 2018) =
* Security issues fixed
= 2.9 (27th Aug ,2018) =
* Russian Translations added. Credit: @ivan192
* Code editor lines number added.
* Minimized window buttons collapsing issue fixed
= 2.8 (15th Jun ,2018) =
* minor Performence fix
= 2.7 (2th Jun ,2018) =
major Performence fix
= 2.6 (18th May ,2018) =
* '/' error Fix,major fix
= 2.5 (16th May ,2018) =
* Upload File issue Fix
= 2.4 (16th Apr ,2018) =
* On extract Invaild Backend issue
= 2.3 (16th Apr ,2018) =
* Extract Issue Resolved
= 2.2 (9th Apr ,2018) =
* PHP 7 Compatibility Issues Resolved
= 2.1 (26th March ,2018) =
* major design fixes
= 2.0 (1st March ,2018) =
* Edit Root Directory Path Feature - Major Update
= 1.9 (8th Jan ,2018) =
* fix Console en js missing error
* Now WP File Manager has various themes. - Major Update
= 1.8 (20th Sep ,2017) =
* fix some Bug in 1.7 - Minor Update
* Now WP File Manager is in various languages. - Major Update
* WP File Manager Translations Available. Compatible with any wordpress language. - Major Update
= 1.7 (18th Aug ,2017) =
* fix some Bug in 1.6 - Minor Update
* System Properties Menu - Added(New)
= 1.6 (20th Apr ,2017) =
* fix some Bug in 1.5 - Minor Update
= 1.5 (01th Mar ,2017) =
* fix some Bug in 1.4 - Major Update
= 1.4 (09th Jan ,2017) =
* fix some Bug in 1.3 - Major Update
* fix File edit auto slash add problem
= 1.3 (23th Nov ,2016) =
* fix some Bug in 1.2 - Minor Update
* fix max upload size problem
= 1.2 (17th Sep ,2016) =
* fix some Bug in 1.1 - Minor Update
* Compatible upto wordpress 4.6.1
= 1.1 (26th Aug ,2016) =
* fix some Bug in 1.0 - Minor Update
* Compatible upto wordpress 4.6
== Upgrade Notice ==
= Upgrade your old version to 3.2
== Other Notes ==
= Minimum requirements for File Manager =
* WordPress 3.3+
* PHP 5.x
* MySQL 5.x
If any problem occurs, please contact us at https://filemanagerpro.io/contact/