by
mate08
0 (0 reviews)
ARDOIZA PRO : réservation de table pour restaurant
Simple table reservation for restaurants, with an online menu, its allergens and a QR code of the menu page. No account, no external service.
ARDOIZA PRO ranks #49,892 among WordPress.org plugins with 0+ active installations, is #576 of 717 in the Business category, and was last updated Oct 6, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1.4
v1.0.7
Current Version v1.0.7
Updated 3 weeks ago
Last Update on 06 Oct, 2026
Refreshed 2 days ago
Last Refreshed on
#576 of 717 in Business
Actively maintained
Rank
#49,892
—
No change
Active Installs
0+
—
No change
KW Avg Position
N/A
—
No change
Downloads
415
+1 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 10
0+
10+
22,324
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 5 more installs to reach 10+
Rank Changes
Current
#49,892
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.0.7
- Last Updated
- Oct 06, 2026
- Requires WP
- 6.5+
- Tested Up To
- 7.1.4
- PHP Version
- 8.1 or higher
- Author
- mate08
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
6K+ installs
#2,757
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#1,015
Widgets for Google Reviews
1M+ installs
#67
GiveWP - Donation Plugin and Fundraising Platform
100K+ installs
#371
Event Tickets and Registration
90K+ installs
#491
WP Job Manager
70K+ installs
#566
TermsFeed AutoTerms: Privacy Policy Generator, Cookie Consent, GDPR, CCPA, Terms & Conditions, Disclaimers, Cookies Policy, EULA
70K+ installs
#582
LearnPress – WordPress LMS Plugin for Create and Sell Online Courses
70K+ installs
#611
Online Scheduling and Appointment Booking System – Bookly
60K+ installs
#655
WP Recipe Maker
50K+ installs
#718
Frequently Asked Questions
Common questions about ARDOIZA PRO : réservation de table pour restaurant
No. Everything runs on your WordPress site. The plugin never contacts ARDOIZA servers.
The 14 substances or products causing allergies or intolerances listed in Annex II of Regulation (EU) No 1169/2011, which apply to non-prepacked food in the European Union. You remain responsible for the accuracy of the information shown to your guests.
Yes. The public styles use CSS custom properties (--ardoiza-accent, --ardoiza-ink, --ardoiza-cream, --ardoiza-sand, and so on), set on .ardoiza-menu and .ardoiza-form-wrap. Redefine them in your theme or in the Customizer's additional CSS with one more selector, because the plugin styles may be loaded after yours (in the footer of the page when you use a shortcode), for example body .ardoiza-menu, body .ardoiza-form-wrap { --ardoiza-accent: #1f4e8c; }. A value set on :root does not reach them. Corner rounding follows --ardoiza-radius and the button shadow follows --ardoiza-accent. Since 1.0.7 each plugin rule starts with .ardoiza-menu or .ardoiza-form-wrap, so that fewer theme rules reach into the menu and the form (a theme rule that is more specific can still change them). If your own CSS targets a plugin class, prefix it with body .ardoiza-menu or body .ardoiza-form-wrap, for example body .ardoiza-menu .ardoiza-dish__price: the plugin styles may be loaded after yours, so your rule needs one more selector to win. The frame of the reservation form is now drawn by .ardoiza-form-wrap instead of .ardoiza-form. Text written between <code> tags in a dish description is shown in the font of the menu, not in a monospace font.
For each day the opening hours are cut into slots of the chosen length; the last slot starts before closing time. A slot is offered when the sum of guests of pending and confirmed reservations plus the requested party fits within the capacity per slot. Past slots and dates beyond the booking horizon are excluded.
Yes. The form posts to the server, which validates the slot again. When JavaScript is available, the list of times is refined as soon as a date and a party size are chosen; a time already chosen stays selected if it is still free, otherwise a message next to the field asks for another one.
Several checks: a security token tied to the form, a hidden trap field, a minimum fill time measured from a timestamp signed by your site for the visitor's address, a limit of five attempts per hour and per address, a limit of three reservations per hour and ten per day for the same email address or phone number, and a limit of 40 reservations per hour for the whole site (filter ardoiza_site_requests_per_hour). Every attempt counts towards the limit per address, including the ones that fail; a request without a valid address is refused. The list of free times can be looked up 30 times per ten minutes from one address. Addresses, emails and phone numbers are only hashed, with the secret salt of your site, for these short-lived counters and are never stored with the reservation. This stops most bots without CAPTCHA or external service. If your pages are served from a cache, the token and the timestamp are refreshed by the plugin's own script when the visitor picks a date; the page holding the form also asks shared caches not to keep it. Should a visitor still send an out of date page, the form says so and asks them to reload.
By default the limits per address use the address seen by PHP (REMOTE_ADDR). Behind a reverse proxy this is the address of the proxy, so all your visitors share the same limits. The filter ardoiza_client_ip lets you give the real address of the visitor. For example, for a site that really is behind Cloudflare, in a small plugin of your own or in the functions.php file of your theme: add_filter( 'ardoiza_client_ip', function ( $ip ) { return isset( $_SERVER['HTTP_CF_CONNECTING_IP'] ) ? wp_unslash( $_SERVER['HTTP_CF_CONNECTING_IP'] ) : $ip; } ); Only trust such a header if your site is really behind that proxy and cannot be reached directly: otherwise anyone can send the header with an address of their choice and escape the limits. A value that is not a valid IP address is ignored and the plugin falls back to REMOTE_ADDR.
In a dedicated table of your WordPress database. The retention period (365 days by default, 0 to keep forever) deletes older reservations once a day. Guests can also ask you to export or erase their data through the WordPress privacy tools.
Only if you tick "Delete dishes, sections, reservations and settings when the plugin is uninstalled" in the settings. Otherwise your data is kept.
Not with this plugin. The paid ARDOIZA offers are described at https://ardoiza.fr/. They are separate products and are not needed to use this plugin.
