Dolibarr JPEG Tagging Module

@rajat07me

Hello, this is a good fit because your brief is specific and follows the right Dolibarr approach already: hooks, no core edits, and standard file storage logic. I can build the module so JPEGs upload directly from the Project card, with fixed stage tags and an admin setting to allow or block user-created tags later. I will also keep the tag visible in both the document listing and file detail area, then provide an installable package with a short README for deployment. If you want, I can also share a brief outline of how I would structure the hooks and settings page.

@ranjika08

Hi, I can build this Dolibarr module using clean PHP and hooks, integrating JPEG uploads directly into Project cards while preserving Dolibarr’s standard file storage and update compatibility. I’ll add fixed stage tagging, display tags in document lists/details, and make custom tags a configurable module setting for future flexibility. I’ll provide a ready-to-install package, commented code, README, and can share a relevant code sample or demo. lets discuss in chat as I have some queries to ask regarding the project to proceed further.

@Iwori

Dolibarr module, hook-based, installed under /custom — no core file touched, survives upgrades. How I build it: - Tag stored in my own table linked to llx_ecm_files by rowid. Files stay where Dolibarr puts them, so directory logic and backups are untouched. - Tag list lives in a dictionary table, not hardcoded. Seed tags (Planning, Execution, Handover...) flagged as system. - Custom tags = one setup switch. ALLOW_CUSTOM_TAGS=0 -> select shows system tags only, creation form hidden. =1 -> users add their own, same table, is_custom flag. No code change, no data migration either way. - Select injected into the Project card attachment form via formObjectOptions/printFieldListValue hooks. Extra "Stage" column in the document list plus edit from the file detail popup. Sample of the injection pattern I use: function formObjectOptions($params, &$object, &$action, $hookmanager) { if (!in_array($object->element, array('project'))) return 0; $this->resprints = $this->renderStageSelect($object); return 0; } Deliverables: zip package with auto SQL install/uninstall, permissions (view / assign / manage dictionary), en_US + es_ES, README your admin can follow alone. One thing I need: your exact Dolibarr version. Hook availability differs between 16 and 21.

@Hrolgar

A hardcoded list of stage tags is quicker to build, but the moment you want to add or rename a stage you're back in the module editing PHP. A user managed table means one more model and a small settings screen, but the tags stop being code and become data you control from the admin panel. I'd build it as a toggle in the module's own settings tab, defaulting to the fixed list, so you can switch to the table later without touching the schema or losing tags already applied to files. Everything hangs off Dolibarr's hook system, mainly the document upload and formObject hooks on the Project card, so the tag gets stored through the standard ECM document mechanism as an extrafield rather than a new table bolted onto core. That's what keeps it alive across version updates: nothing in core gets touched, so an upgrade can't silently break the tagging. M1: hook scaffolding, JPEG upload to Project card, fixed tag list with tagging UI and storage via ECM extrafield. INR 12800, 2 days. M2: settings toggle for fixed list vs user managed table, table CRUD screen, install package and admin README. INR 19200, 3 days. Do you want the stage tag to show as a column in the existing document list on the Project card, or as its own filtered view underneath it?

@jayantkumar314

Hi, I can build this as a clean Dolibarr add-on using the module/hook system so the feature remains upgrade-safe and does not require core modifications. The module will extend the Project card workflow so users can upload JPEG files directly from the project, choose a predefined stage tag such as Planning, Execution or Handover, and see that tag in the document list and file details. I would keep the tag configuration flexible through module settings, allowing custom user-created tags to be enabled or disabled without changing the code. The implementation will follow Dolibarr’s standard document directory/storage logic so existing backup and restore workflows continue to work. Deliverables will include: * Installable Dolibarr module package * Project-card upload integration * Fixed project-stage tagging * Configurable custom-tag option * Tag display in document list/details * Clean PHP/MySQL implementation with no core hacks * README with install/configuration steps I can start by reviewing the target Dolibarr version and current Project/document setup.

@Prutheus

Small, well-defined module — and your open question about user-created tags is the one design decision worth settling now, because it is cheap to build for and expensive to retrofit. My recommendation: build the tag list as a dictionary table from the start, seeded with your fixed stages (Planning, Execution, Handover). Users cannot add tags until you switch a setting on. You get the consistency you want today, and enabling free tags later becomes a configuration change rather than a migration of existing data. That costs almost nothing extra now. The module itself: - Standard Dolibarr module structure, so it survives core updates rather than being a patched core file. - JPEG upload attached to the project report, with the tag selected at upload from the list. - Tag stored as a relation, not a filename convention — filenames get renamed and the metadata is then lost. - Filtering and listing images by stage, since tagging without retrieval is only half useful. - Installable through the standard module interface, with the SQL for tables and permissions included. Background: PHP is a language I work in professionally, and I build ERP-adjacent systems — a wholesaler platform with eighteen services in production, including document and image handling. Questions: which Dolibarr version, and should the images appear on the project itself as well as the report? Also, any file-size or format constraints beyond JPEG? Martin

@shayankhan333

Hello, I will build a small Dolibarr module that attaches JPEGs to a project report and tags each file with a stage from your fixed list, added straight into the Project card using the hook system so no core files are touched. Files will follow Dolibarr's standard directory logic, and the tag will show in the document list and file detail popup. For the custom-tag toggle, I will add a module setting that switches the tag source between the fixed list and a user-editable list. Questions: 1) Which Dolibarr version are you running? Looking forward to discussing further. Regards, Shayan.

@NEHABHAT92

With over 9 years of experience in web and mobile development, my team and I at "Turn Ideas to Realty" have a proven track record of delivering top-notch IT solutions. We have expertise in various technologies including MySQL, PHP, Software Development , Web Development and can seamlessly translate your needs into clean, commented PHP code with Dolibarr's hook system that is flexible enough to incorporate any future changes. Our solutions guarantee survival across version updates, as we strictly adhere to core hack-free principles. Our expertise extends to E-commerce and CMS-based websites, which I believe will be highly beneficial for your project. We are adept at developing functionality-focused plugins that integrate seamlessly into existing systems, as per the user’s need without compromising Dolibarr's standard directory logic; thus ensuring no glitches during backups. Additionally, we follow a robust Quality Assurance process and provide free support for 3 months post-delivery. We also offer cost-effective domain and hosting solutions. I assure you that choosing our team will not only meet but exceed your expectations on the JPEG Tagging module for Dolibarr.

@aprkdream

Hi, Thank you for considering me for your Dolibarr JPEG Tagging Module project. I understand that you're looking for a seamless way to attach JPEG images directly to a project report in Dolibarr, with a tag chosen from a fixed list to maintain consistency across the ERP. I've reviewed your requirements and with 10+ years of experience building scalable SaaS, ERP, CRM, and eCommerce platforms with PHP, Laravel, CodeIgniter, Node.js, and MySQL, I'm confident in my ability to deliver a clean, commented, and flexible PHP code that meets your needs. I've worked with similar ERP systems before and understand the importance of maintaining backup logic and ensuring seamless integration. Specifically, I can design the module to be flexible enough to switch the feature of allowing users to create their own tags on or off through the module settings. This can be achieved by adding a toggle switch in the module settings page that enables or disables user-created tags. To clarify, if you'd like to proceed with this feature, we can discuss the implementation details. Before we begin, can you please provide some more information about the fixed list of tags you'd like to see? Are there any specific tags that need to be included, or will it be a dynamically generated list based on your project stages? Deliverables will include: • Seamless upload from the Project card • Stored files following Dolibarr’s standard directory logic for backup compatibility • Flexible module settings to enable or disable user-created tags I'm looking. Best Regards, Anil Prajapati

@thiagofoz87

Your requirement is very clear: extend the Project card workflow in Dolibarr without touching the core, while keeping document storage fully compatible with the platform’s native directory structure and backup behavior. I would implement this as an isolated module using Dolibarr’s hook system and extra metadata tables, so the JPEG tagging feature remains upgrade-safe across future Dolibarr versions. The upload flow can be injected directly into the Project card document area, allowing users to upload images and assign a stage tag in a single action. For the tagging model, I would structure it in a flexible way from the start: - fixed predefined tags stored in module configuration - optional admin setting to allow custom user-created tags later without changing the database structure - tag visibility in both the document list and file detail popup The implementation would include: - clean PHP module structure - commented and maintainable code - no core hacks - install/uninstall scripts - README with deployment and configuration steps - validation for JPEG uploads and consistent naming behavior I can also keep the UI lightweight and aligned with native Dolibarr screens so the feature feels integrated rather than external. Estimated delivery is 4 days including testing on a recent Dolibarr version and packaging the installable module.

@mikes126

Hi there, let's have short meeting if you wanna quickly discuss the Dolibarr module. I can build this as a clean Dolibarr module using hooks, without touching core files. JPEG upload will be available directly from the Project card, with a fixed stage tag like Planning, Execution, Handover, etc. The tag will show in the document list and file detail popup. I’ll keep the tag logic configurable from module settings, so custom tags can be enabled/disabled later without rewriting the module. Files will use Dolibarr’s standard storage paths, and I’ll provide a clean install package + short README. I’m comfortable with PHP, MySQL and Dolibarr module/hook architecture and can keep the code update-friendly. Budget: $180 Timeline: 4 days

@netswaptech2811

You need a small, upgrade-safe Dolibarr module that adds JPEG project-report uploads with consistent project-stage tagging directly inside the existing Project card—not a core modification. The module would include: JPEG upload directly from the Project card Fixed stage dropdown: Planning, Execution, Handover, etc. Stage/tag displayed in the document list and detail view Files stored through Dolibarr’s standard project/document directory structure Validation for file type, upload errors and permissions No Dolibarr core-file modifications Module settings option to enable/disable custom user-created tags Clean, commented PHP following Dolibarr conventions Installable module package with README and configuration instructions For flexibility, I’d keep the tag source behind a small configuration layer: fixed predefined stages by default, with a settings flag switching to an admin-managed tag list later without rewriting the upload/document logic. Estimated timeline: 2–3 days, including implementation, testing and packaging. Milestones: module structure/hooks → upload + tagging → UI/settings → testing → install package & documentation. If you provide your Dolibarr version and the exact Project card/document area where the upload should appear, I can align the hooks precisely and avoid any core changes.

@aakaashberi

Dolibarr add-ons live or die on the hook system, so that is where I start - zero core files touched, survives your next upgrade. - Module descriptor plus install package: your admin drops it in custom/ and enables it from Modules. - Upload straight from the Project card document tab, files written through Dolibarr's own file logic so backups keep working. - Tag shown in the document list and the file detail popup, stored in its own table keyed to the file entry. On your open question - user-created tags: make it a module setup toggle, not a fork in the code. The fixed list is seeded into a tags table on install; flip the setting on and the same table gets an admin add form. One code path, one setting, and you can decide later without a rewrite. Commented PHP and a README with install and upgrade steps. 2 days to a package you can test on a staging copy first. Tell me your Dolibarr version and I will match it exactly.

@Geetam00

As someone who specializes in end-to-end product development, including building scalable web applications and automations systems, I am well-equipped to take on the Dolibarr JPEG Tagging Module project. My expertise spans across the technology stack that you require for this task, including MySQL, PHP, and a sound understanding of software architecture. I understand the importance of an intuitive user interface and a seamless workflow within a system like Dolibarr. My experience with ERP systems makes me familiar with the strict directory logic that must be followed to ensure smooth backups. I'm confident that I can incorporate all your specific requirements into one neat package using Dolibarr's hook system rather than resorting to complex core hacks. Above all, my track record speaks for itself when it comes to clean, commented PHP code that remains compatible through version updates. This is vital for maintaining future-proof modules without hindering any other functionality. Additionally, not only can I provide you with a quick install package, but I also ensure accompanying documentation (such as short README) for painless deployment by administrators even without my assistance.

@JoseRCarvas

Doing this without touching core means a proper module with a hook class. I'd hook the Project card's upload so the JPEG picker and the stage-tag dropdown sit inline on the card, not in a separate menu, and store the tag in the file's extrafields (companion table keyed on the ecm file rowid) so it shows in both the document list and the file-detail popup. Files still land in Dolibarr's standard documents/ path, so your backups keep working untouched. On the fixed-vs-custom question: I'd put the stage list on the module setup page with one switch there. Off locks it to Planning/Execution/Handover; on reads from an editable dictionary table. Same code path, so turning it on later needs no redeploy. You get an installable zip (enable it in Modules), commented PHP built on the hook system so it survives version updates, and a short README your admin can deploy from alone. I work in PHP/MySQL daily and can send a short snippet of the hook + extrafield wiring up front so you can sanity-check the approach before funding anything. 5.0 stars on my last two projects here. Two things that shape the build: which Dolibarr version are you on, and should the tag be per-file or per-report? I'll confirm once you say.

@Kredbird

With a robust background in ERP systems, specifically Dolibarr, I understand the importance of seamless integration and clean, commented code that ensures compatibility with future updates. I have a number of experience-enhancing projects already under my belt, allowing me to confidently tell you that your desired JPEG tagging module is within my wheelhouse. Allowing flexibility is essential for any system, and I can certainly cater for your possible preference to let users create their own tags. My skills in PHP go hand in hand with Dolibarr, making room for this privision while providing easy module settings toggles. In addition to the technical aspects, you can rely on me to not just develop a working solution but also provide thorough accompanying documentation. A quick-install package and a short README file will be designed to enable your admin to deploy without facing any hurdles. Let us work together to leverage the power of AI and modern web techniques and redesign your business processes for maximum efficiency.

@krish0032

Integrating JPEG tagging directly on the Project card in Dolibarr ensures a smooth user experience. I'd utilize Dolibarr's hook system for easy updates, allowing user-customizable tags via module settings without core alterations. View my similar add-on for streamlined file management using Dolibarr’s logic. Let's discuss your module’s deployment.

@cyberpower65

As a seasoned developer who has been leveraging PHP for ERP-driven projects just like yours, I bring a wealth of experience and technical prowess to the table. More specifically, my expertise in developing custom web applications dovetails perfectly with your Dolibarr JPEG Tagging Module requirements. Reassuringly, clean code that withstands version changes is the bedrock of my work- a crucial aspect you mentioned. I employ Dolibarr's hook system to ensure no core hacks occur, minimizing headaches when it comes to future updates. Notably, I am well-versed in Dolibarr's directory structure- which is exactly what you need for seamless backups and storage that align with the system's logic.

@arnikj4

I propose to develop a lightweight, secure, and upgrade-safe Dolibarr module for uploading JPEG images directly from the Project card and assigning standardized project-stage tags such as Planning, Execution, Testing, Handover, and Maintenance. The solution will use Dolibarr’s hook system and standard document-storage architecture without modifying core files. It will include configurable custom-tag support, proper permissions, tag visibility in document lists and file details, clean commented PHP code, an installable module package, and a concise README for deployment and configuration.