Search the Community
Showing results for tags 'redirects'.
Found 5 results
-
Hi everyone, I’m releasing Cockpit, an open-source short-link control center for ProcessWire. Cockpit keeps campaign, social, email, print, and QR URLs stable while their destinations change. It requires no templates, fields, or frontend pages. KEY FEATURES Custom or automatically generated single-level and nested paths 301, 302, 307, and 308 redirects with practical status guidance A ProcessWire admin workspace with Dashboard, Links, Analytics, and Audit views One management page per link with editing, traffic, QR, and audit history Aggregate lifetime and daily click statistics with rich filters and period comparison A local Campaign URL Builder for GA-compatible UTM parameters JSON/CSV export and transactional dry-run import CLI commands for CRUD, statistics, route inspection, diagnostics, migration, and retention Granular permissions and a privacy-minimal administrative audit log ROUTE SAFETY Cockpit resolves routes late in ProcessWire’s not-found lifecycle, so existing pages, URL segments, PagePathHistory, security/API hooks, and established redirect modules keep precedence. Before an active link is saved, Cockpit checks known route owners, including ProcessWire pages and history, Ichiban, ProcessRedirects, and common hook namespaces. Destination validation is fail-closed by default. Private and reserved networks, localhost, URL credentials, unsafe schemes, ambiguous paths, and redirect cycles are rejected. PRIVACY BY DESIGN Cockpit stores lifetime counters and aggregate daily buckets. It does not store visitor IP addresses, cookies, User-Agent strings, referrers, or one row per request. Bots, previews, HEAD requests, and configured QA addresses can be excluded from counting. QR INTEGRATION Cockpit does not bundle a QR engine. When a compatible FieldtypeQRCode release is installed, Cockpit uses its documented public API to generate a verified QR for the stable short URL. DOCUMENTATION AND SOURCE The repository includes installation and operations documentation, API reference, known-good examples, AI-agent safety guidance, a threat model, privacy statement, production checklist, tests, and deterministic release tooling. https://github.com/mxmsmnv/Cockpit This is the first public release. Feedback on route integrations, admin workflow, analytics, accessibility, and real-world short-link use cases is very welcome. -
We're launching a new version of our website and I need to create redirects from old pages to their new counterparts at different URLs. An example rule that I've created is Redirect 301 /solar-energy-for-business /solar-energy/commercial-solar/ However when I visit the redirected URL it shows up in the address bar as: https://staging.renovaenergy.com/solar-energy/commercial-solar/?it=solar-energy-for-business We're creating these redirects for SEO purposes and they need to not have additional URL parameters being added. This line in the .htaccess file is adding the original URL as a parameter. RewriteRule ^(.*)$ index.php?it=$1 [L,QSA] Does ProcessWire use this parameter for a purpose? What is the best way to create these redirects without this parameter?
-
Hi. I'm wondering if there is a way to add code to the Redirects module to strip the "?fbclid=" parameter from incoming links. My users have noticed that the redirect links they have established via the module are failing when used from Facebook, due to the new FB click tracking code.
-
Hi! I am new to processwire and really like working with it so far. For a relaunch project, some editors of our website need the permission to add redirect URLs while migrating the content. I already created a role "site-manager" so only a few team members have access to certain features. There is also the option to add redirect URLs in the page settings, but it seems to be restricted only to superusers. Does anyone know of a way to grant permission for this option to another user role? Since this is the first PW-Project I did not dive in too deep with the permissions yet. I also tried to add a "page-edit-redirect"-permission, but I am somehow stuck on what to do with it. Thanks
-
Hi there, I want to 301 redirect the following: http://www.example.com/folder-name1/ to http://www.example.com/folder-name1/index.php/folder-name2/ Is that possible with htaccess? Which code should I use Thanks in advance for your answers
