Daniël Wimpel

Client system / WordPress product integration

Infocity Manager

Unify several live plugins without breaking their existing contracts.

01 / Purpose

A tool with a reason to exist.

A modular WordPress management plugin combining CV presentation, scheduled form popups, membership controls and payment-notification workflows while preserving settings and integrations from the standalone modules it replaces.

01

Provide one maintainable administrative surface for several related site capabilities.

02

Preserve existing WordPress options, hooks and external-plugin contracts during consolidation.

03

Avoid double-loading when a legacy standalone module is still active.

04

Keep payment and membership workflows conservative when evidence is incomplete.

02 / Decisions

The interesting part is why.

01

Compatibility before cleanup

A cleaner plugin architecture is not useful if it silently invalidates years of stored settings.

02

Conflict-aware loading

The migration period can contain old and new modules together, so duplicate hooks must be prevented deliberately.

03

Payment paths fail safe

Duplicate or unverified payment notifications create real customer and financial consequences.

04

Accessibility stays in scope

Responsive CV components and modal interactions are part of product correctness, not a polish pass.

03 / Architecture

A deliberate path through the system.

01

Detect

Inspect the WordPress environment and identify legacy module conflicts before registering replacement behaviour.

02

Compose

Load CV, popup, membership and payment modules behind one versioned plugin boundary.

03

Preserve

Reuse established option keys, hooks and integration contracts so consolidation does not discard live configuration.

04

Gate

Suppress duplicate notifications and leave unsafe payment fallbacks disabled unless their evidence is complete.

04 / Technology

The working parts.

PHPWordPressJavaScriptCSSFluent FormsUltimate Membership ProProfileGridPayPal workflows

05 / State & roadmap

What is real now—and what comes next.

Current
  • Version 1.2.0 is a verified package candidate.
  • The isolated development site still runs the earlier accepted 1.1.4 generation.
  • Module consolidation and compatibility safeguards are implemented.
  • Payment, mail and PayPal runtime acceptance remain.
Planned
  • Complete runtime acceptance of payment and email paths.
  • Promote the verified package only after external-plugin compatibility checks.
  • Continue consolidating administration without changing stored contracts.