Budget: 150 EUR Deadline: 2 days
Hello. I have been working with JavaScript for over 8+ years. I am ready to set up input validation. Feel free to contact me.
Ми використовуємо конструктор лендингів/сайтів Onepage (onepage.io). На сайті є форма збору лідів, де користувач вводить номер телефону.
Поточна проблема: форма дозволяє відправити заявку з очевидно некоректними телефонами (наприклад, 0000000000, 12, 123, або будь-якою випадковою послідовністю цифр), навіть якщо обрано код країни +49 (Німеччина). Це призводить до “сміттєвих” лідів і марної роботи менеджерів.
Саппорт Onepage пропонує SMS-верифікацію як окрему платну функцію (підписка + оплата за кожну SMS). Для нашого сценарію (перший контакт, ринок Німеччини) це надто агресивно, погіршує конверсію та створює зайве тертя.
Нам потрібне НЕ підтвердження існування номера через SMS, а коректна технічна перевірка формату номера прямо у формі (client-side validation).
Реалізувати перевірку (валідацію) номера телефону у формі Onepage так, щоб:
Неможливо було відправити форму з явно некоректним номером.
Користувач бачив зрозуміле повідомлення про помилку (DE/EN, бажано DE).
У разі помилки відправка форми блокується (submit prevent).
Рішення не повинно вимагати SMS-підтвердження.
Сервіс: Onepage (onepage.io)
Реалізація очікується через:
Custom Code / вставка власного JavaScript на сторінку (глобально або на конкретній сторінці), або
HTML embed / Custom Code-блок (якщо потрібно).
Доступу до backend Onepage немає. Потрібна клієнтська (front-end) валідація.
Перевірити, як Onepage рендерить форму (HTML структура, селектори полів, submit button, події).
Визначити стабільний спосіб “підхопитися” на подію submit:
form.addEventListener('submit', ...) або
перехоплення кліку на кнопці submit, або
інші події, які реально працюють у Onepage.
Потрібно реалізувати 2 рівні перевірки:
Рівень 1 — базова санітизація та довжина
Поле “Телефон” має приймати лише цифри, пробіли, +, (, ), -.
Перед перевіркою прибрати всі символи, крім цифр та + (для логіки).
Заборонити введення очевидного сміття:
дуже короткі номери (наприклад < 10 цифр),
номер з одних нулів (наприклад 0000000000, +49 0000000000),
повторювані патерни типу 1111111111, 2222222222 (опційно, але бажано).
Рівень 2 — перевірка формату телефонів для Німеччини
Цільова країна — Німеччина (+49).
Валідація має працювати в одному з форматів:
+49XXXXXXXXXX... (між 10 і 15 цифр загалом за E.164)
0XXXXXXXXXX... (локальний формат)
Важливо: німецькі номери можуть мати різну довжину (мобільні/стаціонарні), тому логіка має бути адекватною, не “перерізати” реальні номери.
Рекомендований підхід (переважний):
використати бібліотеку Google libphonenumber або легшу обгортку/порт, яка дозволяє:
визначати валідність номера для регіону DE,
форматувати номер у E.164,
обробляти +49 та локальні 0....
Альтернативний підхід (якщо бібліотеку неможливо підключити):
використати regex + правила довжини (але це менш надійно).
мінімум: довжина (10–15 цифр) + заборона all zeros + заборона “занадто коротко”.
Якщо номер невалідний:
блокувати submit,
показувати повідомлення біля поля або попап/inline alert.
Повідомлення (мінімум німецькою):
DE: „Bitte geben Sie eine gültige Telefonnummer ein.“
EN (опціонально): “Please enter a valid phone number.”
Підсвічування поля червоною рамкою (CSS клас або inline).
При виправленні номера — помилка зникає.
Маска вводу або “розумне поле” з країною:
Наприклад, через intl-tel-input (якщо реально інтегрується у Onepage без конфліктів).
Автоформатування:
приводити номер до E.164 перед відправкою (якщо можливо), або хоча б зберігати “чисті цифри”.
Має працювати в актуальних браузерах: Chrome, Safari, Firefox, Edge.
Має працювати на мобільних (iOS/Android).
Не ламати інші поля/форми/скрипти на сторінці.
Onepage може генерувати динамічні ID/класи. Потрібні стабільні селектори або логіка пошуку елемента:
по label тексту,
по placeholder,
по типу input[type="tel"],
або за структурою блоку.
Можлива наявність кількох форм на сторінці — потрібно чітко прив’язатись до потрібної.
Скрипт має коректно працювати навіть якщо форма завантажується асинхронно (може знадобитися MutationObserver або повторний пошук елементів).
Валідація повинна:
✅ Пропускати:
+49 151 23456789
0151 23456789
реалістичні DE номери (мобільні/стаціонарні), якщо вони валідні за libphonenumber.
❌ Блокувати:
0
12
12345
0000000000
+49 0000000000
+49 1111111111 (бажано)
довільний набір з 5–8 цифр.
Готовий JS-код для вставки в Onepage (з інструкцією “куди вставити”).
Якщо використовуються бібліотеки:
посилання на CDN або файл(и),
інструкція підключення (порядок, залежності).
Інструкція налаштування:
де саме у Onepage вставити код (global/page/section),
як перевірити, що працює.
Короткий документ з селекторами, які використовуються, і логікою пошуку форми/поля.
(Опціонально) Мікро-CSS для стилів помилки.
Робота вважається виконаною, якщо:
неможливо відправити форму з номером 0000000000 або 2–5 цифрами,
коректні німецькі номери проходять,
користувач бачить зрозумілу помилку,
рішення працює стабільно на desktop і mobile,
є інструкція по впровадженню в Onepage.
Лідів у місяць: до ~200.
SMS-верифікацію використовувати НЕ плануємо (через конверсію та чутливість ринку Німеччини).
Мета: мінімізувати сміттєві заявки без підвищення тертя.
Чи маєте досвід інтеграцій в Onepage або подібні конструктори?
Який підхід пропонуєте: libphonenumber чи regex?
Чи зможете зробити так, щоб номер нормалізувався до E.164?
Як забезпечите стабільність при зміні DOM/оновленні Onepage?
Budget: 150 EUR Deadline: 2 days
Hello. I have been working with JavaScript for over 8+ years. I am ready to set up input validation. Feel free to contact me.
Budget: 150 EUR Deadline: 2 days
Hello.
I am ready to take it on. Write to me, we will discuss.
1. I have experience with constructors.
2. We can try using regex.
3. Yes.
4. This question requires a more detailed answer.
Budget: 150 EUR Deadline: 1 day
Good day.
I have worked on similar tasks in Webflow, Tilda, and other builders where there is no access to the backend and everything is resolved through client-side logic. In your case, I would implement a solution using libphonenumber in conjunction with my own submit interception logic, rather than using a simple regex. For the German market, this will provide a much more accurate validation, especially with varying lengths of numbers.
I can implement normalization to E.164 before form submission and block the submit with a correct message in German. The field will be highlighted, and the error will disappear after correction. If needed, we can add a light mask or intl-tel-input without conflicts with Onepage scripts.
We will ensure stability by searching for elements by field type and form context, rather than by dynamic IDs. If necessary, we will use MutationObserver to ensure the script correctly "catches" the form even during asynchronous rendering.
Please let me know if there is one form on the page or several, and if there is a possibility to insert the code globally for the entire site? This will affect the binding method.
Budget: 145 EUR Deadline: 1 day
Hello! I am interested in your project for phone validation in forms on Onepage.
I have experience integrating custom JavaScript into website builders (intercepting submit, working with dynamic DOM, MutationObserver, cross-browser compatibility).
I propose a solution: Validation through libphonenumber (for Germany), blocking submission for incorrect numbers, notifications in German and highlighting the field, normalizing the number to E.164 format (+49…), filtering 0000000000;
The solution will work without SMS, reliably on desktop and mobile, without conflicts with other scripts.
I am ready to implement it quickly and provide instructions for integration.
Budget: 144 EUR Deadline: 3 days
Ready to perform.
Experience in Web Development over 12+.
Examples of work https://koder.pp.ua/portfolio/
Budget: 200 EUR Deadline: 2 days
Good day!
My name is Dmytro, from King Kong Web.
I have reviewed your technical specifications for Onepage. We can implement client-side validation of the phone number without SMS, so that the form is not submitted with "junk" numbers, and the user immediately sees an error.
We will achieve this by inserting custom JavaScript into Onepage: we will hook into the form's submit event, check the number at two levels (basic validation + rules for DE/+49), and in case of an error, we will block the submission and show a message in German. We will also add highlighting to the field, and when the number is corrected, the error will disappear.
Regarding the approach: it is optimal to use libphonenumber (via CDN) to correctly validate German numbers and, if necessary, normalize them to E.164 format before submission. If Onepage does not allow for stable integration of the library, we will implement a reliable fallback based on length/pattern rules (regex + logic against 0000/too short).
After completion, we will provide the ready code for insertion, a brief instruction on where exactly to add it in Onepage, which selectors we are using, and how to check the functionality on desktop/mobile.
We are ready to start immediately. If needed, please send a link to the page with the form or a screenshot/HTML structure to quickly determine the most stable way to connect.
Budget: 150 EUR Deadline: 5 days
Good day, Valery.
I choose libphonenumber instead of regex. This will ensure accurate verification of German numbers (+49), normalization to E.164, and blocking of fakes. I will integrate it through Custom Code, using MutationObserver for stability with the dynamic DOM.
Users will see clear error messages in German, and submission will be blocked until the data is corrected. You will receive the finished code and instructions that guarantee the cleanliness of the database without degrading conversion.
I am ready to provide the complete code and instructions for integration into Onepage.
Additionally, instead of basic validation, I suggest expanding the functionality to an intelligent input mask for the phone number (based on intl-tel-input). This will significantly improve UX by automatically formatting the number during input and highlighting the correct format for Germany. It is also possible to add automatic country detection by prefix, which will simplify input for users from other countries in the future.
Budget: 150 EUR Deadline: 1 day
✋ Hello! We are the IT company dZENcode.
We implement phone validation in Onepage without SMS: libphonenumber, +49 and local 0..., normalization in E.164, blocking submit and errors DE, based on the team's experience, best practices, and our own developments.
Can you provide a link to the Onepage with the form?
Is it acceptable to connect libphonenumber or intl-tel-input via CDN?
You can find detailed information about our services and rates on the website: Freelancehunt.
Take a look – we will discuss the details of the work further, write when you are ready.
The final cost is formed only after clarifying the volume and requirements.
___________________
Best regards,
Manager of dZENcode
Our strengths:
💎 10+ years providing IT services: Outsourcing, Outstaffing
🔥 90+ in-house specialists
🚀 Projects "from scratch" and for support
⚙️ SLA and post-production support
✅ Contract with the company, guaranteed result!
🔥 250+ public reviews since 2015.
Budget: 150 EUR Deadline: 5 days
Hi,
I can implement phone number validation for your Onepage forms. I have experience with JavaScript client side validation, working with form builders, and DOM manipulation for dynamic environments.
I will create a validation script that blocks submission of invalid German phone numbers like 0000000000, short numbers, and repeated patterns, validates both +49 and local 0 formats using Google libphonenumber library for accurate German number validation, shows error messages in German with red border highlighting, normalizes valid numbers to E.164 format before submission, and works reliably on desktop and mobile browsers.
Regarding Onepage.io experience, I haven't worked directly with Onepage.io but I have experience integrating custom JavaScript into platforms like Webflow and Wix where similar challenges exist with dynamic IDs and async form loading. The approach is similar using stable selectors, MutationObserver for async loading, and event delegation.
For the approach I recommend using libphonenumber via CDN lightweight version like google libphonenumber js. This is more reliable than regex for German numbers which have variable length. Regex can work as fallback but won't catch all edge cases.
For E.164 normalization, libphonenumber can normalize valid numbers to E.164 format before form submission which helps with CRM data consistency.
For DOM stability I'll use multiple fallback selectors like input type tel, placeholder text, and label text, and implement MutationObserver to reattach validation if the form reloads asynchronously. I'll also test for multiple forms on the page and target the correct one.
I will deliver ready to use JavaScript code with CDN library links, integration instructions, selector documentation, and optional CSS for error styling.
Timeline: 1 week
Cost: $400 to $500 USD
I am available to start working immediately.
Youssef
Budget: 150 EUR Deadline: 2 days
Hello, write to me in private messages.
Budget: 150 EUR Deadline: 3 days
Hello! I have carefully studied your project and am ready to start its implementation. Let's discuss the details for the best execution.
Budget: 150 EUR Deadline: 2 days
Good day. I have done similar tasks, but not on onepage. The function to insert your own code is available in paid versions - so I cannot check something. I cannot say whether it will work or not. But I do have experience overall, and I personally need to figure it out "on the spot." If it suits you, please reach out. I have done: Script for unifying mobile numbers - it is in my portfolio.
Budget: 150 EUR Deadline: 1 day
Hello, Valerii Shcherbakov.
I've checked your requirements more carefully.
I can fully build the section using library(libphonenumber or other) and a few custom functions.
In this case, I don't need to change DOM for this.
I will add new section(for error) only.
I hope to make contract with you.
Thank you.
Budget: 200 EUR Deadline: 3 days
Hello. I am interested in implementing phone number validation for forms on Onepage. This is an important task, as proper validation will improve lead quality and reduce the workload on managers. My approach: to use the libphonenumber library for accuracy, as it works well with German numbers. Additionally, I will implement primary and secondary validation so that users receive clear error messages. Regarding integrations in Onepage, I have experience working with similar builders. For stability during DOM changes, I will use approaches that do not rely on dynamic selectors. I estimate the project at 200 EUR, with a timeline of about 2-3 days considering a buffer. What questions do you have?
Budget: 150 EUR Deadline: 1 day
Good evening. Your task is completely clear to me. I know how to solve your problem, I will write all the necessary functionality with the required validation. The numbers will be correct, everything as you want...
I will do additional checks, you will be very satisfied with the result!!!
I am waiting for you in personal messages.
Budget: 150 EUR Deadline: 1 day
Ready to execute right now, I will deliver the code in an hour. Experience of more than 4 years.
Responses:
1) Yes. The approach I use is universal for any no-code builders.
2) Definitely libphonenumber-js as the main approach.
3) Yes, it is possible.
4) Cascade selectors: the script searches for the field not by a single ID or class, but by a chain of 7 selectors (type tel, attributes name, placeholder). Even if Onepage changes one — another will work.
P.S. Write to me in private messages, I already have a ready solution.
Budget: 150 EUR Deadline: 1 day
Good evening, I will complete the task in 1 hour, if you are interested, write to me, I will be happy to collaborate.
upd: I already have the ready code, just need to integrate it into your form, a link is needed.
Good day, 1) update jQuery** to the latest version (3.x) with jQuery Migrate included 2) Thoroughly test the functionality of the application 3) and fix any possible errors so that all scripts are compatible with each other by versions here it is necessary to completely rewrite https://filtry.in.ua/assets/libs/libs.js for the new version of jQuery since it has an old Bootstrap and many custom functions written
Description: It is necessary to create a JavaScript script for the Tampermonkey extension. The script will work in an internal CRM system.Logic of operation: The script must read the unique text ID of the current active dialogue on the page (there are a total of 5–10 different IDs). Depending on the ID, the script takes the corresponding text instruction (System Prompt) from the settings. The mapping of parameters by ID should be moved to a separate convenient settings window for the script. When a new message appears in the chat window, the script sends this text along with the prompt via the OpenAI API (model gpt-4o-mini). The received response is inserted into the text input field and initiates sending with a random delay of 20–45 seconds to simulate the natural operation of the operator.Work is purely with text. Budget — 6000 UAH. I am waiting for proposals from developers with experience in working with the OpenAI API and writing browser automation scripts.
A web service needs to be developed for automating the operations of coffee shops and small food service establishments. The product should have functionality similar to Poster POS, but with its own design, architecture, and source code. Copying the code or interface of Poster is not anticipated. The plan is to create a full-fledged commercial SaaS product that various coffee shops can use in the future on a subscription basis.In the first stage, an MVP needs to be developed Main functionality: registration and authorization of the establishment owner; creation of one or several establishments; management of employees and roles; catalog of products, categories, and modifiers; adding sizes, flavors, and additional options; cash interface for processing sales; opening and closing cash shifts; various payment methods; returns and order cancellations; inventory accounting and write-offs; basic stock accounting; sales history; reports on revenue, products, shifts, and employees; loyalty program for customers; adaptive operation on tablets, laptops, and smartphones; administrative panel for the service owner; tariff plans and restrictions according to the tariff.Future plans include mobile application; integration with payment terminals; receipt printing; integration with fiscal services; delivery and online ordering; table reservations; advanced analytics; API for third-party integrations; integration with accounting and CRM systems.Important requirements the system must be designed to operate multiple independent establishments; data of each client must be isolated; scalability of the product must be anticipated; secure handling of financial and personal data is required; the code must be structured and suitable for further development; technical documentation is needed; rights to the source code are transferred to the client after payment. At this moment, the design is absent, so a separate assessment of UI/UX design is needed or a ready-made solution for the MVP should be proposed.Please include in your proposal experience in creating SaaS, POS, CRM, ERP, or accounting systems; examples of similar work; proposed technology stack; team composition; estimated cost of the MVP; development timeline; what exactly is included in the proposed cost; cost of further support; whether you are ready to work in stages with payment for each completed stage. Preference will be given to performers or teams that have already developed cash, inventory, restaurant, or multi-user SaaS systems.
Tech Stack - React: Responsive and dynamic front-end development - Node.js: Robust backend operations - Web3: Multi-chain cryptocurrency integration - Solidity: Smart contract development Project Objective Develop a comprehensive multi-chain staking platform for a popular gaming ecosystem, enabling seamless cryptocurrency interactions, NFT marketplace integration, and enhanced user experience across multiple EVM-compatible blockchain networks. Whitepaper We've been more than just a mobile gaming studio; we are visionaries and innovators in the gaming world. Our team is formed by mobile gaming industry talents and passionate gamers, and is dedicated to pushing the boundaries of what's possible in mobile gaming. Our expertise focuses on hybridizing genres to create something truly unique which we adapt for transitioning Web2 gaming to Web3 gaming titles. From Racing RPGs to Action Strategy games, we are constantly experimenting and blending genres to offer new gaming experiences. Our games aren't just a form of entertainment; they're immersive journeys that engage, challenge, and captivate our players. We embody our mission to not merely entertain but to transport our audience into an extraordinary universe of interactive world within Web3 gaming. - Front-End Development - Back-End Development - Landing Page Redesign - Multi-Chain Integration - NFT Marketplace - Testing & Quality Assurance - Deployment & Maintenance
The website is already launched and operational. The main task is to understand the current project structure, check the quality of implementation, fix identified technical issues, and assist with further changes.Main Stack Next.js 15 React 19 TypeScript Tailwind CSS Zod Redux Toolkit The project may also use: Prisma JWT authorization Stripe Mailgun Google APIs Vercel or Netlify FunctionsMain Tasks conduct an audit of the existing project; evaluate the structure and quality of the code; fix bugs and enhance current functionality; improve server-side rendering and page load speed; check the correctness of the website display on mobile devices; work with forms, the administrative part, and external integrations; make technical SEO changes; maintain and gradually improve the existing website.What is Important to Us good experience with Next.js, React, and TypeScript; ability to understand someone else's code; understanding of SSR and the features of Next.js App Router; attention to performance and quality of implementation; ability to explain identified problems and propose clear solutions; independence and careful work with the existing website. At the first stage, it is necessary to familiarize yourself with the project, conduct a technical audit, and propose a list of priority changes. After that, ongoing work on the further development of the website is possible.