Feat/pro block settings

[iftakharul-islam]

Summary by CodeRabbit

• New Features

  • Added Contributors, Advanced Contributors, Table of Contents, Helpful Feedback and Contact Modal blocks plus new responsive editor controls and shared block styling helpers.

• Bug Fix / Refactor

  • Switched to manifest-driven block registration and modernized build configuration.

• Chores

  • Removed legacy compiled front-end bundles and some generated styles; adjusted dev dependency ordering.

• Documentation

  • Added README for block styling helpers.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Deletes many compiled build artifacts, adds numerous new source-based Gutenberg blocks, helpers, and UI controls/components, wraps DocsGrid render functions with redeclaration guards, and updates asset registration and webpack/package configuration.

Changes

Cohort / File(s)	Summary
Deleted build artifacts assets/build/*, e.g. assets/build/block.asset.php, assets/build/block.js, assets/build/frontend.css, assets/build/index.asset.php, assets/build/store.js, assets/build/style-block.css, assets/build/print.css, assets/build/blocks/DocsGrid/block.json, assets/build/editor.asset.php, assets/build/icons.asset.php	Removes generated JS/CSS bundles and PHP asset manifests emitted to assets/build. Verify enqueues, dependency manifests, and any runtime expectations of those files.
New block sources — Contributors & AdvanceContributors src/blocks/Contributors/*, src/blocks/AdvanceContributors/*	Adds block.json, editor UIs (edit.js, edit-old.js), index registrations, render.php, save.js, and styles; large attribute surfaces and responsive style generation.
New Table of Contents block src/blocks/TableOfContents/*	Adds manifest, editor (edit.js), Inspector/controls (Inspector.js, ColorsControls.js, ListItems.js), server render (render.php), frontend view (view.js), styles and save placeholder.
New Helpful Feedback & Helpful Modal blocks src/blocks/HelpfulFeedback/*, src/blocks/HelpfulModal/*	Adds manifests, editor components, registrations, server renderers, frontend view scripts, save stubs, and SCSS; includes voting/modal JS and server-side rendering.
New block helpers (JS & PHP) src/blocks/helpers/* (block-helpers.js, block-styles.php, index.js, README.md)	Introduces JS helpers for generating inline/responsive CSS and a PHP counterpart with sanitization and responsive CSS generators; re-exports provided.
New common control components src/blocks/commonControls/*	Adds device-aware controls (AlignmentControls, BackgroundImageControls, BorderAndShadowControls, ColorsControls, DimensionsControls, DisplayControls, TypographyControls) with per-device state and Reset actions.
New UI primitives / components src/blocks/components/*	Adds reusable controls: BackgroundControl, BorderControl, DimensionControl, ShadowControl, SpacingControl, TabSystem, TypographyControl, etc.
DocsGrid adjustments src/blocks/DocsGrid/render.php, assets/build/blocks/DocsGrid/render.php	Wraps get_pagination_style_tag and render_wedocs_docs_grid in function_exists guards; built DocsGrid manifest and build assets removed.
Build and packaging changes webpack.config.js, package.json	Updates webpack entries, asset module rules (images/fonts/SVG), output asset naming, and swaps two devDependencies in package.json.
Integration / asset registration updates includes/Assets.php, includes/Frontend.php, wedocs.php, src/blocks/index.js	Adds assetsUrl and isPro to localized script vars, comments out block-style registration, disables template loader filter, switches to block.json registration iteration, adds block category, and imports new blocks.
Editor minor change & docs src/editor/AiDocWriterPanel.js, readme.md, src/blocks/helpers/README.md	Minor import change (PluginSidebar source), README additions, and small formatting edits.

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~60 minutes

Possibly related PRs

• Enhance design and unlock permission management features for free users #224 — touches includes/Assets.php localization keys; overlaps with assetsUrl/isPro additions.
• Add docs grid #203 — modifies DocsGrid render/functions and assets; related to DocsGrid guards and asset removals.
• update ai icon and wording #266 — edits build artifacts under assets/build; overlaps with deleted compiled files here.

Suggested labels

Needs Review

Suggested reviewers

• arifulhoque7

Poem

🐇 I hopped through lines both new and old,
Cleared bundles, planted blocks bold.
Helpers, controls, and TOC in tow,
Contributors lined up in a row.
A rabbit cheers — code ready to grow!

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 25.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.
Title check	❓ Inconclusive	The title 'Feat/pro block settings' is vague and does not clearly summarize the main changes in the changeset, which involve significant refactoring including removal of compiled assets, addition of new blocks (Contributors, AdvanceContributors, TableOfContents, HelpfulFeedback, HelpfulModal), reorganization of build structure, and addition of helper utilities.	Consider a more descriptive title that captures the primary intent, such as 'Add new block implementations and refactor build structure' or 'Introduce pro block components with helper utilities'.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 79

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

webpack.config.js (1)

71-75: Avoid duplicate MiniCssExtractPlugin.

@wordpress/scripts already injects MiniCssExtractPlugin. A second instance can cause conflicts. Reuse the existing one unless you have a specific need.

Apply this diff:

-  plugins: [
-    ...defaultConfig.plugins,
-    new MiniCSSExtractPlugin( {
-      filename: '[name].css',
-      chunkFilename: '[id].css',
-    } ),
-  ],
+  plugins: [ ...defaultConfig.plugins ],

🧹 Nitpick comments (98)

assets/build/style-block-rtl.css (2)

1-1: Reconsider extensive use of !important flags.

The CSS contains numerous !important declarations (e.g., background-color:var(--field-color) !important), which typically indicates CSS architecture or specificity issues. Using !important broadly can make the codebase harder to maintain and override.

Review the specificity of selectors and consider restructuring to rely on proper selector hierarchy instead of !important. For example:

/* Instead of: */
.wp-block-wedocs-wedocs-search .wedocs-search-input .search-field {
  background-color: var(--field-color) !important;
}

/* Consider: */
.wp-block-wedocs-wedocs-search .wedocs-search-input .search-field {
  background-color: var(--field-color);
}

This requires ensuring the selector specificity is sufficient without needing !important.

---

1-1: Consider build artifact exclusion from version control.

Build artifacts are typically auto-generated and should not be committed to version control. If this file is generated during the build process, it should be excluded via .gitignore and regenerated as part of CI/CD.

Verify that assets/build/ is excluded from .gitignore and that the build pipeline regenerates these files. This keeps the repository clean and ensures artifacts stay in sync with source.

src/blocks/components/SpacingControl.js (3)

26-68: Consider extracting the duplicated BoxControl configuration.

The Padding and Margin sections share identical configuration (units, allowReset, resetValues). Extract this into a shared helper or constant to improve maintainability.

Example refactor:

+const SPACING_BOX_CONFIG = {
+	units: [
+		{ value: 'px', label: 'px' },
+		{ value: 'em', label: 'em' },
+		{ value: 'rem', label: 'rem' },
+		{ value: '%', label: '%' }
+	],
+	allowReset: true,
+	resetValues: {
+		top: '0px',
+		right: '0px',
+		bottom: '0px',
+		left: '0px'
+	}
+};
+
 const SpacingControl = ({
 	// ... props
 }) => {
 	return (
 		<PanelBody title={label} initialOpen={false}>
 			{showPadding && (
 				<>
 					<BoxControl
 						label={__('Padding', 'wedocs')}
 						values={paddingValue}
 						onChange={onPaddingChange}
-						units={[
-							{ value: 'px', label: 'px' },
-							{ value: 'em', label: 'em' },
-							{ value: 'rem', label: 'rem' },
-							{ value: '%', label: '%' }
-						]}
-						allowReset={true}
-						resetValues={{
-							top: '0px',
-							right: '0px',
-							bottom: '0px',
-							left: '0px'
-						}}
+						{...SPACING_BOX_CONFIG}
 					/>
 					<Spacer marginTop={4} marginBottom={4} />
 				</>
 			)}
 
 			{showMargin && (
 				<>
 					<BoxControl
 						label={__('Margin', 'wedocs')}
 						values={marginValue}
 						onChange={onMarginChange}
-						units={[
-							{ value: 'px', label: 'px' },
-							{ value: 'em', label: 'em' },
-							{ value: 'rem', label: 'rem' },
-							{ value: '%', label: '%' }
-						]}
-						allowReset={true}
-						resetValues={{
-							top: '0px',
-							right: '0px',
-							bottom: '0px',
-							left: '0px'
-						}}
+						{...SPACING_BOX_CONFIG}
 					/>
 					<Spacer marginTop={4} marginBottom={4} />
 				</>
 			)}
 		</PanelBody>
 	);
 };

---

77-77: Consider consistent default value handling.

The gapValue uses an inline fallback ('10px') while paddingValue and marginValue have default values in the props destructuring. For consistency, consider adding a default for gapValue in the props definition (line 18).

---

74-85: Note: API inconsistency with custom UnitControl.

This component uses WordPress's experimental UnitControl (value as a string like '10px'), while the codebase also has a custom UnitControl at src/blocks/CustomControls/UnitControl.js with a different API (separate value and unit props). Consider documenting when to use each or standardizing on one approach to avoid confusion.

src/blocks/commonControls/DisplayControls.js (1)

26-47: Consider extracting styles to a stylesheet.

While inline styles work, extracting them to a dedicated CSS file or using a CSS-in-JS solution would improve maintainability and allow for better reusability across components.

readme.md (1)

26-39: Remove misleading Mozart configuration comment from readme.md.

This commented JSON block references "WPMUDEV\PluginTest" and includes google/apiclient, but verification shows: the weDocs project has no Mozart configuration in composer.json, and google/apiclient is not used anywhere in the codebase. This appears to be accidentally copied from another project and should be deleted to avoid confusion.

src/blocks/TableOfContents/editor.scss (1)

18-24: Consider the UX implications of cursor: default on links.

The TOC list links have cursor: default but still show a hover color change. This creates an inconsistent user experience where the visual feedback (color change on hover) suggests interactivity, but the cursor doesn't change to indicate a clickable element.

If these links are not meant to be clickable in the editor (which seems to be the intent), consider either:

1. Removing the hover color change to match the non-interactive cursor, or
2. Using pointer-events: none to completely disable interaction and remove the need for hover styles.

Apply this diff to remove hover styles for consistency:

 	.toc-content {
 		.toc-list {
 			li a {
 				cursor: default;
-
-				&:hover {
-					color: #0073aa;
-				}
+				pointer-events: none;
 			}
 		}
 	}

assets/build/blocks/TableOfContents/style-index.css (2)

1-1: Typo in custom property name (sytle → style) and likely wrong binding.

color uses var(--list-item-sytle, inherit). Rename to a clear token (e.g., --toc-link-color) across LTR/RTL CSS and JS, and bind it to listColor (not container background).

---

1-1: Nit: prefer ::before/::after.

Use double-colon pseudo-elements for modern CSS.

src/blocks/commonControls/TypographyControls.js (2)

255-270: Use undefined on reset instead of null to truly clear values.

Block serialization treats undefined as “absent”; null may persist and complicate style builders. Prefer undefined.

Apply this diff:

-                                fontFamily: null,
-                                fontSize: null,
-                                fontAppearance: null,
-                                lineHeight: null,
-                                letterSpacing: null,
-                                textDecoration: null,
-                                textTransform: null,
+                                fontFamily: undefined,
+                                fontSize: undefined,
+                                fontAppearance: undefined,
+                                lineHeight: undefined,
+                                letterSpacing: undefined,
+                                textDecoration: undefined,
+                                textTransform: undefined,

---

49-66: Reduce repetition with a small helper.

setAttributes blocks repeat. Extract a setTypographyForDevice(key, value) helper to cut noise and mistakes.

Example:

+ const setTypographyForDevice = (key, value) => {
+   setAttributes({
+     typographyControls: {
+       ...typographyControls,
+       [device]: {
+         ...typographyControls[device],
+         [key]: value,
+       },
+     },
+   });
+ };
...
- onChange={(value) => { setAttributes({ ... }) }}
+ onChange={(value) => setTypographyForDevice('fontFamily', value)}

Also applies to: 90-107, 111-144, 149-165, 167-201, 204-242

webpack.config.js (4)

19-20: Use content hashing (or path) for emitted assets to avoid collisions and aid caching.

images/[name][ext] can overwrite when names repeat. Prefer contenthash or preserve subpaths.

Apply one:

- assetModuleFilename: 'images/[name][ext]',
+ assetModuleFilename: 'images/[name].[contenthash:8][ext]',

or:

- assetModuleFilename: 'images/[name][ext]',
+ assetModuleFilename: '[path][name][ext]',

---

24-31: Broaden filter to include webp/avif; otherwise rules conflict.

Default WP Scripts rules often match webp/avif; your filter leaves them, causing overlap.

Apply this diff:

- return !testString.match(/jpg|jpeg|png|gif|svg|bmp|ico/i);
+ return !testString.match(/jpg|jpeg|png|gif|svg|bmp|ico|webp|avif/i);

---

48-59: Brittle SVG routing by substring match.

Checking pathData.filename.includes('assets/fonts') can fail with alternate paths. Use include/exclude with resolved paths, or a dedicated fonts rule before SVG images.

Example:

- if (pathData.filename.includes('assets/fonts')) { return 'fonts/[name][ext]'; }
+ // In rules: put a fonts-first rule with `test: /\.svg$/i, include: path.resolve(__dirname, 'assets/fonts')`
+ // and a second svg rule for images with `exclude` pointing to the fonts dir.

---

78-94: Make devServer host configurable.

Hardcoding host 'wedocs.test' can block other devs. Read from env with a safe default.

Example:

- host: 'wedocs.test',
+ host: process.env.DEV_HOST || 'localhost',
+ port: parseInt(process.env.DEV_PORT || '8886', 10),

src/blocks/components/TypographyControl.js (3)

54-70: Use theme/gutenberg font families, not a hard‑coded list.

Pull families via useSettings('typography.fontFamilies') to respect theme.json and user fonts; fall back gracefully for classic themes.

Example snippet:

import { useSettings } from '@wordpress/block-editor';
const ff = useSettings( 'typography.fontFamilies' );
const themeFonts = ff?.[0]?.theme ?? [];
const customFonts = ff?.[0]?.custom ?? [];
const options = [{ label: __('Default','wedocs'), value: 'default' }, ...themeFonts, ...customFonts];

---

116-127: UnitControl defaults should be empty/undefined, not 'normal'.

UnitControl expects numeric+unit (or empty). Use placeholders and treat undefined as “inherit/normal” in style builders.

Apply this diff:

- value={value.lineHeight || 'normal'}
+ value={value.lineHeight}
...
- value={value.letterSpacing || 'normal'}
+ value={value.letterSpacing}

Then handle “normal” in CSS generation (fallback when undefined).

Also applies to: 130-140

---

32-33: Open by default only when needed.

Initial open Panels can be noisy. Consider initialOpen prop controlled by caller or keep it closed by default for consistency with other panels.

assets/build/blocks/TableOfContents/style-index-rtl.css (1)

1-1: Typo in custom property (sytle) and binding.

Rename var(--list-item-sytle) to --toc-link-color (or similar) and align with JS to source from listColor, not container background.

src/blocks/helpers/README.md (1)

1-120: Add minimum WP/Gutenberg versions and SSR registration snippet.

Include a short “Compatibility” section (min WP and Gutenberg) and a code snippet showing register_block_type with render_callback using these helpers for dynamic blocks. Helps adopters avoid guesswork.

assets/build/block.js (1)

1-1: Do not lint/review minified build artifacts; exclude assets/build from linters and code review.

Biome “noRedeclare / use-before-declare” errors are from minification. Add assets/build to .eslintignore/.biomeignore and CI excludes. Prefer reviewing source files with sourcemaps.

Example .biomeignore/.eslintignore entry:

assets/build/**

src/blocks/commonControls/AlignmentControls.js (2)

30-76: DRY the four nearly identical handlers

Reduce repetition and accidental divergence by using a generic updater.

Example:

-const handleDirectionAlignmentChange = (value) => { /* ...direction... */ };
-const handleTextAlignmentChange = (value) => { /* ...textAlign... */ };
-const handleHorizontalAlignmentChange = (value) => { /* ...justifyContent... */ };
-const handleVerticalAlignmentChange = (value) => { /* ...alignItems... */ };
+const updateAlignment = (key) => (value) =>
+  setAttributes({
+    alignmentControls: {
+      ...alignmentControls,
+      [device]: {
+        ...currentAlignment,
+        [key]: value,
+      },
+    },
+  });
+
+const handleDirectionAlignmentChange = updateAlignment('direction');
+const handleTextAlignmentChange = updateAlignment('textAlign');
+const handleHorizontalAlignmentChange = updateAlignment('justifyContent');
+const handleVerticalAlignmentChange = updateAlignment('alignItems');

---

196-219: Prefer removing keys over saving nulls on Reset

Persisting null bloats attribute storage and requires extra null checks. Remove the keys for the current device instead.

- onClick={() => {
-   setAttributes({
-     alignmentControls: {
-       ...alignmentControls,
-       [device]: {
-         ...currentAlignment,
-         textAlign: null,
-         alignItems: null,
-         justifyContent: null,
-         direction: null,
-       },
-     },
-   });
- }}
+ onClick={() => {
+   const { textAlign, alignItems, justifyContent, direction, ...rest } = currentAlignment || {};
+   setAttributes({
+     alignmentControls: {
+       ...alignmentControls,
+       [device]: rest,
+     },
+   });
+ }}

Ensure downstream CSS generation handles missing keys (undefined) correctly.

src/blocks/components/BackgroundControl.js (2)

15-27: Default onChange handlers to no-ops to prevent crashes

If a parent omits a handler, RadioControl/TextControl/MediaUpload will call undefined.

-const BackgroundControl = ({
+const BackgroundControl = ({
   label,
   backgroundType = 'classic',
-  onBackgroundTypeChange,
+  onBackgroundTypeChange = () => {},
   backgroundColor,
-  onBackgroundColorChange,
+  onBackgroundColorChange = () => {},
   backgroundGradient,
-  onBackgroundGradientChange,
+  onBackgroundGradientChange = () => {},
   backgroundImage = {},
-  onBackgroundImageChange,
+  onBackgroundImageChange = () => {},
   showGradient = true,
   showImage = true
 }) => {

---

31-39: Optional UX polish: clear opposite-type state on switch

Avoid stale values when toggling type.

- onChange={onBackgroundTypeChange}
+ onChange={(type) => {
+   onBackgroundTypeChange(type);
+   if (type === 'classic') onBackgroundGradientChange?.('');
+   if (type === 'gradient') onBackgroundColorChange?.('');
+ }}

Also, when selecting an image, consider fallback alt (media.alt || media.title || '').

Also applies to: 57-66, 69-107

src/blocks/commonControls/DimensionsControls.js (2)

98-154: Consistency: consider supplying explicit units to UnitControl

DimensionControl.js defines units; this component leaves defaults. Aligning units across both improves UX and predictability.

Example:

 <UnitControl
   __next40pxDefaultSize
   label={__('Fixed', 'wedocs')}
   value={currentDimensions.width || ''}
+  units={[ { value: 'px', label: 'px' }, { value: '%', label: '%' }, { value: 'em', label: 'em' }, { value: 'rem', label: 'rem' } ]}

Repeat for min/max width/height.

Also applies to: 171-227

---

230-258: Prefer removing keys over saving nulls on Reset

Same rationale as AlignmentControls.

- [device]: {
-   ...currentDimensions,
-   width: null,
-   minWidth: null,
-   maxWidth: null,
-   height: null,
-   minHeight: null,
-   maxHeight: null,
-   padding: null,
-   margin: null,
-   blockSpacing: null,
- },
+[device]: ((d) => {
+  const {
+    width, minWidth, maxWidth,
+    height, minHeight, maxHeight,
+    padding, margin, blockSpacing,
+    ...rest
+  } = d || {};
+  return rest;
+})(currentDimensions),

src/blocks/components/DimensionControl.js (1)

8-16: Default onChange handlers to no-ops

Prevents accidental crashes if a parent forgets a handler.

-const DimensionControl = ({
+const DimensionControl = ({
   label,
   widthValue,
-  onWidthChange,
+  onWidthChange = () => {},
   heightValue,
-  onHeightChange,
+  onHeightChange = () => {},
   showHeight = true,
   linkValues = false
 }) => {

assets/build/print-rtl.css (4)

39-40: Remove duplicate border declaration

Only the latter applies; drop the first to avoid confusion.

-  border: 1px solid #ccc;
-  border: 1px solid rgba(0, 0, 0, 0.15);
+  border: 1px solid rgba(0, 0, 0, 0.15);

---

36-37: Deduplicate white-space

The second overrides the first. Keep pre-wrap for readability in print.

-  white-space: pre;
-  white-space: pre-wrap;
+  white-space: pre-wrap;

---

55-56: Resolve conflicting font-size declarations

font-size appears twice; only last wins. Keep the intended value (15px shown later) and remove the earlier one.

-  font-size: 18px;
   line-height: 1.2em;
   border-radius: 50px;
   color: #fff;
   background: #3197d1;
   vertical-align: baseline;
   white-space: nowrap;
-  font-size: 15px;
+  font-size: 15px;

Also applies to: 62-62

---

141-144: Drop duplicate selector

Same selector listed twice.

-a:not(.anchorjs-link)::after,
-a:not(.anchorjs-link)::after {
+a:not(.anchorjs-link)::after {
   content: ' (' attr(href) ')';
 }

src/blocks/TableOfContents/style.scss (3)

63-67: Use logical properties to support RTL

Replace left-specific properties with logical ones.

- border-left: 3px solid #0073aa;
- padding-left: 10px;
+ border-inline-start: 3px solid #0073aa;
+ padding-inline-start: 10px;

---

133-135: Respect reduced motion preferences

Avoid forced smooth scrolling when users prefer reduced motion.

 html.smooth-scroll {
   scroll-behavior: smooth;
 }
+@media (prefers-reduced-motion: reduce) {
+  html.smooth-scroll {
+    scroll-behavior: auto;
+  }
+}

---

137-151: Avoid non-localizable CSS-generated content

The loading message is hardcoded via content: and can’t be localized/accessibility-announced. Prefer rendering this text in markup with an ARIA live region.

src/blocks/commonControls/ColorsControls.js (1)

17-17: Remove unused props

isTextColor, isBackgroundColor, isLinkColor are declared but unused. Drop them or implement conditional rendering.

assets/build/blocks/DocsGrid/index.js (2)

1-1: Avoid per_page: -1 REST queries in editor

Fetching all docs/sections/articles can be slow on large sites. Paginate or limit plus on-demand fetch to improve editor perf.

---

1-1: Consider excluding built assets from PRs

Minified bundles create noisy diffs and false-positive lint. Commit sources and rely on build steps or attach artifacts on releases.

assets/build/frontend-rtl.css (2)

508-516: Conflicting font-size declarations

font-size is set to 18px then 15px for the same selector; the latter wins. Remove one for clarity.

-  font-size: 18px;
   line-height: 1.2em;
   border-radius: 50px;
   color: #fff;
   background: #3197d1;
   vertical-align: baseline;
   white-space: nowrap;
-  font-size: 15px;
+  font-size: 15px;

---

164-168: Prefer overflow: auto for hit list

overflow: scroll always shows scrollbars; auto avoids visual noise.

-  overflow: scroll;
+  overflow: auto;

src/blocks/Contributors/edit-old.js (4)

10-23: Prune unused imports

RangeControl and ButtonGroup appear unused. Remove to reduce bundle size.

---

66-71: currentPost is computed but unused

Either wire it into preview/data fetching or remove it.

---

92-100: Avatar border radius used but not configurable here

rounded uses attributes.avatarBorderRadius, but this UI doesn’t expose a control to set it. Add a UnitControl or remove the dependency.

---

28-29: Remove edit-old.js — it's unused and superseded by edit.js.

Verification confirms src/blocks/Contributors/index.js imports from ./edit (not edit-old), and there are no references to edit-old.js anywhere in the codebase. The file appears to be legacy code that was fully replaced by edit.js. Keeping it risks maintenance burden and accidental edits to the wrong file.

src/blocks/helpers/block-styles.php (3)

141-149: Gradient is overridden by image; support layered backgrounds.

Currently background-image gets set twice; the URL wins and gradient is lost. Compose a single declaration:

-    if ($background_type === 'gradient' && $background_gradient) {
-        $styles[] = 'background-image: ' . esc_attr($background_gradient);
-    }
-    if (isset($background_image['url']) && !empty($background_image['url'])) {
-        $styles[] = 'background-image: url(' . esc_url($background_image['url']) . ')';
-        $styles[] = 'background-size: cover';
-        $styles[] = 'background-position: center';
-    }
+    $images = [];
+    if ($background_type === 'gradient' && $background_gradient) {
+        $images[] = esc_attr($background_gradient);
+    }
+    if (!empty($background_image['url'])) {
+        $images[] = 'url(' . esc_url($background_image['url']) . ')';
+        $styles[] = 'background-size: cover';
+        $styles[] = 'background-position: center';
+    }
+    if ($images) {
+        $styles[] = 'background-image: ' . implode(', ', $images);
+    }

Also applies to: 145-149

---

236-242: Avoid dropping legitimate “0” values in styles_to_css.

array_filter without a callback treats "0" as empty. Use strlen to keep "margin: 0" strings intact (future-proofing).

-    return implode('; ', array_filter($styles));
+    return implode('; ', array_filter($styles, 'strlen'));

---

290-311: Broaden sanitizer to modern CSS functions.

calc(), clamp(), min(), max(), and var() are common in block styles. Consider supporting them to avoid stripping valid input. Example approach (illustrative):

-    if (preg_match('/^(-?\d*\.?\d+)([a-z%]+)?$/i', $value, $matches)) {
+    if (preg_match('/^(-?\d*\.?\d+)([a-z%]+)?$/i', $value, $matches)) {
         ...
-    }
+    } elseif (preg_match('/^(calc|clamp|min|max)\(.+\)$/i', $value) || preg_match('/^var\(--[a-z0-9\-\_]+\)$/i', $value)) {
+        return $value;
+    }

src/blocks/commonControls/BackgroundImageControls.js (1)

18-19: Hoist static constants outside the component.

Move ALLOWED_MEDIA_TYPES to module scope to avoid re-allocating on every render.

-const BackgroundImageControls = ({ attributes, setAttributes, device }) => {
-    const { backgroundImageControls } = attributes;
-    const currentBackgroundImage = backgroundImageControls[device] || {};
-
-    const ALLOWED_MEDIA_TYPES = ['image'];
+const ALLOWED_MEDIA_TYPES = [ 'image' ];
+const BackgroundImageControls = ({ attributes, setAttributes, device }) => {
+    const { backgroundImageControls } = attributes;
+    const currentBackgroundImage = backgroundImageControls[device] || {};

src/blocks/AdvanceContributors/edit-old.js (3)

151-161: Use WordPress date i18n utilities for preview date.

Respect site locale/timezone for the editor preview.

-import { useSelect } from '@wordpress/data';
+import { useSelect } from '@wordpress/data';
+import { dateI18n, getSettings as getDateSettings } from '@wordpress/date';
...
-                        <span style={dateStyle}>
-                            {attributes.datePrefix} {new Date().toLocaleDateString('en-US', {
-                                year: 'numeric',
-                                month: 'long',
-                                day: 'numeric'
-                            })}
-                        </span>
+                        <span style={dateStyle}>
+                            { attributes.datePrefix } { dateI18n( getDateSettings().formats.date || 'F j, Y', Date.now() ) }
+                        </span>

---

292-320: Capture media ID with background image for better caching and REST usage.

Store id alongside url/alt to allow size switching and consistent serialization.

-    onSelect={(media) => setAttributes({
-        backgroundImage: { url: media.url, alt: media.alt }
-    })}
+    onSelect={(media) => setAttributes({
+        backgroundImage: { id: media.id, url: media.url, alt: media.alt }
+    })}

If server render uses IDs for responsive sources, ensure schema accepts backgroundImage.id.

---

33-49: Consider centralizing style generation via the new PHP helpers (parity).

Inline editor styles duplicate logic now present in src/blocks/helpers/block-styles.php. A small utility mirroring the helper on the client would reduce drift and bugs.

Happy to sketch a tiny JS style-builder to keep parity with wedocs_build_* helpers.

src/blocks/AdvanceContributors/index.js (1)

12-16: Update comment to match inline implementation.

The comment references ./save.js but the save function is defined inline. Since this block uses server-side rendering (returning null), consider either:

1. Removing the comment, or
2. Updating it to reflect the inline implementation

 	/**
-	 * @see ./save.js
+	 * Server-side rendered block - save returns null
 	 */
 	save: () => null,

src/blocks/TableOfContents/index.js (1)

29-35: Remove trailing whitespace.

Clean up the trailing whitespace at the end of the file.

 registerBlockType( metadata.name, {
 	/**
 	 * @see ./edit.js
 	 */
 	edit: Edit,
 } );
-	

src/blocks/Contributors/save.js (1)

1-11: Remove unused blockProps variable.

Since this is a server-rendered block that returns null, the useBlockProps.save() call and blockProps variable are unnecessary and can be removed. The import can also be removed.

-import { useBlockProps } from '@wordpress/block-editor';
-
 const Save = () => {
-	const blockProps = useBlockProps.save();
-
 	// Since this is a dynamic block that uses PHP rendering,
 	// we return null to let the server-side render function handle the output
 	return null;
 };

 export default Save;

src/blocks/TableOfContents/controls/ListItems.js (1)

18-22: Remove commented-out code.

The commented-out ColorsControls block should either be implemented or removed. Leaving commented code in production decreases maintainability.

src/blocks/Contributors/style.scss (1)

105-108: Consider removing !important if possible.

The !important flags on lines 106-107 for avatar sizing may indicate specificity issues. If possible, increase selector specificity instead to avoid !important.

.contributor-avatar {
    // Smaller avatars on mobile
    img, .default-icon {
        width: 28px;
        height: 28px;
    }
}

If these rules are being overridden elsewhere, consider refactoring the CSS architecture rather than using !important.

src/blocks/Contributors/index.js (1)

19-41: Consider extracting icon styles to constants.

The inline styles for the PRO badge could be extracted to named constants for better maintainability and reusability if this pattern is used across multiple blocks.

const PRO_BADGE_STYLES = {
    badge: {
        position: 'absolute',
        top: '22px',
        right: '-2px',
        background: '#4f47e6',
        color: 'white',
        fontSize: '9px',
        padding: '2px 3px',
        borderRadius: '3px',
        fontWeight: 'bold',
        lineHeight: 1
    },
    wrapper: {
        position: 'relative',
        display: 'inline-block'
    }
};

icon: {
    src: () => (
        <span style={PRO_BADGE_STYLES.wrapper}>
            <Icon icon={starFilled} />
            <span style={PRO_BADGE_STYLES.badge}>PRO</span>
        </span>
    ),
}

wedocs.php (1)

185-185: Remove or uncomment the AdvanceContributors block.

Line 185 has the AdvanceContributors block commented out. Either enable it or remove the comment to keep the codebase clean.

assets/build/blocks/DocsGrid/render.php (3)

10-37: Prefix or scope helper function to avoid global collisions.

get_pagination_style_tag() is unprefixed and global. Prefer wedocs_get_pagination_style_tag(), or make it a private helper inside render_wedocs_docs_grid(). The new function_exists guard helps but namespacing is safer.

---

183-183: Remove unused variables or implement their usage.

$total_pages and $total_articles are declared but never used. Either remove them or render pagination/article counts. This also silences PHPMD warnings.

Also applies to: 228-228

---

184-206: Inline <script>: consider enqueueing and optional chaining support.

Move the toggle JS to an enqueued script or wp_add_inline_script attached to the block handle to play well with CSP and caching. Also verify that optional chaining (?.) meets your supported browsers for front-end visitors.

Would you confirm your browser support baseline and whether CSP is enforced on typical installs?

src/blocks/TableOfContents/ColorsControls.js (1)

21-28: Prefer stable APIs to fetch theme palettes.

Consider using useSetting for palettes/gradients to avoid unsafe WP APIs and the eslint disable.

Example:

import { useSetting } from '@wordpress/block-editor';
const themeColors = useSetting( 'color.palette' ) || [];
const themeGradients = useSetting( 'color.gradients' ) || [];

If other controls already use useSetting (e.g., BorderAndShadowControls.js), align for consistency.

assets/build/blocks/Contributors/style-index-rtl.css (1)

1-1: Scope note: avoid cross-component bleed.

This stylesheet also targets .contributors-tab-system .components-button-group. Ensure this file is only enqueued where needed, or move editor-only styles to the editor stylesheet to avoid front-end collisions.

src/blocks/components/ShadowControl.js (3)

5-7: Avoid confusion with local UnitControl by renaming the WP import.

You already have a custom UnitControl in the codebase. Rename the WP import to clarify intent.

- __experimentalUnitControl as UnitControl,
+ __experimentalUnitControl as WPUnitControl,

And update usages:

- <UnitControl ...
+ <WPUnitControl ...

Confirm no other imports in this file shadow the same name.

Also applies to: 41-51, 55-64, 69-78, 83-92

---

16-21: Defensive: guard onShadowChange.

If onShadowChange is omitted, updateShadow will throw. Either require it or no-op guard:

- const updateShadow = (key, newValue) => {
-   onShadowChange({
+ const updateShadow = (key, newValue) => {
+   (onShadowChange || (() => {}))({
      ...shadowValue,
      [key]: newValue
    });
  };

---

96-106: API check: PanelColorSettings deprecation.

PanelColorSettings has been phased out in favor of ToolsPanel/ColorGradientControl in newer WP. If you target recent core, plan a follow-up to migrate.

assets/build/blocks/AdvanceContributors/block.json (1)

1-16: Missing textdomain in block.json

Consider adding "textdomain": "wedocs" to enable proper i18n tooling for strings in metadata.

src/blocks/components/BorderControl.js (2)

26-41: Reset width/color when switching to “None”

If users set width/color then choose “None”, stale styles may persist downstream.

Apply:

-            onChange={onBorderStyleChange}
+            onChange={(newStyle) => {
+                onBorderStyleChange(newStyle);
+                if (newStyle === 'none') {
+                    onBorderWidthChange({});
+                    onBorderColorChange(undefined);
+                }
+            }}

---

87-96: PanelColorSettings is deprecated in newer WP; consider ToolsPanel/ColorPalette

Future-proof by migrating to ColorSettings within ToolsPanel or use block-editor color support if applicable.

src/blocks/Contributors/render.php (1)

12-18: Unused parameters + missing $post guard

Silence analyzers and avoid fatals on non-singular contexts.

-    function render_wedocs_contributors_block($attributes, $content, $block) {
-        // Get the current post
-        $post = get_post();
+    function render_wedocs_contributors_block($attributes, $content, $block) {
+        // Silence unused params
+        unset($content, $block);
+        // Get the current post
+        $post = get_post();
+        if ( ! $post ) {
+            return '';
+        }

Also applies to: 19-39

assets/build/blocks/AdvanceContributors/style-index-rtl.css (1)

1-1: Contrast media query value and legacy prefix

• prefers-contrast: high is non-standard; use "more" for broader support.
• The -o-object-fit prefix is obsolete.

Apply:

-@media(prefers-contrast: high){
+@media(prefers-contrast: more){

And drop "-o-object-fit: cover".

src/blocks/AdvanceContributors/style.scss (3)

64-75: Add visible focus styles for keyboard users.

Anchors only style :hover. Include :focus-visible for parity and WCAG compliance.

 .contributor-name {
   transition: color 0.3s ease;
   text-decoration: none;
+  outline: none;
+  &:focus-visible {
+    outline: 2px solid currentColor;
+    outline-offset: 2px;
+    text-decoration: underline;
+  }
 }

---

49-61: Use CSS variables instead of hard-coded brand colors.

Replace fixed hex with theme variables to improve theming and dark-mode harmony.

- .default-icon {
-   background-color: #0073aa;
-   color: white;
+ .default-icon {
+   --wedocs-accent: var(--wp--preset--color--primary, #0073aa);
+   --wedocs-on-accent: var(--wp--preset--color--background, #fff);
+   background-color: var(--wedocs-accent);
+   color: var(--wedocs-on-accent);
 }
@@
-  .contributor-item {
-    .contributor-avatar .default-icon {
-      background-color: #4a90a4;
-    }
-  }
+  .contributor-item .contributor-avatar .default-icon {
+    background-color: color-mix(in oklab, var(--wedocs-accent) 70%, black);
+  }

Also applies to: 151-156

---

103-109: Avoid !important; raise specificity instead.

!important makes overrides harder. Prefer a more specific selector or block-scoped size token.

- img, .default-icon {
-   width: 28px !important;
-   height: 28px !important;
- }
+ img, .default-icon {
+   width: 28px;
+   height: 28px;
+ }

If collisions occur, scope via .wedocs-contributors .contributors-container .contributor-item .contributor-avatar img rather than using !important.

assets/build/blocks/TableOfContents/view.js (1)

1-1: Scope heading search to the nearest content container; reduce O(n²) and support H6.

• Limit to the block’s nearest article/content container to avoid cross-picking headings from the whole page.
• Replace Array.from(list).indexOf(node) with the loop index.
• Initialize counters up to H6.

- const c=document.querySelector(".entry-content, .post-content, main, .content")||document.body
+ const c = t.closest("article, .entry-content, .post-content, main, .content") || document.body;
@@
- const i={1:0,2:0,3:0,4:0,5:0};
+ const i={1:0,2:0,3:0,4:0,5:0,6:0};
@@
- t.forEach(function(e){
-   const l=parseInt(e.tagName.charAt(1))
+ t.forEach(function(e, idx){
+   const l = Math.min(6, parseInt(e.tagName.charAt(1), 10) || 2);
@@
-   const a = e.id || "toc-heading-"+Array.from(t).indexOf(e);
+   const a = e.id || "toc-heading-" + idx;

src/blocks/DocsGrid/render.php (4)

183-183: Remove or use $total_pages; currently unused.

Either render pagination or drop the variable. See next comment for adding pagination.

- $total_pages = $docs_query->max_num_pages;
+ $total_pages = $docs_query->max_num_pages; // Use below if pagination is enabled.

---

42-53: Wire up pagination rendering and style variables.

Attributes include pagination settings but output is missing; also get_pagination_style_tag() is never used.

@@
-        $show_view_details = $attributes['showViewDetails'] ?? true;
+        $show_view_details = $attributes['showViewDetails'] ?? true;
+        $enable_pagination = $attributes['enablePagination'] ?? false;
@@
-        // Query docs with pagination
+        // Query docs with pagination
         $docs_query = new WP_Query($args);
@@
-        echo $toggle_script;
-        // Output hover styles
-        echo $hover_styles;
+        // Pagination CSS variables
+        echo get_pagination_style_tag( $attributes );
+        echo $toggle_script;
+        echo $hover_styles;
@@
-            </div>
-        </div>
+            </div>
+        </div>
+        <?php if ( $enable_pagination && $docs_per_page !== 'all' && $total_pages > 1 ) : ?>
+            <nav class="wedocs-docs-grid__pagination" aria-label="<?php esc_attr_e('Docs navigation', 'wedocs'); ?>">
+                <?php
+                echo paginate_links( array(
+                    'total'   => $total_pages,
+                    'current' => max( 1, (int) $current_page ),
+                    'type'    => 'list',
+                    'prev_text' => __('Previous', 'wedocs'),
+                    'next_text' => __('Next', 'wedocs'),
+                ) );
+                ?>
+            </nav>
+        <?php endif; ?>
         <?php
         return ob_get_clean();

Also applies to: 158-171, 210-213, 319-323

---

256-257: Compose inline styles once and escape as a whole.

Avoid mixing escaped and raw CSS fragments inside the attribute.

- <h4 class="wedocs-docs-grid__section-title"
-     style="<?php echo esc_attr($title_style); ?> display: flex; justify-content: space-between; align-items: center;">
+ <?php $section_title_style = trim($title_style . ' display:flex; justify-content:space-between; align-items:center;'); ?>
+ <h4 class="wedocs-docs-grid__section-title" style="<?php echo esc_attr( $section_title_style ); ?>">

---

228-228: Remove $total_articles or implement usage.

Declared but never used.

- $total_articles = 0;
+ // $total_articles reserved for future use; remove if not needed.

src/blocks/commonControls/BorderAndShadowControls.js (3)

123-131: Avoid boolean className.

Passing false can stringify to "false". Use a conditional string.

- className={isOpen && 'is-open'}
+ className={isOpen ? 'is-open' : undefined}

---

215-237: Reset to undefined/null to fall back cleanly.

Setting empty objects keeps truthy values around. Prefer null/undefined to fully reset.

- border: {},
- borderRadius: null,
- boxShadow: {},
+ border: undefined,
+ borderRadius: undefined,
+ boxShadow: undefined,

---

35-46: Confirm boxShadow key naming consistency.

This control uses { x, y, blur, spread, color, inset }. Ensure all consumers/readers (renderers/styles) expect these keys (not horizontal/vertical). If not, map keys at the boundary.

src/blocks/Contributors/block.json (1)

27-30: Potential contrast issue for titleColor default.

Title defaults to #fff while backgroundColor defaults to #f9f9f9; visually OK, but if a theme sets a white background it may become invisible. Consider a darker default (e.g., #111).

src/blocks/TableOfContents/Inspector.js (1)

19-77: Unify textdomain with the block’s domain (“wedocs”).

Strings use 'dynamic-table-of-contents-block-wp' while block.json declares 'wedocs'. Aligning domains improves translation loading.

- __('TOC Title', 'dynamic-table-of-contents-block-wp')
+ __('TOC Title', 'wedocs')
# Apply to all __() calls in this file.

Also applies to: 94-223

assets/build/blocks/Contributors/render.php (2)

290-306: Small UX/accessibility hardening on avatar rendering.

• Add loading="lazy" and decoding="async" to .
• Mark the default icon container as aria-hidden.

-                    $output .= '<img src="' . esc_url($avatar_url) . '" alt="' . esc_attr($contributor->display_name) . '" style="' . wedocs_styles_to_css($avatar_styles) . '">';
+                    $output .= '<img src="' . esc_url($avatar_url) . '" alt="' . esc_attr($contributor->display_name) . '" loading="lazy" decoding="async" style="' . wedocs_styles_to_css($avatar_styles) . '">';
...
-                    $output .= '<div class="default-icon" style="' . wedocs_styles_to_css($icon_styles) . '">';
+                    $output .= '<div class="default-icon" aria-hidden="true" style="' . wedocs_styles_to_css($icon_styles) . '">';

---

12-12: Silence PHPMD UnusedFormalParameter for $content and $block.

WP render callbacks accept ($attributes, $content, $block) even if unused. Prefix unused params to signal intent.

-    function render_wedocs_contributors_block($attributes, $content, $block) {
+    function render_wedocs_contributors_block($attributes, $_content = null, $_block = null) {

Alternatively, add a PHPMD ignore for these params.

src/blocks/TableOfContents/edit.js (1)

154-163: Typo in CSS custom property name.

"--list-item-sytle" → "--list-item-style" (or remove if unused). Typo prevents styles from applying.

-            "--list-item-sytle": containerBackgroundColor,
+            "--list-item-style": containerBackgroundColor,

src/blocks/TableOfContents/view.js (3)

57-61: Avoid assembling HTML with strings; build DOM nodes to reduce XSS/escaping risk.

Even with textContent, innerHTML concatenation is fragile. Prefer createElement/append with textContent.

Example replacement for this block:

-        const tocHTML = generateTOCHTML(headings, supportedHeadings, showHierarchy, showNumbering);
-        const tocContent = tocBlock.querySelector('.toc-content');
-        tocContent.innerHTML = tocHTML;
+        const tocContent = tocBlock.querySelector('.toc-content');
+        tocContent.innerHTML = '';
+        tocContent.appendChild(
+          generateTOCListElement(headings, supportedHeadings, showHierarchy, showNumbering)
+        );

…with a new generateTOCListElement that returns a UL element constructed via createElement.

---

150-160: Add a11y state to collapsible behavior.

Toggle aria-expanded on the title and aria-hidden on the content; announce via role="button".

-        if (title && content) {
-            title.addEventListener('click', function() {
-                title.classList.toggle('collapsed');
-                content.classList.toggle('collapsed');
-            });
-        }
+        if (title && content) {
+            title.setAttribute('role', 'button');
+            title.setAttribute('aria-controls', 'toc-content');
+            title.setAttribute('aria-expanded', 'true');
+            content.id = 'toc-content';
+            title.addEventListener('click', function() {
+                const expanded = title.getAttribute('aria-expanded') === 'true';
+                title.setAttribute('aria-expanded', String(!expanded));
+                title.classList.toggle('collapsed');
+                content.classList.toggle('collapsed');
+                content.setAttribute('aria-hidden', String(expanded));
+            });
+        }

---

217-236: Preserve URL hash on smooth scroll.

Currently prevents default without updating history, so deep links don’t work. Push the hash after scrolling.

                 if (targetElement) {
                     const offsetTop = targetElement.offsetTop - 80; // Account for sticky headers
@@
                     } else {
                         // Fallback smooth scroll
                         animateScrollTo(offsetTop, 600);
                     }
+                    // Update hash without jump
+                    history.replaceState(null, '', '#' + targetId);
                 }

src/blocks/AdvanceContributors/edit.js (2)

164-179: Parallelize manual user fetch to reduce editor latency.

Serial await in a loop is slow with many users. Use Promise.all and filter nulls.

-                        if (attributes.selectedContributors.length > 0) {
-                            for (const userId of attributes.selectedContributors) {
-                                try {
-                                    const user = await wp.apiFetch({
-                                        path: `/wp/v2/users/${userId}?context=edit`
-                                    });
-                                    if (user) {
-                                        contributors.push(user);
-                                    }
-                                } catch (error) {
-                                    console.warn(`Could not fetch user ${userId}:`, error);
-                                }
-                            }
-                        }
+                        if (attributes.selectedContributors.length > 0) {
+                            const fetched = await Promise.all(
+                                attributes.selectedContributors.map((userId) =>
+                                    wp.apiFetch({ path: `/wp/v2/users/${userId}?context=edit` }).catch((e) => {
+                                        console.warn(`Could not fetch user ${userId}:`, e);
+                                        return null;
+                                    })
+                                )
+                            );
+                            contributors.push(...fetched.filter(Boolean));
+                        }

---

193-221: Minor: also dedupe against the main author when merging revisions.

You already track contributorIds; ensure main author is included initially to avoid duplicates.

-                                const contributorIds = [currentPost.author];
+                                const contributorIds = [currentPost.author];

This is correct as written. Please verify that get users for both main author and revisions do not produce duplicates in displayContributors. If duplicates appear, add a final Map by id when setting state:

-                setActualContributors(contributors);
+                const uniq = Array.from(new Map(contributors.map(u => [u.id || u.ID, u])).values());
+                setActualContributors(uniq);

src/blocks/TableOfContents/render.php (1)

14-44: Emit styles via wp_add_inline_style and traverse nested blocks.

• Printing a raw <style> in wp_head is brittle. Prefer wp_add_inline_style against an enqueued handle.
• parse_blocks() only inspects top-level blocks; recurse innerBlocks to style nested TOCs.

- add_action( 'wp_head', 'wedocs_dynamic_table_of_contents_inline_styles' );
+ add_action( 'wp_enqueue_scripts', 'wedocs_dynamic_table_of_contents_inline_styles', 20 );
@@
-        $blocks = parse_blocks( $post->post_content );
-        $styles = '';
-        foreach ( $blocks as $block ) {
+        $blocks  = parse_blocks( $post->post_content );
+        $styles  = '';
+        $walker  = function( $blocks ) use ( &$styles ) {
+            foreach ( $blocks as $block ) {
+                if ( 'wedocs/table-of-contents' === ( $block['blockName'] ?? '' ) ) {
+                    $attributes = $block['attrs'] ?? array();
+                    $block_id   = $attributes['blockId'] ?? '';
+                    if ( $block_id ) {
+                        $styles .= wedocs_generate_toc_styles( $attributes, $block_id );
+                    }
+                }
+                if ( ! empty( $block['innerBlocks'] ) ) {
+                    $walker( $block['innerBlocks'] );
+                }
+            }
+        };
+        $walker( $blocks );
@@
-        if ( ! empty( $styles ) ) {
-            echo '<style id="dynamic-toc-styles">' . $styles . '</style>';
-        }
+        if ( ! empty( $styles ) ) {
+            // Ensure 'wedocs-toc' (or actual handle) is registered/enqueued beforehand.
+            wp_add_inline_style( 'wedocs-toc', $styles );
+        }

Also applies to: 25-37, 39-44

src/blocks/helpers/block-helpers.js (4)

23-31: Gradient overwritten by image; honor backgroundType.

When backgroundType is 'gradient', subsequent backgroundImage url() assignment overrides it. Gate the image path by type.

- if (attributes.backgroundImage?.url) {
+ if (attributes.backgroundType !== 'gradient' && attributes.backgroundImage?.url) {
     styles.backgroundImage = `url(${attributes.backgroundImage.url})`;
     styles.backgroundSize = 'cover';
     styles.backgroundPosition = 'center';
 }

---

250-267: Allow common CSS functions (calc, var, clamp).

Current validator rejects calc()/var()/clamp(). Broaden acceptance to typical safe patterns.

- const regex = /^(-?\d*\.?\d+)([a-z%]+)?$/i;
+ const functionOk = /^(calc|var|clamp)\(/i.test(value.trim());
+ if (functionOk) return true;
+ const regex = /^(-?\d*\.?\d+)([a-z%]+)?$/i;

---

374-390: Guard for SSR/Node usage.

Accessing window breaks SSR/tests. Add typeof window check and default false.

-export const isBreakpoint = (breakpoint) => {
-  const breakpoints = getBreakpoints();
-  const width = window.innerWidth;
+export const isBreakpoint = (breakpoint) => {
+  if (typeof window === 'undefined') return false;
+  const breakpoints = getBreakpoints();
+  const width = window.innerWidth;

---

231-241: Expose cancel() on debounce for cleanup in effects.

Helps avoid stray timers.

 export const debounce = (func, wait) => {
   let timeout;
-  return function executedFunction(...args) {
+  const debounced = function executedFunction(...args) {
     const later = () => {
       clearTimeout(timeout);
       func(...args);
     };
     clearTimeout(timeout);
     timeout = setTimeout(later, wait);
   };
+  debounced.cancel = () => clearTimeout(timeout);
+  return debounced;
 };

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

TOC link color custom property likely misbound.

The bundle sets {"--list-item-sytle": containerBackgroundColor}. That appears intended for listColor. Please adjust in the source (e.g., src/blocks/TableOfContents/edit.js) and fix the property name typo across CSS/JS.

---

I need to verify the source code to confirm the issue. Let me search for the TableOfContents block implementation.

[/run_scripts]

[/run_scripts]

[/run_scripts]

---

🏁 Script executed:

#!/bin/bash
# Find TableOfContents block source files
fd -type f -name "*.js" -path "*TableOfContents*" | head -20
fd -type f -name "*.jsx" -path "*table-of-contents*" -o -path "*toc*" | grep -v node_modules | head -20

Length of output: 341

---

🏁 Script executed:

#!/bin/bash
# Search for the specific CSS custom property in source files
rg -n "list-item" --type=js --type=jsx -B2 -A2 | head -50
rg -n "containerBackgroundColor" --type=js --type=jsx -B3 -A3 | grep -i "style\|toc\|list" | head -50

Length of output: 55

---

🏁 Script executed:

#!/bin/bash
# Look for TOC block edit file and check the style object
find . -type f \( -name "*edit.js" -o -name "*edit.jsx" \) | xargs grep -l "toc\|table-of-contents" -i 2>/dev/null

Length of output: 36

---

Now let me examine the source file to verify the CSS custom property binding:

[/run_scripts]

[/run_scripts]

---

🏁 Script executed:

#!/bin/bash
# View the TableOfContents edit.js file
cat ./src/blocks/TableOfContents/edit.js

Length of output: 6113

---

🏁 Script executed:

#!/bin/bash
# Search for the style object and CSS custom properties in edit.js
grep -n "\-\-list\|containerBackgroundColor\|listColor" ./src/blocks/TableOfContents/edit.js -A2 -B2

Length of output: 695

---

Fix CSS custom property binding and typo in TableOfContents block.

Line 154 in src/blocks/TableOfContents/edit.js contains two errors:

• Property name typo: --list-item-sytle should be --list-item-style
• Wrong variable: should bind listColor (used for list text, line 184) instead of containerBackgroundColor (container background)

Change:

"--list-item-sytle": containerBackgroundColor,

to:

"--list-item-style": listColor,

🧰 Tools

🪛 Biome (2.1.2)

[error] 1-1: This variable is used before its declaration.

The variable is declared here:

(lint/correctness/noInvalidUseBeforeDeclaration)

---

[error] 1-1: This variable is used before its declaration.

The variable is declared here:

(lint/correctness/noInvalidUseBeforeDeclaration)

---

[error] 1-1: This variable is used before its declaration.

The variable is declared here:

(lint/correctness/noInvalidUseBeforeDeclaration)

---

[error] 1-1: This variable is used before its declaration.

The variable is declared here:

(lint/correctness/noInvalidUseBeforeDeclaration)

---

[error] 1-1: Shouldn't redeclare 'a'. Consider to delete it or rename it.

'a' is defined here:

(lint/suspicious/noRedeclare)

---

[error] 1-1: Shouldn't redeclare 'l'. Consider to delete it or rename it.

'l' is defined here:

(lint/suspicious/noRedeclare)

---

[error] 1-1: Shouldn't redeclare 'n'. Consider to delete it or rename it.

'n' is defined here:

(lint/suspicious/noRedeclare)

---

[error] 1-1: This variable is used before its declaration.

The variable is declared here:

(lint/correctness/noInvalidUseBeforeDeclaration)

---

[error] 1-1: This variable is used before its declaration.

The variable is declared here:

(lint/correctness/noInvalidUseBeforeDeclaration)

🤖 Prompt for AI Agents

In assets/build/block.js around lines 1 to 1, the inline style object for the
TableOfContents block uses a misspelled CSS custom property and binds the wrong
variable; change the entry that currently sets "--list-item-sytle" to instead
set "--list-item-style" and bind it to the list color variable used elsewhere
(replace the container background variable with the listColor variable).

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Box shadow schema doesn’t match renderer expectations

Defaults use "horizontal"/"vertical", but the renderer in AdvanceContributors expects "x"/"y", so shadows will never render.

Either:

• Change defaults to x/y, or
• Update the renderer to read "horizontal"/"vertical".
  If you keep schema as-is, align the PHP at Box Shadow handling. See related comment in render.php.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

$post may be null; unsafe property access

Accessing $post->ID without verifying $post will fatal on non-singular contexts or previews.

Guard before use:

-        case 'main_author':
-            $author_id = get_post_field('post_author', $post->ID);
+        case 'main_author':
+            if ( ! $post ) { break; }
+            $author_id = get_post_field('post_author', $post->ID);

Repeat this pattern wherever $post->ID is used.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	case 'main_author':
	$author_id = get_post_field('post_author', $post->ID);
	if ($author_id) {
	$author_user = get_userdata($author_id);
	if ($author_user) {
	$contributors[] = $author_user;
	}
	}
	break;
	case 'main_author':
	if ( ! $post ) { break; }
	$author_id = get_post_field('post_author', $post->ID);
	if ($author_id) {
	$author_user = get_userdata($author_id);
	if ($author_user) {
	$contributors[] = $author_user;
	}
	}
	break;

🤖 Prompt for AI Agents

In assets/build/blocks/AdvanceContributors/render.php around lines 49 to 57, the
code accesses $post->ID without ensuring $post is non-null which will fatal in
non-singular contexts; update the case 'main_author' to first check that $post
is an object (e.g. if (!$post || !isset($post->ID)) return/continue or wrap the
block in if ($post && isset($post->ID)) { ... }), then retrieve post_author and
proceed as before; apply the same null-guard pattern to every other location in
this file that accesses $post->ID.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Box shadow keys mismatch (“x/y” vs “horizontal/vertical”)

This check requires ['x'] but block attributes provide ['horizontal'] and ['vertical']; shadow never applies.

Update to:

-        if (isset($controls['boxShadow']) && is_array($controls['boxShadow']) && isset($controls['boxShadow']['x'])) {
+        if (isset($controls['boxShadow']) && is_array($controls['boxShadow']) && isset($controls['boxShadow']['horizontal'])) {
             $shadow = $controls['boxShadow'];
             $shadow_value = '';
             if (isset($shadow['inset']) && $shadow['inset']) {
                 $shadow_value .= 'inset ';
             }
-            $shadow_value .= esc_attr($shadow['x']) . ' ';
-            $shadow_value .= esc_attr($shadow['y']) . ' ';
+            $shadow_value .= esc_attr($shadow['horizontal']) . ' ';
+            $shadow_value .= esc_attr($shadow['vertical']) . ' ';

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	// Box Shadow
	if (isset($controls['boxShadow']) && is_array($controls['boxShadow']) && isset($controls['boxShadow']['x'])) {
	$shadow = $controls['boxShadow'];
	$shadow_value = '';
	if (isset($shadow['inset']) && $shadow['inset']) {
	$shadow_value .= 'inset ';
	}
	$shadow_value .= esc_attr($shadow['x']) . ' ';
	$shadow_value .= esc_attr($shadow['y']) . ' ';
	$shadow_value .= esc_attr($shadow['blur']) . ' ';
	$shadow_value .= esc_attr($shadow['spread']) . ' ';
	$shadow_value .= esc_attr($shadow['color']);
	$rules[] = 'box-shadow: ' . $shadow_value;
	}
	// Box Shadow
	if (isset($controls['boxShadow']) && is_array($controls['boxShadow']) && isset($controls['boxShadow']['horizontal'])) {
	$shadow = $controls['boxShadow'];
	$shadow_value = '';
	if (isset($shadow['inset']) && $shadow['inset']) {
	$shadow_value .= 'inset ';
	}
	$shadow_value .= esc_attr($shadow['horizontal']) . ' ';
	$shadow_value .= esc_attr($shadow['vertical']) . ' ';
	$shadow_value .= esc_attr($shadow['blur']) . ' ';
	$shadow_value .= esc_attr($shadow['spread']) . ' ';
	$shadow_value .= esc_attr($shadow['color']);
	$rules[] = 'box-shadow: ' . $shadow_value;
	}

🤖 Prompt for AI Agents

In assets/build/blocks/AdvanceContributors/render.php around lines 229 to 242,
the box-shadow branch checks for shadow['x'] and shadow['y'] but the block
attributes provide horizontal/vertical keys, so the shadow never applies; update
the guard to check for horizontal/vertical (with fallbacks to x/y for backward
compatibility), read horizontal and vertical into local variables, then build
the shadow string using those values (preserving inset, blur, spread, color and
esc_attr usage) and only add the rule if horizontal/vertical (or their
fallbacks) are present.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Hide-class logic inverted; always hides on all devices

You append wedocs-hide-{device} when the device key exists (it always does), so the block is hidden across breakpoints.

Only add hide-class when display is explicitly 'none':

-    if (isset($display_controls['desktop']) && $display_controls['desktop']) {
+    if (isset($display_controls['desktop']['display']) && $display_controls['desktop']['display'] === 'none') {
         $display_classes[] = 'wedocs-hide-desktop';
     }
-    if (isset($display_controls['tablet']) && $display_controls['tablet']) {
+    if (isset($display_controls['tablet']['display']) && $display_controls['tablet']['display'] === 'none') {
         $display_classes[] = 'wedocs-hide-tablet';
     }
-    if (isset($display_controls['mobile']) && $display_controls['mobile']) {
+    if (isset($display_controls['mobile']['display']) && $display_controls['mobile']['display'] === 'none') {
         $display_classes[] = 'wedocs-hide-mobile';
     }

🤖 Prompt for AI Agents

In assets/build/blocks/AdvanceContributors/render.php around lines 333 to 345,
the current logic adds wedocs-hide-{device} whenever the device key exists
(which is always true), causing the block to be hidden on all devices; change
the checks so you only append the hide class when the display control for that
device is explicitly 'none' (e.g. isset($display_controls['desktop']) &&
$display_controls['desktop'] === 'none'), repeat for tablet and mobile, then
merge those classes into $css_classes as before.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Use children for Button label (avoid Button.text for compatibility).

Some versions of @wordpress/components don’t support the “text” prop on Button. Safer to pass children.

- <Button
+ <Button
     __next40pxDefaultSize
     variant="secondary"
     isDestructive
-    text={__('Reset All', 'block-responsive')}
     style={{
       width: '100%',
       justifyContent: 'center',
       marginTop: '16px',
     }}
     onClick={() => {
       setAttributes({
         colorsControls: {
           ...colorsControls,
           [device]: {
             ...currentColors,
             textColor: undefined,
             backgroundColor: undefined,
             linkColor: undefined,
             linkHoverColor: undefined,
           },
         },
       });
     }}
   />
+ >
+   { __('Reset All', 'wedocs') }
+ </Button>

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	<Button
	__next40pxDefaultSize
	variant="secondary"
	isDestructive
	text={__('Reset All', 'block-responsive')}
	style={{
	width: '100%',
	justifyContent: 'center',
	marginTop: '16px',
	}}
	onClick={() => {
	setAttributes({
	colorsControls: {
	...colorsControls,
	[device]: {
	...currentColors,
	textColor: undefined,
	backgroundColor: undefined,
	linkColor: undefined,
	linkHoverColor: undefined,
	},
	},
	});
	}}
	/>
	</>
	<Button
	__next40pxDefaultSize
	variant="secondary"
	isDestructive
	style={{
	width: '100%',
	justifyContent: 'center',
	marginTop: '16px',
	}}
	onClick={() => {
	setAttributes({
	colorsControls: {
	...colorsControls,
	[device]: {
	...currentColors,
	textColor: undefined,
	backgroundColor: undefined,
	linkColor: undefined,
	linkHoverColor: undefined,
	},
	},
	});
	}}
	>
	{__('Reset All', 'block-responsive')}
	</Button>

🤖 Prompt for AI Agents

In src/blocks/TableOfContents/ColorsControls.js around lines 322 to 347, the
Button currently uses the text prop which some @wordpress/components versions
don't support; replace the text prop with a child node: remove text={__('Reset
All', 'block-responsive')} and instead place the __('Reset All',
'block-responsive') string as the Button's child content (keeping all other
props and the onClick handler unchanged) so the label is passed via children for
maximum compatibility.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Empty file with meaningless whitespace; implement like AdvanceContributors or remove entirely.

This file contains only whitespace but no actual code. For server-rendered blocks, you should either:

1. Implement it like src/blocks/AdvanceContributors/save.js (returning null with proper imports)
2. Remove the file entirely if not needed

The current whitespace-only content serves no purpose and creates inconsistency.

Apply this diff to implement the proper pattern:

-
-  
-	
+import { useBlockProps } from '@wordpress/block-editor';
+
+const Save = () => {
+	const blockProps = useBlockProps.save();
+
+	// Since this is a dynamic block that uses PHP rendering,
+	// we return null to let the server-side render function handle the output
+	return null;
+};
+
+export default Save;

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	import { useBlockProps } from '@wordpress/block-editor';
	const Save = () => {
	const blockProps = useBlockProps.save();
	// Since this is a dynamic block that uses PHP rendering,
	// we return null to let the server-side render function handle the output
	return null;
	};
	export default Save;

🤖 Prompt for AI Agents

In src/blocks/TableOfContents/save.js lines 1-3: the file currently contains
only whitespace; either remove the file or implement the server-rendered block
pattern used by src/blocks/AdvanceContributors/save.js — create a save.js that
imports React (if your linting requires it) and exports a default Save component
that returns null (i.e., server-rendered no-client-save), matching the project's
style and export conventions; ensure any required ESLint or module headers are
present.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

Fix CSS custom property typo

--list-item-sytle is misspelled; it prevents the custom color from working.

Apply:

- color: var(--list-item-sytle, inherit);
+ color: var(--list-item-style, inherit);

Run to find all occurrences and ensure consistency:

---

🏁 Script executed:

#!/bin/bash
rg -n --type=css --type=scss --type=js --type=php --no-ignore -S '\-\-list-item-sy?tle'

Length of output: 28

---

---

🏁 Script executed:

#!/bin/bash
# Search for the misspelled custom property across all file types
# Using rg without the problematic type specification
rg -n -S 'list-item-sy' --glob='*.scss' --glob='*.css' --glob='*.js' --glob='*.php'

Length of output: 82389

---

🏁 Script executed:

#!/bin/bash
# Also check the specific file mentioned in the review
cat src/blocks/TableOfContents/style.scss | grep -n 'list-item'

Length of output: 47

---

🏁 Script executed:

#!/bin/bash
# Search for both spellings to understand which is used
rg -n 'list-item-style' --glob='*.scss' --glob='*.css' --glob='*.js' --glob='*.php'

Length of output: 0

---

Fix CSS custom property typo in two locations

The custom property --list-item-sytle is misspelled (should be --list-item-style), preventing the custom color from being applied.

Apply the fix in:

1. src/blocks/TableOfContents/style.scss line 55:

- color: var(--list-item-sytle, inherit);
+ color: var(--list-item-style, inherit);

2. src/blocks/TableOfContents/edit.js line 154:

- "--list-item-sytle": containerBackgroundColor,
+ "--list-item-style": containerBackgroundColor,

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	a {
	text-decoration: none;
	color: var(--list-item-sytle, inherit);
	display: inline-block;
	a {
	text-decoration: none;
	color: var(--list-item-style, inherit);
	display: inline-block;

🤖 Prompt for AI Agents

In src/blocks/TableOfContents/style.scss around lines 53-56 and in
src/blocks/TableOfContents/edit.js at line 154, the CSS custom property name is
misspelled as --list-item-sytle; update both occurrences to --list-item-style so
the intended custom color is applied (search for the misspelled token and
replace it with the corrected property name in both files).

[coderabbitai]

Actionable comments posted: 20

Note

Due to the large number of review comments, Critical, Major severity comments were prioritized as inline comments.

♻️ Duplicate comments (43)

src/blocks/components/TabSystem.js (3)

3-3: Remove unused Spacer import.

The __experimentalSpacer as Spacer import is never used in this component.

🔎 Proposed fix

-import { Button, ButtonGroup, __experimentalSpacer as Spacer } from '@wordpress/components';
+import { Button, ButtonGroup } from '@wordpress/components';

---

21-38: Add accessibility attributes for tab navigation.

The tab navigation is missing essential ARIA attributes for screen reader support. The ButtonGroup should have role="tablist", and each Button should have role="tab", aria-selected, and aria-controls attributes.

🔎 Proposed fix

-				<ButtonGroup>
+				<ButtonGroup role="tablist" aria-label={__('Block Settings Tabs', 'wedocs')}>
 					{tabs.map(tab => (
 						<Button
 							key={tab.key}
 							variant={activeTab === tab.key ? 'primary' : 'secondary'}
 							onClick={() => setActiveTab(tab.key)}
+							role="tab"
+							id={`wedocs-tab-${tab.key}`}
+							aria-selected={activeTab === tab.key}
+							aria-controls={`wedocs-tabpanel-${tab.key}`}
 							style={{
 								marginRight: '4px',
 								display: 'flex',
 								alignItems: 'center',
 								gap: '4px'
 							}}
 						>

---

43-55: Fix children handling, duplicate keys, and add accessibility attributes.

Three critical issues:

1. Runtime error: children.map will break when a single child is passed (React children can be an object, not an array).
2. Duplicate keys: All children after the first get key="style", causing React reconciliation issues.
3. Missing accessibility: Tab panels need role="tabpanel", aria-labelledby, and corresponding id attributes.

🔎 Proposed fix

First, import Children from React:

-import { useState } from '@wordpress/element';
+import { useState, Children } from '@wordpress/element';

Then fix the content rendering:

 			{/* Tab Content */}
 			<div className="tab-content">
-				{children.map((child, index) => {
-					const tabKey = index === 0 ? 'setup' : 'style';
-					return (
-						<div
-							key={tabKey}
-							style={{
-								display: activeTab === tabKey ? 'block' : 'none'
-							}}
-						>
-							{child}
-						</div>
-					);
-				})}
+				{Children.toArray(children).map((child, index) => {
+					const tabKey = index === 0 ? 'setup' : 'style';
+					return (
+						<div
+							key={`${tabKey}-${index}`}
+							id={`wedocs-tabpanel-${tabKey}`}
+							role="tabpanel"
+							aria-labelledby={`wedocs-tab-${tabKey}`}
+							style={{
+								display: activeTab === tabKey ? 'block' : 'none'
+							}}
+						>
+							{child}
+						</div>
+					);
+				})}
 			</div>

src/blocks/TableOfContents/save.js (1)

1-3: The empty file issue from the previous review remains unresolved.

As noted in the previous review, this file contains only whitespace and serves no purpose. For server-rendered blocks, you should either implement it properly (returning null with proper imports like AdvanceContributors/save.js) or remove the file entirely.

assets/build/style-block-rtl.css (1)

1-1: Fix duplicate width property in source CSS.

A duplicate width property declaration exists in the selector .wedocs-search-input,.wedocs-editor-search-input. Since this is a build artifact, the issue should be resolved in the source CSS file before rebuilding.

🧰 Tools

🪛 Biome (2.1.2)

[error] 1-1: Duplicate properties can lead to unexpected behavior and may override previous declarations unintentionally.

Remove or rename the duplicate property to ensure consistent styling.

(lint/suspicious/noDuplicateProperties)

assets/build/block.js (1)

1-1: Address CSS custom property issue in TableOfContents source.

A previous review identified a typo and incorrect variable binding in the TableOfContents block source (src/blocks/TableOfContents/edit.js line 154). Since this is a build artifact, fix the source and rebuild.

src/blocks/Contributors/edit-old.js (1)

151-161: Preview ignores configured date format settings.

The date preview uses a hardcoded toLocaleDateString format and ignores the dateFormat and customDateFormat attributes that users can configure. This creates a mismatch between editor preview and frontend output.

Since PHP date format strings are specified in the help text, consider either:

1. Using @wordpress/date utilities with format conversion
2. Rendering a placeholder indicating the format will apply on frontend

src/blocks/AdvanceContributors/edit-old.js (2)

51-65: Replace wp.apiFetch with imported @wordpress/api-fetch.

This was flagged in a previous review. For bundled code, import apiFetch directly for better tree-shaking and explicit dependency management.

---

151-161: Date format preview ignores user settings.

This was flagged in a previous review. The preview hardcodes toLocaleDateString and ignores dateFormat/customDateFormat attributes.

assets/build/blocks/DocsGrid/index.asset.php (1)

1-1: Existing critical issue with react-jsx-runtime dependency already flagged.

The incompatibility between the react-jsx-runtime dependency (requires WP 6.6+) and the plugin's minimum WordPress requirement (5.6+) has already been identified in a previous review comment. Please address that issue before merging.

includes/Assets.php (1)

85-89: Critical: Style handle enqueued without registration (duplicate issue).

The wedocs-block-style registration remains commented out (lines 85-89), but the style is still enqueued at lines 129 and 155. This is the same critical issue flagged in the previous review and must be resolved.

Apply one of the fixes from the previous review:

Option 1: Uncomment and fix the registration:

🔎 Restore registration

-            // wp_register_style(
-            //     'wedocs-block-style',
-            //     $assets_url . '/build/style-block.css',
-            //     $block_dependencies['version']
-            // );
+            wp_register_style(
+                'wedocs-block-style',
+                $assets_url . '/build/style-block.css',
+                array(),
+                $block_dependencies['version']
+            );

Option 2: Remove all enqueue calls:

🔎 Remove enqueue calls

-        wp_enqueue_style( 'wedocs-block-style' );

And in admin_enqueue:

     public function admin_enqueue() {
-        wp_enqueue_style( 'wedocs-block-style' );
-
         // Enqueue admin script.

Also applies to: 129-129, 155-155

src/blocks/TableOfContents/controls/ListItems.js (1)

7-16: Critical: Undefined variable reference (duplicate issue).

The component uses containerBackgroundColor on line 14 without defining it. This is the same critical issue from the previous review and will cause a ReferenceError at runtime.

Apply one of the fixes from the previous review:

Option 1: Destructure from attributes:

🔎 Destructure the variable

 const ListItems = ({ attributes, setAttributes }) => {
+    const { containerBackgroundColor } = attributes;
+    
     return (
         <PanelBody title={__('List Items', 'dynamic-table-of-contents-block-wp')} initialOpen={false}>

Option 2: Access via attributes:

🔎 Use attributes.containerBackgroundColor

             <div style={{ marginBottom: '20px' }}>
                 <label>{__('Background Color', 'dynamic-table-of-contents-block-wp')}</label>
                 <ColorPicker
-                    color={containerBackgroundColor}
+                    color={attributes.containerBackgroundColor}
                     onChange={(value) => setAttributes({ containerBackgroundColor: value })}
                 />

assets/build/blocks/TableOfContents/style-index.css (1)

1-1: Accessibility issue: Loading message in CSS pseudo-element (previously flagged).

As noted in the previous review, the .toc-loading .toc-content:after rule renders "Loading headings..." via a CSS pseudo-element, which is not accessible to screen readers. This loading message should be moved to the DOM with role="status" or aria-live="polite" to ensure it's announced by assistive technologies.

assets/build/blocks/TableOfContents/style-index-rtl.css (1)

1-1: Accessibility issue: Loading message in CSS pseudo-element (previously flagged in RTL variant).

The same accessibility issue noted in the LTR version applies here: the loading message in .toc-loading .toc-content:after should be moved to the DOM with appropriate ARIA attributes for screen reader support.

assets/build/store.js (1)

1-1: Static analysis errors remain unaddressed.

The unsafe optional chaining and switch clause issues flagged by static analysis are still present in this build artifact. These were previously identified in the source files (src/data/docs/reducer.js around lines 84-85). The source must be fixed and the bundle rebuilt.

src/blocks/TableOfContents/ColorsControls.js (3)

17-20: Undefined colorsControls will crash the component.

The destructuring of colorsControls without a default value and immediate access to colorsControls[device] will throw a TypeError if attributes.colorsControls is undefined.

---

53-53: Incorrect text domain breaks translations.

The text domain 'block-responsive' should be 'wedocs' to match this plugin's translation infrastructure. This issue appears throughout the file at multiple locations.

Also applies to: 68-68, 108-108, 122-122, 135-135, 158-158, 174-174, 229-229, 243-243, 257-257, 280-280, 293-293, 326-326

---

322-347: Button.text prop may not be supported in all versions.

Using the text prop on Button can cause compatibility issues with some versions of @wordpress/components. The label should be passed as children instead.

src/blocks/commonControls/TypographyControls.js (1)

28-30: Undefined typographyControls will crash the component.

Destructuring without a default and accessing typographyControls[device] will throw if attributes.typographyControls is undefined.

src/blocks/commonControls/AlignmentControls.js (2)

26-28: Guard against undefined alignmentControls to avoid runtime errors

attributes.alignmentControls may be undefined; accessing alignmentControls[device] will throw. This was flagged in a previous review.

🔎 Proposed fix

 const AlignmentControls = ({ attributes, setAttributes, device }) => {
-	const { alignmentControls } = attributes;
-	const currentAlignment = alignmentControls[device] || {};
+	const { alignmentControls = {} } = attributes;
+	const currentAlignment = alignmentControls[device] || {};

---

161-165: Invalid CSS value for alignItems: "space-between" is not valid

align-items does not accept space-between; that's a justify-content value. This will produce invalid CSS. This was flagged in a previous review.

🔎 Proposed fix

 <ToggleGroupControlOptionIcon
-	value="space-between"
-	label={__('Space between', 'wedocs')}
+	value="stretch"
+	label={__('Stretch', 'wedocs')}
 	icon={justifyStretchVertical}
 />

assets/build/blocks/DocsGrid/render.php (1)

74-82: Guard against non-array padding/margin inputs

If $grid_padding is not an array, accessing ['top'] etc. will emit "Illegal string offset" notices. This was flagged in a previous review.

🔎 Proposed fix

-        if ($grid_padding) {
+        if ( is_array( $grid_padding ) ) {
             $padding_style = sprintf(
                 'padding: %s %s %s %s;',
                 esc_attr($grid_padding['top'] ?? '1.5rem'),

Apply the same pattern to $grid_margin, $button_padding, and $button_margin checks.

src/blocks/commonControls/DisplayControls.js (2)

50-57: Guard against undefined displayControls

If attributes.displayControls is undefined, line 53-54 and line 61 will throw runtime errors. This was flagged in a previous review.

🔎 Proposed fix

 const toggleDeviceVisibility = (deviceKey) => {
+	const current = attributes.displayControls || {};
 	setAttributes({
 		displayControls: {
-			...attributes.displayControls,
-			[deviceKey]: !attributes.displayControls[deviceKey],
+			...current,
+			[deviceKey]: !current[deviceKey],
 		},
 	});
 };

 // Render individual device control card
 const renderDeviceCard = ({ key, icon, label }) => {
-	const isHidden = attributes.displayControls[key];
+	const isHidden = attributes.displayControls?.[key];

Also applies to: 61-61

---

76-80: Add aria-label for accessibility

The toggle button displays only an icon, making it inaccessible to screen reader users. This was flagged in a previous review.

🔎 Proposed fix

 <Button
 	__next40pxDefaultSize
 	onClick={() => toggleDeviceVisibility(key)}
 	icon={isHidden ? unseen : seen}
+	aria-label={
+		isHidden
+			? __('Show on', 'wedocs') + ' ' + key
+			: __('Hide on', 'wedocs') + ' ' + key
+	}
 />

src/blocks/Contributors/render.php (5)

100-106: Wrong API for retrieving contributors - uses get_post_field instead of post meta

get_post_field('wedocs_contributors', ...) reads a posts table column, not post meta. For main_author case, this should use post_author field. This was flagged in a previous review.

🔎 Proposed fix

         case 'main_author':
-            $author_id = get_post_field('wedocs_contributors', $post->ID);
+            if ( ! $post ) { break; }
+            $author_id = get_post_field('post_author', $post->ID);
             if ($author_id) {
                 $contributors[] = get_userdata($author_id);
             }
             break;

---

120-131: Invalid contributor retrieval in 'all' case

get_post_field('wedocs_contributors', ...) returns a string column, not post meta. Calling array_values() on it produces an array of characters, causing incorrect behavior. This was flagged in a previous review.

🔎 Proposed fix

         case 'all':
         default:
             // Get all contributors who have edited the post
-            $author_id = get_post_field('wedocs_contributors', $post->ID);
-            $authors = array_values($author_id); // return auhtors id.
-            foreach($authors as $author){
-                $contributors[]= get_userdata($author);
-            }
-
-
-            if ($author_id && ($author_user = get_userdata($author_id))) {
-                $contributors[] = $author_user;
-            }
+            // Include post author first
+            $post_author_id = $post ? (int) get_post_field('post_author', $post->ID) : 0;
+            if ( $post_author_id && ($author_user = get_userdata($post_author_id)) ) {
+                $contributors[] = $author_user;
+            }
+
+            // Get contributors from post meta
+            $author_ids = (array) get_post_meta($post->ID, 'wedocs_contributors', true);
+            foreach ( $author_ids as $uid ) {
+                if ( $user = get_userdata( (int) $uid ) ) {
+                    $contributors[] = $user;
+                }
+            }

---

156-165: Demo fallback should not render in production

This creates a fake "Demo Author" user on production sites when no contributors are found. This was flagged in a previous review.

🔎 Proposed fix

-        if (empty($contributors)) {
-            // For demo purposes, add mock contributors if none found
-            $contributors = [
-                (object) [
-                    'ID' => 1,
-                    'display_name' => 'Demo Author',
-                    'user_email' => 'demo@example.com'
-                ]
-            ];
-        }
+        if (empty($contributors)) {
+            return '';
+        }

---

395-395: Return markup instead of echoing

Block render callbacks should return the output string, not echo it. Echoing can cause misplaced output. This was flagged in a previous review.

🔎 Proposed fix

-    echo render_wedocs_contributors_block($attributes, $content, $block);
+    return render_wedocs_contributors_block($attributes, $content, $block);
 }

Note: The echo should be moved outside the function_exists block and removed entirely since the function already returns the output.

---

153-154: De-duplicate contributors list

array_filter removes nulls but doesn't prevent duplicate users (e.g., if post author also appears in revisions). This was flagged in a previous review.

🔎 Proposed fix

         // Filter out invalid contributors
-        $contributors = array_filter($contributors);
+        $contributors = array_filter($contributors);
+        // De-duplicate by user ID
+        $contributors = array_values(array_reduce($contributors, function($acc, $u) {
+            if (is_object($u) && isset($u->ID)) {
+                $acc[$u->ID] = $u;
+            }
+            return $acc;
+        }, []));

assets/build/blocks/AdvanceContributors/render.php (4)

49-57: Critical: Unsafe $post property access without null check.

Lines 50 and 73 access $post->ID without verifying that $post is not null. This will cause a fatal error in non-singular contexts (archives, previews, etc.).

🔎 Required fix

 case 'main_author':
+	if (!$post) { break; }
 	$author_id = get_post_field('post_author', $post->ID);

Apply the same null guard at Line 73 and anywhere else $post->ID is accessed.

Based on past review comments.

---

229-242: Major: Box shadow key mismatch prevents shadows from rendering.

Line 230 checks for $shadow['x'] but the block attributes schema (block.json lines 284-290) provides 'horizontal' and 'vertical' keys. This mismatch means box shadows will never apply.

🔎 Required fix

-if (isset($controls['boxShadow']) && is_array($controls['boxShadow']) && isset($controls['boxShadow']['x'])) {
+if (isset($controls['boxShadow']) && is_array($controls['boxShadow']) && isset($controls['boxShadow']['horizontal'])) {
 	$shadow = $controls['boxShadow'];
 	$shadow_value = '';
 	if (isset($shadow['inset']) && $shadow['inset']) {
 		$shadow_value .= 'inset ';
 	}
-	$shadow_value .= esc_attr($shadow['x']) . ' ';
-	$shadow_value .= esc_attr($shadow['y']) . ' ';
+	$shadow_value .= esc_attr($shadow['horizontal']) . ' ';
+	$shadow_value .= esc_attr($shadow['vertical']) . ' ';

Based on past review comments.

---

333-345: Critical: Inverted hide-class logic hides block on all devices.

Lines 335-342 add wedocs-hide-{device} classes whenever the device key exists (which is always true per the schema defaults), causing the block to be hidden across all breakpoints.

🔎 Required fix

Only add hide classes when display is explicitly set to 'none':

-if (isset($display_controls['desktop']) && $display_controls['desktop']) {
+if (isset($display_controls['desktop']['display']) && $display_controls['desktop']['display'] === 'none') {
 	$display_classes[] = 'wedocs-hide-desktop';
 }
-if (isset($display_controls['tablet']) && $display_controls['tablet']) {
+if (isset($display_controls['tablet']['display']) && $display_controls['tablet']['display'] === 'none') {
 	$display_classes[] = 'wedocs-hide-tablet';
 }
-if (isset($display_controls['mobile']) && $display_controls['mobile']) {
+if (isset($display_controls['mobile']['display']) && $display_controls['mobile']['display'] === 'none') {
 	$display_classes[] = 'wedocs-hide-mobile';
 }

Based on past review comments.

---

497-499: Critical: Render file must return the generated HTML.

Line 499 calls the render function but doesn't return its output to WordPress, resulting in empty block output on the frontend.

🔎 Required fix

 	return $output;
 }
-render_wedocs_advance_contributors_block( $attributes, $content, $block );
+return render_wedocs_advance_contributors_block( $attributes, $content, $block );

Based on past review comments.

assets/build/blocks/AdvanceContributors/block.json (1)

284-291: Schema mismatch with render.php for box shadow.

The block.json schema correctly defines box shadow with "horizontal" and "vertical" keys, but the render.php file (Line 230) checks for "x" and "y", causing shadows to never render.

The fix should be applied in render.php to match this schema. See the review comment on render.php lines 229-242.

Based on past review comments.

assets/build/blocks/TableOfContents/index.js (1)

1-1: Reconsider committing minified build artifacts to the repository.

This is generated build output that should not be committed to version control. See the previous comment on assets/build/blocks/AdvanceContributors/index.js for the same rationale.

src/blocks/commonControls/DimensionsControls.js (3)

11-14: Guard against undefined dimensionsControls to prevent runtime errors.

dimensionsControls may be undefined, causing dimensionsControls[device] to throw a runtime error.

🔎 Proposed fix

-const DimensionsControls = ({ attributes, setAttributes, device }) => {
-	const { dimensionsControls } = attributes;
-	const currentDimensions = dimensionsControls[device] || {};
+const DimensionsControls = ({ attributes, setAttributes, device }) => {
+	const { dimensionsControls = {} } = attributes;
+	const currentDimensions = dimensionsControls[device] || {};

Based on past review comments.

---

15-28: Guard nested object spreads to prevent runtime errors.

Spreading currentDimensions.padding will throw if padding is undefined.

🔎 Proposed fix

 const handlePaddingChange = (value) => {
 	const newDimensionsControls = {
 		...dimensionsControls,
 		[device]: {
 			...currentDimensions,
 			padding: {
-				...currentDimensions.padding,
+				...(currentDimensions.padding ?? {}),
 				...value,
 			},
 		},
 	};
 
 	setAttributes({ dimensionsControls: newDimensionsControls });
 };

Apply the same pattern to handleMarginChange (lines 30-43) and handleBlockSpacingChange (lines 45-58).

Based on past review comments.

---

69-74: Replace -Infinity with a supported numeric value.

Gutenberg's SpacingSizesControl expects a finite number for minimumCustomValue. Using -Infinity is not supported and may break UI validation.

🔎 Proposed fix

 <SpacingSizesControl
 	values={currentDimensions.margin || {}}
 	onChange={handleMarginChange}
 	label={__('Margin', 'wedocs')}
-	minimumCustomValue={-Infinity}
+	minimumCustomValue={-1000}
 />

Alternatively, omit the prop to use the component's default minimum value.

Based on past review comments.

src/blocks/TableOfContents/style.scss (1)

53-56: Fix CSS custom property typo.

The custom property name is misspelled as --list-item-sytle (should be --list-item-style), which prevents the custom color from being applied.

🔎 Proposed fix

 a {
 	text-decoration: none;
-	color: var(--list-item-sytle, inherit);
+	color: var(--list-item-style, inherit);
 	display: inline-block;
 	transition: color 0.2s ease;

Note: According to past review comments, this typo also appears in the corresponding edit.js file where the CSS variable is set. Ensure both locations are fixed for consistency.

Based on past review comments.

src/blocks/commonControls/ColorsControls.js (1)

17-19: Add missing device prop to function signature.

The component references device on line 19 but doesn't receive it as a prop, causing colorsControls[device] to be undefined.

🔎 Proposed fix

-const ColorsControls = ({ attributes, setAttributes, isTextColor = false, isBackgroundColor = false, isLinkColor = false }) => {
-	const { colorsControls } = attributes;
+const ColorsControls = ({ attributes, setAttributes, device, isTextColor = false, isBackgroundColor = false, isLinkColor = false }) => {
+	const { colorsControls = {} } = attributes;
 	const currentColors = colorsControls[device] || {};

Additionally, consider providing a default value for device (e.g., device = 'desktop') if it's optional.

Based on past review comments.

src/blocks/commonControls/BackgroundImageControls.js (1)

164-182: UnitControl: "auto" is invalid for __experimentalUnitControl.

__experimentalUnitControl expects a numeric value with unit. Passing "auto" will cause validation issues. Use empty string and add explicit units.

This was flagged in a previous review. The fix should use an empty string as the default and define allowed units:

 <UnitControl
     __next40pxDefaultSize
-    value={currentBackgroundImage.bgWidth || 'auto'}
+    value={currentBackgroundImage.bgWidth ?? ''}
+    units={[
+        { value: 'px', label: 'px' },
+        { value: '%', label: '%' },
+    ]}
     disabled={currentBackgroundImage.bgSize !== 'tile'}
     onChange={(value) => { ... }}
     placeholder={__('Auto', 'wedocs')}
 />

src/blocks/helpers/block-styles.php (2)

58-70: CSS value sanitization function exists but is not used.

The wedocs_sanitize_css_value() function (lines 290-312) provides proper CSS value sanitization, but wedocs_build_spacing_styles() uses only esc_attr() which doesn't validate CSS units. This was previously flagged and the sanitization function was added, but integration is incomplete.

The fix from the past review should be applied here to use wedocs_sanitize_css_value() for padding/margin values.

---

81-101: Border style and radius values lack proper sanitization.

This segment uses esc_attr() for CSS values but doesn't validate against allowed units. The wedocs_sanitize_css_value() function exists but isn't used here.

🟡 Minor comments (21)

readme.md-23-39 (1)

23-39: Clarify the purpose and placement of the Mozart configuration block.

This commented-out configuration block appears to be for the Mozart dependency system, but it's unclear why this needs to be in a README file. Additionally, the namespace (WPMUDEV_PluginTest) and classmap prefix suggest this may be example or copied configuration, not specific to weDocs.

Consider:

• Moving actual configuration to proper config files (e.g., composer.json or a dedicated Mozart config file)
• If this is documentation, provide context explaining what Mozart is and why weDocs uses it
• Removing the commented block if it's example code that's not relevant to this project

src/blocks/components/SpacingControl.js-73-85 (1)

73-85: Fallback logic may override intentional '0px' gap values.

The expression gapValue || '10px' on Line 77 will default to '10px' for any falsy value, including '0px', 0, or ''. If a developer explicitly wants to set the gap to zero, this fallback will prevent it.

🔎 Proposed fix using nullish coalescing

 			<UnitControl
 				label={__('Gap', 'wedocs')}
-				value={gapValue || '10px'}
+				value={gapValue ?? '10px'}
 				onChange={onGapChange}
 				units={[
 					{ value: 'px', label: 'px' },

This ensures only null or undefined trigger the default, allowing explicit '0px' or 0 values.

src/blocks/components/SpacingControl.js-1-7 (1)

1-7: Update imports to use stable BoxControl and UnitControl exports.

__experimentalBoxControl and __experimentalUnitControl were promoted to stable APIs (BoxControl and UnitControl) in WordPress 6.7/6.8. Update the imports to:

import { BoxControl, UnitControl } from '@wordpress/components';

The __experimentalSpacer import should remain as-is, as Spacer has not been stabilized yet.

src/blocks/commonControls/BorderAndShadowControls.js-215-237 (1)

215-237: Inconsistent reset values for different properties.

The reset operation uses different values for each property:

• border: {} (empty object)
• borderRadius: null (null)
• boxShadow: {} (empty object)

While this works due to the fallback logic on line 97, the inconsistency could confuse maintainers.

🔎 Suggested fix for consistency

 				onClick={() => {
 					setAttributes({
 						borderAndShadowControls: {
 							...borderAndShadowControls,
 							[device]: {
 								...currentBorderAndShadow,
-								border: {},
-								borderRadius: null,
-								boxShadow: {},
+								border: undefined,
+								borderRadius: undefined,
+								boxShadow: undefined,
 							},
 						},
 					});

Or consistently use empty objects:

-								borderRadius: null,
+								borderRadius: {},

assets/build/print-rtl.css-141-144 (1)

141-144: Duplicate selector a:not(.anchorjs-link)::after.

The same selector appears twice on consecutive lines. This is likely a copy-paste error.

🔎 Proposed fix

-a:not(.anchorjs-link)::after,
-a:not(.anchorjs-link)::after {
+a:not(.anchorjs-link)::after {
   content: ' (' attr(href) ')';
 }

src/blocks/helpers/block-helpers.js-374-389 (1)

374-389: isBreakpoint will throw in SSR/Node environments.

Direct access to window.innerWidth without a guard will cause a ReferenceError during server-side rendering or testing in Node. Add a check for window existence.

🔎 Proposed fix

 export const isBreakpoint = (breakpoint) => {
+	if (typeof window === 'undefined') {
+		return false;
+	}
 	const breakpoints = getBreakpoints();
 	const width = window.innerWidth;

assets/build/print-rtl.css-55-62 (1)

55-62: Duplicate font-size declarations in the same rule.

font-size is declared twice (line 55: 18px, line 62: 15px). The second declaration overrides the first, making line 55 dead code. If 15px is the intended size, remove line 55.

🔎 Proposed fix

 .entry-content dl dt {
   float: right;
   display: inline-block;
   font-weight: 400;
   text-align: center;
   padding: 4px 9px;
   margin-bottom: 1em;
-  font-size: 18px;
   line-height: 1.2em;
   border-radius: 50px;
   color: #fff;
   background: #3197d1;
   vertical-align: baseline;
   white-space: nowrap;
   font-size: 15px;

src/blocks/TableOfContents/index.js-29-34 (1)

29-34: Add save: () => null to the block registration.

The block registration is missing the save property. Based on the pattern used in Contributors and AdvanceContributors blocks (which also use server-side rendering via render.php), add:

save: () => null,

This indicates that the block content is rendered server-side rather than stored in the database.

src/blocks/commonControls/TypographyControls.js-244-271 (1)

244-271: Use children for Button label instead of text prop.

The text prop on Button may not be supported in all versions of @wordpress/components. Pass the label as children for better compatibility.

🔎 Proposed fix

 <Button
 	__next40pxDefaultSize
 	variant="secondary"
 	isDestructive
-	text={__('Reset All', 'wedocs')}
 	style={{
 		width: '100%',
 		justifyContent: 'center',
 		marginTop: '16px',
 	}}
 	onClick={() => {
 		setAttributes({
 			typographyControls: {
 				...typographyControls,
 				[device]: {
 					...currentTypography,
 					fontFamily: null,
 					fontSize: null,
 					fontAppearance: null,
 					lineHeight: null,
 					letterSpacing: null,
 					textDecoration: null,
 					textTransform: null,
 				},
 			},
 		});
 	}}
-/>
+>
+	{__('Reset All', 'wedocs')}
+</Button>

src/blocks/Contributors/render.php-332-332 (1)

332-332: Use wp_date() instead of date() for timezone-aware formatting

date() doesn't respect WordPress timezone settings. Use wp_date() for consistent timezone handling.

🔎 Proposed fix

-            $last_modified = $post ? get_the_modified_date($date_format_string, $post) : date($date_format_string);
+            $last_modified = $post ? get_the_modified_date($date_format_string, $post) : wp_date($date_format_string);

src/blocks/Contributors/edit.js-323-327 (1)

323-327: Hardcoded date format in preview.

The preview always uses 'en-US' locale and a specific format, ignoring the attributes.dateFormat and attributes.customDateFormat settings. This creates a mismatch between the editor preview and the actual rendered output.

Consider using the configured date format settings to make the preview more accurate, or add a comment explaining this is a simplified preview.

assets/build/frontend-rtl.css-508-515 (1)

508-515: Remove duplicate font-size declaration.

Line 508 declares font-size: 18px and line 515 declares font-size: 15px for the same selector. This creates ambiguity about which size should be applied.

🔎 Proposed fix

   padding: 4px 9px;
   margin-bottom: 1em;
-  font-size: 18px;
   line-height: 1.2em;
   border-radius: 50px;
   color: #fff;
   background: #3197d1;
   vertical-align: baseline;
   white-space: nowrap;
   font-size: 15px;

src/blocks/AdvanceContributors/render.php-454-454 (1)

454-454: Incorrect date fallback when post is unavailable.

Line 454 uses date($date_format_string) as fallback when $post is unavailable, which returns the current date/time rather than a meaningful post date. Consider omitting the date section entirely when the post is unavailable.

🔎 Proposed fix

-        $last_modified = $post ? get_the_modified_date($date_format_string, $post) : date($date_format_string);
+        $last_modified = $post ? get_the_modified_date($date_format_string, $post) : '';
+        
+        if (!$last_modified) {
+            // Skip rendering date if post is unavailable
+            $show_last_updated = false;
+        }

Committable suggestion skipped: line range outside the PR's diff.

src/blocks/DocsGrid/render.php-183-184 (1)

183-184: Unused variable $total_pages and missing pagination rendering.

$total_pages is computed but never used. The get_pagination_style_tag function exists but pagination UI is not rendered. Either implement pagination or remove the unused code.

Also applies to: 207-212

src/blocks/TableOfContents/edit.js-113-113 (1)

113-113: Potential negative indent when h1 is included in supportedHeadings.

The counters object starts at level 2, and indent calculation (heading.level - 2) * 20 produces negative values for h1. If h1 is supported, this could cause layout issues.

🔎 Proposed fix

-		let counter = 1;
-		const counters = { 2: 0, 3: 0, 4: 0, 5: 0 };
+		let counter = 1;
+		const counters = { 1: 0, 2: 0, 3: 0, 4: 0, 5: 0 };

And for indent:

-				const indent = showHierarchy ? (heading.level - 2) * 20 : 0;
+				const indent = showHierarchy ? Math.max(0, (heading.level - 1) * 20) : 0;

Also applies to: 130-130

assets/build/blocks/Contributors/render.php-332-332 (1)

332-332: Use wp_date() instead of date() for WordPress timezone handling.

date() uses server timezone, not the WordPress configured timezone. Use wp_date() for consistency with WordPress settings.

🔎 Proposed fix

-            $last_modified = $post ? get_the_modified_date($date_format_string, $post) : date($date_format_string);
+            $last_modified = $post ? get_the_modified_date($date_format_string, $post) : wp_date($date_format_string);

src/blocks/TableOfContents/edit.js-154-154 (1)

154-154: Fix typo in CSS variable name: --list-item-sytle → --list-item-style.

This typo will cause the CSS variable to not match any references expecting --list-item-style.

🔎 Proposed fix

         style: {
-            "--list-item-sytle": containerBackgroundColor,
+            "--list-item-style": containerBackgroundColor,

src/blocks/DocsGrid/render.php-176-178 (1)

176-178: Use integer -1 instead of string '-1' for posts_per_page.

WP_Query expects an integer for posts_per_page. Using a string may cause unexpected behavior.

🔎 Proposed fix

         } else {
-            $args['posts_per_page'] = '-1';
+            $args['posts_per_page'] = -1;
             $args['paged'] = 1;
         }

src/blocks/AdvanceContributors/edit.js-286-290 (1)

286-290: Avoid Math.random() as React key.

Using Math.random() for keys (line 289 fallback) causes React to unmount and remount components on every render, degrading performance and breaking state.

🔎 Suggested fix

-						const contributorId = contributor.id || contributor.ID || Math.random();
+						const contributorId = contributor.id || contributor.ID || `fallback-${index}`;

Note: This requires adding index parameter to the .map() callback.

Committable suggestion skipped: line range outside the PR's diff.

src/blocks/helpers/block-styles.php-222-225 (1)

222-225: Custom styles are merged without validation.

The $args['custom'] array is directly merged into styles without any sanitization. If this array contains user-controlled values, it could allow CSS injection.

🔎 Suggested fix

     // Custom styles
     if (isset($args['custom']) && is_array($args['custom'])) {
-        $styles = array_merge($styles, $args['custom']);
+        $sanitized_custom = array_map('sanitize_text_field', $args['custom']);
+        $styles = array_merge($styles, $sanitized_custom);
     }

package.json-30-30 (1)

30-30: Test the build thoroughly after upgrading @wordpress/scripts to v30.

The upgrade from @wordpress/scripts v25 to v30.15.0 includes changes to webpack, Babel, and ESLint presets. Review the changelog for breaking changes specific to your setup, run your build scripts, and verify that blocks render correctly in WordPress. The version of @wordpress/block-editor does not need to be bumped solely based on this upgrade—WordPress packages use a dist-tag strategy (e.g., @wordpress/block-editor@wp-6.x) for version coordination rather than strict pinning.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash

echo "=== Checking for build artifacts in assets/build/ ==="
if [ -d assets/build ]; then
    find assets/build -type f | head -20
else
    echo "assets/build/ directory not found"
fi

echo -e "\n=== Checking git status of assets/build/ ==="
git ls-files assets/build/ 2>/dev/null | head -20 || echo "No git-tracked files in assets/build/"

echo -e "\n=== Checking .gitignore for build directory exclusions ==="
if [ -f .gitignore ]; then
    echo "=== Full .gitignore content ==="
    cat -n .gitignore
    echo ""
    echo "=== Patterns matching 'build' or 'assets' ==="
    grep -n "build\|dist\|assets" .gitignore || echo "No matching patterns found"
else
    echo ".gitignore file not found"
fi

echo -e "\n=== Checking for build-related files (package.json, etc.) ==="
if [ -f package.json ]; then
    echo "=== package.json found, checking for build scripts ==="
    head -50 package.json
fi

echo -e "\n=== Git status overview for assets/build/ ==="
git status assets/build/ 2>/dev/null || echo "Git status check failed"

Repository: weDevsOfficial/wedocs-plugin

Length of output: 4514

---

Remove build artifacts from version control and add assets/build/ to .gitignore.

The assets/build/ directory contains auto-generated files created by wp-scripts build and is currently tracked in git. These artifacts should not be committed because they:

• Cause merge conflicts when multiple developers build locally
• Bloat the repository with auto-generated content
• Create unnecessary churn in the version history

Add assets/build/ to .gitignore and regenerate these assets during the build/deployment process (e.g., via the npm run build or npm run release scripts).

🤖 Prompt for AI Agents

In assets/build/blocks/AdvanceContributors/index.asset.php at line 1, a
generated build artifact is committed; remove all files under assets/build/ from
version control and add assets/build/ to .gitignore so generated assets aren’t
tracked. Specifically: delete the committed assets/build/ files from the repo
(git rm --cached or remove and commit), add an entry "assets/build/" to
.gitignore, and ensure the build step (npm run build/release) generates these
files during CI or deployment instead of committing them.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Compare LTR and RTL versions to verify they're different

echo "=== Comparing AdvanceContributors LTR and RTL files ==="
if [ -f assets/build/blocks/AdvanceContributors/style-index.css ] && [ -f assets/build/blocks/AdvanceContributors/style-index-rtl.css ]; then
  echo "File sizes:"
  wc -c assets/build/blocks/AdvanceContributors/style-index*.css
  echo ""
  echo "Diff output (first 50 lines):"
  diff assets/build/blocks/AdvanceContributors/style-index.css assets/build/blocks/AdvanceContributors/style-index-rtl.css | head -50
else
  echo "Files not found - listing directory:"
  find assets/build/blocks/AdvanceContributors -type f -name "*.css" 2>/dev/null || echo "Directory not found"
fi

echo ""
echo "=== Checking for RTL-specific properties in AdvanceContributors RTL file ==="
if [ -f assets/build/blocks/AdvanceContributors/style-index-rtl.css ]; then
  echo "Searching for directional properties:"
  grep -o "padding-right\|border-right\|margin-right\|float" assets/build/blocks/AdvanceContributors/style-index-rtl.css | sort | uniq -c
else
  echo "RTL file not found"
fi

echo ""
echo "=== Checking TableOfContents RTL file for reference ==="
if [ -f assets/build/blocks/TableOfContents/style-index-rtl.css ]; then
  echo "Size of TableOfContents RTL file:"
  wc -c assets/build/blocks/TableOfContents/style-index-rtl.css
  echo ""
  echo "Searching for directional properties in TableOfContents RTL:"
  grep -o "padding-right\|border-right\|margin-right\|float" assets/build/blocks/TableOfContents/style-index-rtl.css | head -10
else
  echo "TableOfContents RTL file not found"
fi

Repository: weDevsOfficial/wedocs-plugin

Length of output: 684

---

RTL stylesheet is identical to LTR version and missing directional adjustments.

The style-index-rtl.css file is byte-for-byte identical to style-index.css (both 3204 bytes with no differences). RTL stylesheets require directional properties adjustments such as:

• padding-right instead of padding-left (and vice versa)
• border-right instead of border-left
• margin-right instead of margin-left
• Adjusted float and text-align values

The TableOfContents RTL variant correctly implements these adjustments. Apply equivalent RTL transformations to the AdvanceContributors stylesheet.

🤖 Prompt for AI Agents

In assets/build/blocks/AdvanceContributors/style-index-rtl.css around lines 1 to
1, the RTL file is identical to the LTR stylesheet and lacks directional
mirroring; update the CSS to mirror directional properties from the LTR file —
replace left/right properties (padding-left ↔ padding-right, margin-left ↔
margin-right, border-left ↔ border-right), invert float and text-align values,
and adjust directional shorthands (e.g., margin: top right bottom left -> swap
left/right), ensure any directional transform/translateX values are negated, and
follow the same RTL adjustments used in the TableOfContents RTL variant so
layout, alignment and visual ordering are correct for right-to-left languages.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Render function called inside function_exists guard.

The echo render_wedocs_contributors_block(...) at line 395 is inside the guard, so it only executes on first load. Typically, the function should be defined inside the guard, but called outside.

🔎 Proposed fix

     return $output;
-    }
-    echo render_wedocs_contributors_block($attributes, $content, $block);
 }
+}
+
+echo render_wedocs_contributors_block($attributes, $content, $block);

Also applies to: 395-396

🧰 Tools

🪛 PHPMD (2.15.0)

12-12: Avoid unused parameters such as '$content'. (undefined)

(UnusedFormalParameter)

---

12-12: Avoid unused parameters such as '$block'. (undefined)

(UnusedFormalParameter)

🤖 Prompt for AI Agents

In assets/build/blocks/Contributors/render.php around lines 11-12 and 395-396,
the render function call (echo render_wedocs_contributors_block(...)) is placed
inside the function_exists() guard so it only runs when the function is being
defined; move the echo call out of the guard so the guard only wraps the
function definition. Specifically, keep the if ( !
function_exists('render_wedocs_contributors_block') ) { function ... } block
as-is, then after the closing brace call echo
render_wedocs_contributors_block($attributes, $content, $block) so the function
is defined conditionally but always invoked.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Logic bug: Author may be added twice in 'all' mode.

The code iterates over $authors adding each contributor, then adds the author again at lines 130-132. This can result in duplicate entries.

🔎 Proposed fix

             case 'all':
             default:
                 // Get all contributors who have edited the post
                 $author_id = get_post_field('wedocs_contributors', $post->ID);
-                $authors = array_values($author_id); // return auhtors id.
-                foreach($authors as $author){
-                    $contributors[]= get_userdata($author);
-                }
-
-
-                if ($author_id && ($author_user = get_userdata($author_id))) {
-                    $contributors[] = $author_user;
+                if (is_array($author_id)) {
+                    foreach ($author_id as $author) {
+                        $user = get_userdata($author);
+                        if ($user) {
+                            $contributors[] = $user;
+                        }
+                    }
+                } elseif ($author_id && ($author_user = get_userdata($author_id))) {
+                    $contributors[] = $author_user;
                 }

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	case 'all':
	default:
	// Get all contributors who have edited the post
	$author_id = get_post_field('wedocs_contributors', $post->ID);
	$authors = array_values($author_id); // return auhtors id.
	foreach($authors as $author){
	$contributors[]= get_userdata($author);
	}
	if ($author_id && ($author_user = get_userdata($author_id))) {
	$contributors[] = $author_user;
	}
	case 'all':
	default:
	// Get all contributors who have edited the post
	$author_id = get_post_field('wedocs_contributors', $post->ID);
	if (is_array($author_id)) {
	foreach ($author_id as $author) {
	$user = get_userdata($author);
	if ($user) {
	$contributors[] = $user;
	}
	}
	} elseif ($author_id && ($author_user = get_userdata($author_id))) {
	$contributors[] = $author_user;
	}

🤖 Prompt for AI Agents

In assets/build/blocks/Contributors/render.php around lines 120 to 132, the code
appends contributors from $authors then unconditionally appends $author_user
again, causing duplicate entries; fix by removing the redundant append or
deduplicating before adding: either drop the final if-block that adds
$author_user (since it’s already added from $authors), or normalize $author_id
to an array and build $authors from it then ensure you only add each user once
(e.g., track added user IDs or filter duplicates with their IDs) before pushing
get_userdata results into $contributors.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Type safety: array_values() on potentially non-array value.

get_post_field('wedocs_contributors', $post->ID) may return a string, empty string, or WP_Error depending on the meta value. Calling array_values() on a non-array will cause a fatal error.

🔎 Proposed fix

-                $author_id = get_post_field('wedocs_contributors', $post->ID);
-                $authors = array_values($author_id); // return auhtors id.
+                $author_id = get_post_field('wedocs_contributors', $post->ID);
+                $authors = is_array($author_id) ? array_values($author_id) : [];

🤖 Prompt for AI Agents

In assets/build/blocks/Contributors/render.php around lines 123-124, the code
calls array_values() directly on the result of get_post_field which may be a
WP_Error, string, or empty value; update it to first guard against WP_Error,
then normalize the value to an array before calling array_values: if
is_wp_error($author_id) return/handle error (or set $authors = []), if
is_array($author_id) use array_values($author_id), if it's a non-empty scalar
wrap it as a single-element array (e.g. $authors = [$author_id]), otherwise set
$authors = []; this ensures type safety and avoids fatal errors.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Default export references identifiers that are not in scope.

The named re-exports on lines 11-22 make the functions available to consumers of this module, but they do not bring those identifiers into the local scope of this file. The default export object (lines 26-37) references generateBlockStyles, debounce, etc., which are undefined in this file's scope.

This will cause a ReferenceError at runtime when importing the default export.

🔎 Proposed fix

-// Export all helper functions
-export {
+// Import helpers for local use
+import {
 	generateBlockStyles,
 	generateTypographyStyles,
 	generateSpacingStyles,
 	generateElementStyles,
 	generateCustomProperties,
 	debounce,
 	isValidCSSValue,
 	convertToPx,
 	classNames,
 	getBreakpoints,
 	isBreakpoint
 } from './block-helpers';
+
+// Re-export all helper functions
+export {
+	generateBlockStyles,
+	generateTypographyStyles,
+	generateSpacingStyles,
+	generateElementStyles,
+	generateCustomProperties,
+	debounce,
+	isValidCSSValue,
+	convertToPx,
+	classNames,
+	getBreakpoints,
+	isBreakpoint
+};

 // Export default object with all helpers
 export default {
 	generateBlockStyles,

Committable suggestion skipped: line range outside the PR's diff.

🤖 Prompt for AI Agents

In src/blocks/helpers/index.js around lines 11-38, the file currently only
re-exports named helpers but then attempts to reference those identifiers for a
default export (causing ReferenceError); fix this by bringing the functions into
the local scope (either with a single import { generateBlockStyles,
generateTypographyStyles, generateSpacingStyles, generateElementStyles,
generateCustomProperties, debounce, isValidCSSValue, convertToPx, classNames,
getBreakpoints, isBreakpoint } from './block-helpers' or import * as helpers
from './block-helpers'), then re-export the named symbols and create the default
export object from those locally imported identifiers (or simply export default
helpers if using namespace import). Ensure the file both exports the named
symbols and exposes a valid default object referencing identifiers that exist in
this module scope.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Code executes at include time before $attributes is available.

Lines 109-152 run when the file is included, but $attributes isn't defined yet - it's only available when WordPress calls the render callback. This will cause PHP warnings/errors about undefined variables.

This code should either be inside the render callback or removed entirely as it duplicates logic already in render_wedocs_table_of_contents_block().

🤖 Prompt for AI Agents

In src/blocks/TableOfContents/render.php around lines 109-152, code is executing
at include time and references $attributes which is undefined until the
WordPress render callback runs; move this entire block into the
render_wedocs_table_of_contents_block() function (or delete it if it duplicates
that function) so it runs only when the render callback receives $attributes,
replace direct references to $attributes with the function's $attributes
parameter, and ensure any helper variables ($block_id, $css_classes,
$wrapper_attributes, $inline_styles, etc.) are computed inside the render
callback to avoid PHP notices and duplicate logic.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Same issue: Duplicate rendering code outside of function.

This file has the identical problem as the build version - lines 375-438 contain rendering code outside of any function that will execute on every file include.

This appears to be the source file. The entire section from line 375 to end of file should be removed, as it duplicates render_wedocs_table_of_contents_block() defined above.

🤖 Prompt for AI Agents

In src/blocks/TableOfContents/render.php around lines 375 to 438 there is
duplicated block render code placed outside any function (it duplicates
render_wedocs_table_of_contents_block()), which causes it to run on every
include; remove the entire section from line 375 to the end of the file (the
duplicated rendering block) so only the previously defined
render_wedocs_table_of_contents_block() is used, and verify there are no
leftover stray PHP open/close tags or duplicated variable definitions after
removal.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

IDs are assigned to headings after TOC HTML is generated, causing broken anchor links.

The generateTOCHTML function (line 58) is called before IDs are assigned to headings (lines 63-67). When generateTOCHTML accesses heading.id on line 100, headings without existing IDs will have empty id values, and the fallback 'toc-heading-' + index won't match the IDs assigned later.

🔎 Proposed fix: Assign IDs before generating HTML

 	function generateTOC(tocBlock) {
 		const supportedHeadings = getSupportedHeadings(tocBlock);
 		const showHierarchy = tocBlock.dataset.showHierarchy !== 'false';
 		const showNumbering = tocBlock.dataset.showNumbering === 'true';

 		// Find all headings in the page content
 		const contentArea = document.querySelector('.entry-content, .post-content, main, .content') || document.body;
 		const headingSelector = supportedHeadings.map(h => h.toLowerCase()).join(', ');
 		const headings = contentArea.querySelectorAll(headingSelector);

 		if (headings.length === 0) {
 			const tocContent = tocBlock.querySelector('.toc-content');
 			tocContent.innerHTML = '<div class="toc-empty-state"><p>No headings found in the content.</p></div>';
 			return;
 		}

+		// Add IDs to headings BEFORE generating TOC HTML
+		headings.forEach(function(heading, index) {
+			if (!heading.id) {
+				heading.id = 'toc-heading-' + index;
+			}
+		});
+
 		// Generate TOC HTML
 		const tocHTML = generateTOCHTML(headings, supportedHeadings, showHierarchy, showNumbering);
 		const tocContent = tocBlock.querySelector('.toc-content');
 		tocContent.innerHTML = tocHTML;
-
-		// Add IDs to headings if they don't have them
-		headings.forEach(function(heading, index) {
-			if (!heading.id) {
-				heading.id = 'toc-heading-' + index;
-			}
-		});
 	}

🤖 Prompt for AI Agents

In src/blocks/TableOfContents/view.js around lines 57 to 68, IDs are being added
to headings after generateTOCHTML is called, so generateTOCHTML sees empty ids
and produces broken anchors; move the headings.forEach block that assigns ids to
run before calling generateTOCHTML (or alternatively update generateTOCHTML to
generate and use fallback ids itself), then call generateTOCHTML and set
tocContent.innerHTML so the TOC uses the correct, already-assigned ids.

[coderabbitai]

Actionable comments posted: 2

🤖 Fix all issues with AI agents

In @src/blocks/TableOfContents/Inspector.js:
- Around line 113-122: The commented Advanced Panel in Inspector.js references
the attribute additionalCssClass but that variable is not included in the
attributes destructuring, which will throw a ReferenceError if the block is ever
uncommented; fix by adding additionalCssClass to the attributes destructuring
(where other attributes are pulled out, e.g., in the TableOfContentsInspector or
the functional component's props destructuring around the existing attributes
block) so additionalCssClass and its usage with setAttributes are defined and
safe to uncomment.
- Around line 10-11: Update the import so BoxControl uses the stable export:
replace __experimentalBoxControl with BoxControl in the import list (keep
__experimentalUnitControl as-is); ensure the import line now reads to include
BoxControl and __experimentalUnitControl so references to BoxControl in
Inspector.js resolve to the stable component.

🧹 Nitpick comments (1)

src/blocks/TableOfContents/Inspector.js (1)

52-53: Consider CSS classes for repeated styling patterns.

Multiple inline styles are used throughout, particularly marginBottom: '20px' which appears several times. While functional, using CSS classes would improve maintainability and consistency.

Also applies to: 129-130, 181-182, 197-197, 229-229, 233-234, 241-242

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 42113cb and 624b0b2.

📒 Files selected for processing (2)

• src/blocks/TableOfContents/Inspector.js
• src/editor/AiDocWriterPanel.js

🔇 Additional comments (3)

src/editor/AiDocWriterPanel.js (1)

7-7: Import path modernization is correct.

The migration from @wordpress/edit-post to @wordpress/editor is valid. Both PluginSidebar and PluginSidebarMoreMenuItem are properly exported by @wordpress/editor v14.5.0 and will work as expected.

src/blocks/TableOfContents/Inspector.js (2)

16-38: Previous critical issue resolved.

The destructuring of attributes is now properly implemented. All attribute variables used throughout the component are correctly extracted here, resolving the ReferenceError that was flagged in the previous review.

---

56-69: Well-implemented immutable state handling.

The checkbox logic correctly maintains immutability when adding or removing heading tags from the supportedHeadings array.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🌐 Web query:

@wordpress/components 28.10.0 BoxControl UnitControl stable

💡 Result:

Short answer: In @wordpress/components v28.10.0 BoxControl is stable, while UnitControl remains experimental (not stabilized).

Sources:

• BoxControl documented as stable / stabilized in core updates. [1]
• UnitControl still exported as __experimentalUnitControl in the handbook (experimental). [2]
• Release/changes overview noting BoxControl stabilization and UnitControl listed among experimental-to-monitor changes. [3]

References
[1] Make WordPress Core — Updates to user‑interface components in WordPress 6.8 (stabilized BoxControl).
[2] WordPress Block Editor Handbook — UnitControl (shows __experimentalUnitControl usage).
[3] WordPress Block Editor Handbook — BoxControl (stable usage and props).

---

🌐 Web query:

WordPress components experimental BoxControl UnitControl release notes

💡 Result:

Short summary:

• BoxControl: the experimental __experimentalBoxControl was stabilized and can be imported as BoxControl (not experimental) as part of the editor components changes around the WordPress 6.7 / 6.8 timeframe. [1][2]

• UnitControl: remains an experimental component (__experimentalUnitControl) in the Block Editor handbook; its docs and usage examples are published in the developer handbook. [3]

Sources:
[1] Make WordPress Core — Editor components updates in WordPress 6.7 (stabilized BoxControl).
[2] Make WordPress Core — Updates to user‑interface components in WordPress 6.8 (40px default-size opt-in, mentions BoxControl stabilization).
[3] WordPress Block Editor Handbook — UnitControl (experimental) documentation.

---

🌐 Web query:

@wordpress/components BoxControl UnitControl API stability changelog

💡 Result:

Summary — API stability / changelog highlights for BoxControl and UnitControl in @wordpress/components:

• BoxControl: stabilized (moved from __experimentalBoxControl to BoxControl) during the progressive reduction of experimental APIs (noted in WordPress 6.7 and reiterated in 6.8 release notes). [1][2]

• UnitControl: received API/structure changes in WordPress 6.2 (className/outer wrapper behavior; removal of components-unit-control-wrapper and __unstableWrapperClassName), and later was included in the 6.8 list of controls logging deprecation warnings while adopting the new 40px default sizing opt-in. [3][1]

• General: several components (including BoxControl and UnitControl) were part of the effort to reduce experimental exports and normalize sizing/props; consumers should prefer the stabilized exports (BoxControl, UnitControl) and follow the 40px default-size opt-in prop where noted (__next40pxDefaultSize). [1][2][3]

Sources:
[1] Make WordPress Core — “Updates to user-interface components in WordPress 6.8.”
[2] Make WordPress Core — “Updates to user-interface components in WordPress 6.7.”
[3] Make WordPress Core — “Editor Components updates in WordPress 6.2.”

---

Update BoxControl import to stable version.

BoxControl was stabilized in @wordpress/components (WordPress 6.7+) and can be imported directly without the experimental prefix. Update line 10 to import the stable version:

BoxControl,

UnitControl correctly remains experimental and should continue using __experimentalUnitControl as it has not yet been stabilized.

🤖 Prompt for AI Agents

In @src/blocks/TableOfContents/Inspector.js around lines 10 - 11, Update the
import so BoxControl uses the stable export: replace __experimentalBoxControl
with BoxControl in the import list (keep __experimentalUnitControl as-is);
ensure the import line now reads to include BoxControl and
__experimentalUnitControl so references to BoxControl in Inspector.js resolve to
the stable component.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Commented code references undefined variable.

The commented Advanced panel references additionalCssClass (line 116), which is not destructured from attributes. If this code is uncommented in the future without first adding the variable to the destructuring block, it will cause a ReferenceError.

🔧 Fix if uncommenting this section

Add to the destructuring block at line 38:

         listColor,
         listHoverColor,
-        listFontSize
+        listFontSize,
+        additionalCssClass
     } = attributes;

Committable suggestion skipped: line range outside the PR's diff.

🤖 Prompt for AI Agents

In @src/blocks/TableOfContents/Inspector.js around lines 113 - 122, The
commented Advanced Panel in Inspector.js references the attribute
additionalCssClass but that variable is not included in the attributes
destructuring, which will throw a ReferenceError if the block is ever
uncommented; fix by adding additionalCssClass to the attributes destructuring
(where other attributes are pulled out, e.g., in the TableOfContentsInspector or
the functional component's props destructuring around the existing attributes
block) so additionalCssClass and its usage with setAttributes are defined and
safe to uncomment.

[coderabbitai]

Actionable comments posted: 13

🤖 Fix all issues with AI agents

In @src/blocks/Contributors/render.php:
- Around line 156-165: Remove the hard-coded demo contributor array set to
$contributors when empty; instead either return empty output or show an
admin-only message. Replace the current block that assigns the mock (the array
with 'ID' => 1, 'display_name' => 'Demo Author', 'user_email' =>
'demo@example.com') with one of: 1) leave $contributors empty and
return/continue rendering nothing, 2) wrap a debug-only fallback behind a flag
like WP_DEBUG or a custom is_dev() check, or 3) display a message only to admins
using current_user_can('manage_options') before emitting any placeholder. Ensure
no mock data is present in production by removing the literal array assignment
to $contributors.
- Around line 100-151: The 'all' case mishandles wedocs_contributors as both
array and scalar causing duplicates and type errors; update the logic in the
switch 'all' branch to first retrieve and validate the contributors data from
get_post_field('wedocs_contributors', $post->ID) (ensure it exists and is an
array or decode it if stored as JSON), normalize it into an array (e.g.,
$author_ids), iterate that array to populate $contributors via get_userdata($id)
while tracking seen IDs to avoid duplicates, remove the redundant scalar check
that treats $author_id as a single ID, and then merge additional unique revision
authors into the same seen set before adding their userdata.
- Line 395: The file currently calls echo
render_wedocs_contributors_block($attributes, $content, $block) at file scope;
remove that call so the function render_wedocs_contributors_block is only
defined and not invoked on include. Ensure the function definition remains in
place and that block.json registers this function as the render callback (so
WordPress will call it with the proper $attributes, $content, $block when
rendering the block).

In @src/blocks/HelpfulFeedback/edit.js:
- Around line 104-113: The containerStyle object can throw if containerPadding
or containerMargin is undefined; update the code that builds containerStyle
(and/or create safePadding/safeMargin helper objects) to use optional chaining
or fallbacks for top/right/bottom/left (e.g., derive safe values from
containerPadding?.top ?? 0 etc.) so padding and margin string interpolation
never accesses undefined properties; apply the same defensive fallback for
containerBorderRadius and containerBorderWidth if needed to avoid runtime errors
when those props are missing.

In @src/blocks/HelpfulFeedback/render.php:
- Around line 37-38: The code reads $_COOKIE['wedocs_response'] directly;
instead retrieve and sanitize the cookie before exploding and comparing to
$post_id: get the raw cookie (e.g., via filter_input(INPUT_COOKIE,
'wedocs_response') or isset($_COOKIE['wedocs_response'])), run wp_unslash() and
sanitize_text_field() (or appropriate sanitizer), then explode into an array and
cast/clean each element (e.g., array_map('intval') or
array_map('sanitize_text_field')) before assigning to $previous and using
in_array($post_id, $previous, true) to ensure safe, type-strict comparison.
- Line 302: Replace raw translation outputs that use _e() with the escaped
helper esc_html_e() to ensure translated strings are escaped for HTML;
specifically update the calls rendering "You found this helpful", "Yes", and
"No" (the _e('You found this helpful', 'wedocs'), _e('Yes', 'wedocs'), and
_e('No', 'wedocs') usages in the HelpfulFeedback render) to use esc_html_e()
instead so translation output is safely escaped.
- Line 26: The code directly assigns $_SERVER['REMOTE_ADDR'] to $user_ip without
sanitization; change the assignment so you read the value safely (e.g., $raw_ip
= $_SERVER['REMOTE_ADDR'] ?? '';), then validate it with filter_var($raw_ip,
FILTER_VALIDATE_IP) and only assign the validated value to $user_ip (or set to
an empty string/null if invalid). Update the code around the $user_ip variable
in render.php to use this validation and avoid trusting the superglobal raw
value.
- Around line 13-19: The file contains top-level render logic that must be
wrapped in the project's standard render callback; create a function named
render_wedocs_helpful_feedback_block($attributes, $content, $block) and move the
existing code (including the get_post_type() check and ob_start()/ob_get_clean()
flow) into that function, adjust indentation, and return the buffered output
(use return ob_get_clean() instead of echo); ensure the function signature
matches other blocks so it can be used as the render callback.

In @src/blocks/HelpfulFeedback/save.js:
- Around line 1-5: Remove the unused import by deleting the "useBlockProps"
import statement at the top of the file since the Save component returns null
for server-side rendering; update the import list in
src/blocks/HelpfulFeedback/save.js so only necessary imports remain (keep the
Save function as-is returning null).

In @src/blocks/HelpfulFeedback/view.js:
- Around line 141-154: The template injects thankYouMessage directly into
thankYouContent, creating an XSS risk; fix it by escaping or encoding the
message before interpolation (e.g., create an escapeHtml utility or use a DOM
text node and textContent) and replace thankYouMessage with
escapedThankYouMessage in the thankYouContent construction; update the code that
builds thankYouContent (the template literal block) to use the escaped value and
ensure any helper is reused wherever thankYouMessage is interpolated.

In @src/blocks/HelpfulModal/render.php:
- Around line 140-151: The declared global function get_help_icon_svg can
collide with other blocks; refactor it into a uniquely namespaced/static class
method (e.g., HelpfulModal::getHelpIconSvg or HelpfulModal_get_help_icon_svg)
and move the SVG map into that class, then replace all calls to
get_help_icon_svg(...) with the new static method name to avoid function_exists
guards and unintended override; ensure the method signature and return behavior
remain the same.

In @wedocs.php:
- Around line 179-180: The code enqueues 'wedocs-admin-script' on init which can
race with Assets::register() / register_blocks() and also loads on the frontend;
change it so the script is enqueued only after registration and only in
admin/editor context by moving the enqueue call into an admin_enqueue_scripts
callback (or guard it with is_admin() || current_user_can('edit_posts')) and
ensure it runs after Assets::register() / register_blocks() so
'wedocs-admin-script' is registered before calling wp_enqueue_script.

🧹 Nitpick comments (18)

src/blocks/Contributors/render.php (1)

12-12: Optional: Consider documenting unused callback parameters.

Static analysis flags $content and $block as unused. While these are part of the WordPress render callback signature, consider:

1. Adding @SuppressWarnings or similar annotation if they're intentionally unused
2. Verifying whether $block context might be useful for future enhancements
3. Using @param documentation to clarify they're part of the required WordPress signature

src/blocks/HelpfulModal/index.js (2)

2-6: Fix inconsistent comment indentation.

The JSDoc comment block has extra leading spaces before /**, which is inconsistent with standard formatting conventions.

♻️ Proposed fix

-
-  /**
+/**
  * Registers a new block provided a unique name and an object defining its behavior.
  *
  * @see https://developer.wordpress.org/block-editor/reference-guides/block-api/block-registration/
  */

---

35-35: Remove trailing whitespace.

Line 35 contains trailing whitespace that should be removed for code cleanliness.

src/blocks/HelpfulModal/style.scss (1)

43-43: Consider using a lower z-index value.

The z-index of 99999 is extremely high and may conflict with other WordPress plugins, themes, or admin UI elements that use high z-index values. WordPress admin bar typically uses z-index around 99999-100000, which could cause overlap issues.

Consider using a more moderate z-index value (e.g., 10000-50000) to reduce the likelihood of conflicts while still ensuring the modal appears above most content.

♻️ Proposed fix

-	z-index: 99999;
+	z-index: 10000;

src/blocks/HelpfulFeedback/index.js (1)

1-5: Standardize quote style for consistency.

This file uses double quotes for imports, while other block files in the PR (e.g., src/blocks/HelpfulModal/index.js) use single quotes. For consistency across the codebase, consider standardizing on one quote style.

♻️ Proposed fix

-import { registerBlockType } from "@wordpress/blocks";
-import Edit from "./edit";
-import Save from "./save";
-import metadata from "./block.json";
-import "./style.scss";
+import { registerBlockType } from '@wordpress/blocks';
+import Edit from './edit';
+import Save from './save';
+import metadata from './block.json';
+import './style.scss';

src/blocks/index.js (2)

7-7: Remove trailing whitespace.

Line 7 contains trailing whitespace that should be removed for code cleanliness.

---

8-73: Remove or document commented out imports.

There are 65+ lines of commented out block imports. Consider one of the following approaches:

1. If these blocks are not being developed: Remove the commented code entirely to reduce clutter and maintenance burden.
2. If these are planned features: Remove the comments and track these features in GitHub issues or a project roadmap instead.
3. If temporarily disabled: Add a clear comment explaining why they're disabled and when they'll be re-enabled.

Leaving large amounts of commented code in the codebase creates confusion for future maintainers and increases the risk of merge conflicts.

Example approach

If these are planned features:

-// import './Breadcrumbs';
-// import './CategoryDocs';
-// ... (63 more lines)
+// Future block implementations tracked in:
+// - Issue #XXX: Documentation blocks (Breadcrumbs, CategoryDocs, etc.)
+// - Issue #YYY: Engagement blocks (DocRating, DocFeedback, etc.)

Or simply remove them if not actively planned.

src/blocks/HelpfulFeedback/view.js (1)

123-126: Consider extracting duplicate SVG icons to a shared module.

These SVG icon paths are duplicated across view.js, edit.js, and render.php. Extracting them to a shared constants file would improve maintainability.

src/blocks/HelpfulFeedback/edit.js (1)

4-4: Unused import: RichText.

RichText is imported but never used in this component.

♻️ Remove unused import

-import { useBlockProps, InspectorControls, RichText } from '@wordpress/block-editor';
+import { useBlockProps, InspectorControls } from '@wordpress/block-editor';

src/blocks/HelpfulFeedback/style.scss (1)

218-227: Consider prefixing the fadeIn keyframe name.

The fadeIn keyframe name is generic and could conflict with other stylesheets. A prefixed name like wedocs-fadeIn would prevent potential conflicts.

♻️ Suggested naming

-    @keyframes fadeIn {
+    @keyframes wedocs-fadeIn {
         from {
             opacity: 0;
             transform: translateY(10px);
         }
         to {
             opacity: 1;
             transform: translateY(0);
         }
     }

And update the animation reference:

-        animation: fadeIn 0.3s ease-in-out;
+        animation: wedocs-fadeIn 0.3s ease-in-out;

src/blocks/HelpfulFeedback/render.php (1)

253-255: Consider escaping vote count output for consistency.

While $yes_votes and $no_votes are cast to integers (line 29-30), it's a WordPress best practice to escape all output. Using esc_html() would add defense-in-depth.

♻️ Suggested consistency improvement

-                            <span class="vote-count">(<?php echo $yes_votes; ?>)</span>
+                            <span class="vote-count">(<?php echo esc_html($yes_votes); ?>)</span>

src/blocks/HelpfulModal/edit.js (2)

36-36: Unused icon imports from @wordpress/icons.

help, info, and email are imported but never used. The getIcon function (lines 120-142) renders custom inline SVGs instead.

♻️ Remove unused imports

-import { settings, help, info, email } from '@wordpress/icons';
+import { settings } from '@wordpress/icons';

---

28-28: Use the custom BorderControl component for consistency.

The custom BorderControl component at src/blocks/components/BorderControl.js is used in active blocks like Contributors, but HelpfulModal imports the experimental WordPress __experimentalBorderControl instead. Update this to import from the custom components for consistency with other similar blocks.

wedocs.php (5)

49-49: Consider using consistent path resolution.

Line 48 uses __DIR__ while this line uses plugin_dir_path(__FILE__). Both work, but consistency improves readability.

♻️ Suggested refactor for consistency

-require_once plugin_dir_path(__FILE__) . 'src/blocks/helpers/block-styles.php';
+require_once __DIR__ . '/src/blocks/helpers/block-styles.php';

---

186-186: Remove or document commented-out code.

The commented-out AdvanceContributors block suggests incomplete development. Either remove it or add a TODO comment explaining why it's disabled.

---

178-202: Consider enqueuing scripts only in block editor context.

The wedocs-admin-script is enqueued on every init action, including frontend requests. For better performance, consider enqueuing it only when the block editor is loaded.

♻️ Suggested improvement for editor-only enqueuing

 public function register_blocks() {
-    // Enqueue admin script early to make weDocsAdminScriptVars available for blocks
-    wp_enqueue_script( 'wedocs-admin-script' );
-
     // Modern WordPress block registration using block.json files
     $block_directories = [

Instead, ensure the script is enqueued via block.json editorScript property or in an enqueue_block_editor_assets hook.

---

347-356: Prevent potential duplicate block categories.

The filter always appends the 'wedocs' category without checking if it already exists, which could create duplicates if the filter runs multiple times or another plugin adds the same category.

♻️ Suggested fix to prevent duplicates

 add_filter( 'block_categories_all', function( $categories, $post ) {
-    // Add "wedocs" category if not already there
-    $categories[] = array(
-        'slug'  => 'wedocs',
-        'title' => __( 'weDocs Blocks', 'wedocs' ),
-        'icon'  => null, // optional, doesn't show everywhere
-    );
-
+    // Check if category already exists
+    $category_exists = false;
+    foreach ( $categories as $category ) {
+        if ( isset( $category['slug'] ) && $category['slug'] === 'wedocs' ) {
+            $category_exists = true;
+            break;
+        }
+    }
+    
+    // Add "wedocs" category if not already there
+    if ( ! $category_exists ) {
+        $categories[] = array(
+            'slug'  => 'wedocs',
+            'title' => __( 'weDocs Blocks', 'wedocs' ),
+            'icon'  => null,
+        );
+    }
+    
     return $categories;
 }, 10, 2 );

---

347-356: Unused $post parameter.

The filter callback declares a $post parameter but never uses it. You can either remove it or suppress the unused variable warning with @param annotation.

♻️ Option 1: Remove unused parameter

-add_filter( 'block_categories_all', function( $categories, $post ) {
+add_filter( 'block_categories_all', function( $categories ) {

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5012397 and 8a5d8d0.

📒 Files selected for processing (18)

• src/blocks/Contributors/render.php
• src/blocks/HelpfulFeedback/block.json
• src/blocks/HelpfulFeedback/edit.js
• src/blocks/HelpfulFeedback/index.js
• src/blocks/HelpfulFeedback/render.php
• src/blocks/HelpfulFeedback/save.js
• src/blocks/HelpfulFeedback/style.scss
• src/blocks/HelpfulFeedback/view.js
• src/blocks/HelpfulModal/block.json
• src/blocks/HelpfulModal/edit.js
• src/blocks/HelpfulModal/editor.scss
• src/blocks/HelpfulModal/index.js
• src/blocks/HelpfulModal/render.php
• src/blocks/HelpfulModal/save.js
• src/blocks/HelpfulModal/style.scss
• src/blocks/HelpfulModal/view.js
• src/blocks/index.js
• wedocs.php

✅ Files skipped from review due to trivial changes (4)

• src/blocks/HelpfulModal/save.js
• src/blocks/HelpfulModal/editor.scss
• src/blocks/HelpfulFeedback/block.json
• src/blocks/HelpfulModal/block.json

🧰 Additional context used

🧬 Code graph analysis (8)

src/blocks/HelpfulFeedback/edit.js (1)

src/blocks/CustomControls/RadioImageControl.js (1)

• RadioImageControl (3-26)

src/blocks/HelpfulFeedback/view.js (2)

src/utils/menuFix.js (1)

• $ (2-2)

assets/js/frontend.js (1)

• data (163-166)

src/blocks/HelpfulModal/edit.js (2)

src/blocks/components/BorderControl.js (1)

• BorderControl (11-116)

src/blocks/helpers/block-helpers.js (1)

• p (35-35)

src/blocks/HelpfulModal/render.php (1)

src/blocks/HelpfulModal/edit.js (1)

• attributes (55-104)

src/blocks/Contributors/render.php (1)

src/blocks/helpers/block-styles.php (8)

• wedocs_build_background_styles (134-152)
• wedocs_build_spacing_styles (58-70)
• wedocs_build_border_styles (81-101)
• wedocs_build_shadow_styles (109-123)
• wedocs_build_element_styles (179-228)
• wedocs_generate_block_id (160-162)
• wedocs_styles_to_css (236-242)
• wedocs_generate_responsive_css (251-281)

src/blocks/HelpfulModal/index.js (1)

src/blocks/HelpfulModal/edit.js (1)

• Edit (54-690)

src/blocks/HelpfulFeedback/render.php (1)

src/blocks/HelpfulFeedback/edit.js (1)

• attributes (22-69)

src/blocks/HelpfulFeedback/index.js (2)

src/blocks/HelpfulFeedback/edit.js (1)

• Edit (19-511)

src/blocks/HelpfulFeedback/save.js (1)

• Save (3-5)

🪛 PHPMD (2.15.0)

src/blocks/Contributors/render.php

12-12: Avoid unused parameters such as '$content'. (undefined)

(UnusedFormalParameter)

---

12-12: Avoid unused parameters such as '$block'. (undefined)

(UnusedFormalParameter)

🔇 Additional comments (12)

src/blocks/Contributors/render.php (3)

11-17: LGTM: Function guard and post validation.

The function existence check and early return for non-docs post types are appropriate defensive patterns.

---

167-344: LGTM: Avatar styling and HTML output generation.

The avatar styling (lines 167-203), element style building (lines 205-230), and HTML output generation (lines 232-344) demonstrate good practices:

• Proper use of helper functions from block-styles.php
• Consistent output escaping (esc_attr, esc_html, esc_url)
• Flexible avatar rendering (user avatar or default icon)
• Configurable link behavior
• Optional schema.org markup support

---

346-391: LGTM: Responsive CSS generation.

The responsive CSS implementation properly uses the wedocs_generate_responsive_css helper function and includes:

• Tablet and mobile breakpoints
• Accessibility considerations (prefers-reduced-motion)
• Hover effects with CSS custom properties
• Proper CSS variable fallbacks

src/blocks/HelpfulFeedback/view.js (1)

6-71: Well-structured AJAX voting implementation.

Good use of class-based organization, proper loading state management, and comprehensive error handling with context-aware messages (403, 429 status codes). The event binding delegation pattern ($(document).on) is appropriate for dynamically rendered content.

src/blocks/HelpfulFeedback/edit.js (1)

10-16: Usage of experimental WordPress components.

Multiple __experimental prefixed components are used (BoxControl, BorderControl, ToolsPanel, ToolsPanelItem). These APIs may change in future WordPress releases. Consider monitoring WordPress core updates for API stability.

src/blocks/HelpfulModal/render.php (1)

198-199: JSON data output is properly encoded.

Good use of wp_json_encode() for the modal data script, which properly escapes special characters for safe JSON output.

src/blocks/HelpfulFeedback/style.scss (1)

38-49: Excellent accessibility implementation.

Good attention to accessibility: minimum touch target size (44px), visible focus indicators, and proper disabled state styling. The reduced motion and high contrast media queries are also well implemented.

src/blocks/HelpfulModal/view.js (2)

257-265: Good XSS protection with escapeHtml helper.

Properly escapes HTML entities for user-provided content in the modal. All dynamic content (title, labels, placeholder, button text) is correctly escaped before insertion.

---

133-139: Good defensive check for AJAX configuration.

Properly validates that needMoreHelpAjax is defined before attempting form submission, with a user-friendly error message.

src/blocks/HelpfulModal/edit.js (2)

145-153: Good defensive coding in style computation.

Proper use of ternary operators to handle potentially undefined containerPadding and containerMargin values, with sensible fallbacks.

---

585-686: Well-implemented editor modal preview.

Good UX with a toggle-able modal preview in the editor. The form properly prevents default submission (line 679), and the overlay click closes the modal. This allows content editors to preview their changes without leaving the editor.

wedocs.php (1)

336-343: LGTM! Good performance optimization.

The function correctly dequeues pro frontend CSS on non-docs pages to prevent unnecessary asset loading. The logic covers all relevant docs-related contexts (singular, archive, taxonomies), and the priority of 20 ensures it runs after the styles are enqueued.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Remove or guard mock contributor data.

The mock/demo contributor data on lines 158-164 should not appear in production code. If no contributors are found, consider:

1. Returning empty output
2. Displaying a message to administrators only
3. Moving mock data behind a development/debug flag

Currently, this mock data could appear on live documentation pages if the contributor logic fails, which would be confusing to end users.

💡 Suggested fix to remove mock data

 // Filter out invalid contributors
 $contributors = array_filter($contributors);
 
 if (empty($contributors)) {
-    // For demo purposes, add mock contributors if none found
-    $contributors = [
-        (object) [
-            'ID' => 1,
-            'display_name' => 'Demo Author',
-            'user_email' => 'demo@example.com'
-        ]
-    ];
+    return ''; // No contributors to display
 }

Committable suggestion skipped: line range outside the PR's diff.

🤖 Prompt for AI Agents

In @src/blocks/Contributors/render.php around lines 156 - 165, Remove the
hard-coded demo contributor array set to $contributors when empty; instead
either return empty output or show an admin-only message. Replace the current
block that assigns the mock (the array with 'ID' => 1, 'display_name' => 'Demo
Author', 'user_email' => 'demo@example.com') with one of: 1) leave $contributors
empty and return/continue rendering nothing, 2) wrap a debug-only fallback
behind a flag like WP_DEBUG or a custom is_dev() check, or 3) display a message
only to admins using current_user_can('manage_options') before emitting any
placeholder. Ensure no mock data is present in production by removing the
literal array assignment to $contributors.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Critical: Remove incorrect echo statement.

Line 395 attempts to call the function at file scope, which is incorrect for WordPress block render callbacks. This will cause errors because:

1. $attributes, $content, and $block are undefined at this scope
2. WordPress automatically calls the render callback when the block is rendered
3. This echo will execute on every file include, not during block rendering

The function should only be defined here, not called. WordPress will invoke it via the render callback mechanism defined in block.json.

🐛 Proposed fix

     return $output;
 }
-echo render_wedocs_contributors_block($attributes, $content, $block);
 }

Note: Ensure block.json properly registers this function as the render callback.

Committable suggestion skipped: line range outside the PR's diff.

🤖 Prompt for AI Agents

In @src/blocks/Contributors/render.php at line 395, The file currently calls
echo render_wedocs_contributors_block($attributes, $content, $block) at file
scope; remove that call so the function render_wedocs_contributors_block is only
defined and not invoked on include. Ensure the function definition remains in
place and that block.json registers this function as the render callback (so
WordPress will call it with the proper $attributes, $content, $block when
rendering the block).

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Potential runtime error when accessing nested padding/margin properties.

If containerPadding or containerMargin is undefined, accessing .top, .right, etc. will throw an error. Consider using optional chaining or providing fallback objects.

🛡️ Suggested defensive coding

     const containerStyle = {
         backgroundColor: containerBgColor,
-        padding: `${containerPadding.top} ${containerPadding.right} ${containerPadding.bottom} ${containerPadding.left}`,
-        margin: `${containerMargin.top} ${containerMargin.right} ${containerMargin.bottom} ${containerMargin.left}`,
+        padding: containerPadding ? `${containerPadding.top} ${containerPadding.right} ${containerPadding.bottom} ${containerPadding.left}` : undefined,
+        margin: containerMargin ? `${containerMargin.top} ${containerMargin.right} ${containerMargin.bottom} ${containerMargin.left}` : undefined,

🤖 Prompt for AI Agents

In @src/blocks/HelpfulFeedback/edit.js around lines 104 - 113, The
containerStyle object can throw if containerPadding or containerMargin is
undefined; update the code that builds containerStyle (and/or create
safePadding/safeMargin helper objects) to use optional chaining or fallbacks for
top/right/bottom/left (e.g., derive safe values from containerPadding?.top ?? 0
etc.) so padding and margin string interpolation never accesses undefined
properties; apply the same defensive fallback for containerBorderRadius and
containerBorderWidth if needed to avoid runtime errors when those props are
missing.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash

# First, let's see the actual structure of the file in question
echo "=== Structure of src/blocks/HelpfulFeedback/render.php ==="
head -50 src/blocks/HelpfulFeedback/render.php

echo ""
echo "=== Total lines in file ==="
wc -l src/blocks/HelpfulFeedback/render.php

echo ""
echo "=== Checking for function definitions ==="
rg 'function|fn\s+\(' src/blocks/HelpfulFeedback/render.php

Repository: weDevsOfficial/wedocs-plugin

Length of output: 1975

---

🏁 Script executed:

#!/bin/bash

# Compare with other render.php files
echo "=== Other render.php files in src/blocks ==="
fd -e php -p 'render\.php$' src/blocks

echo ""
echo "=== Structure of a few other render.php files (first 40 lines) ==="
for file in $(fd -e php -p 'render\.php$' src/blocks | head -3); do
  echo "--- File: $file ---"
  head -40 "$file"
  echo ""
done

Repository: weDevsOfficial/wedocs-plugin

Length of output: 5988

---

Structural issue: Code not wrapped in function callback.

All other render.php files in the project (AdvanceContributors, Contributors, DocsGrid) wrap their logic in a function definition. This file contains 398 lines of render logic indented as if inside a function, but with no function wrapper. The code should be wrapped in a render callback function consistent with the project's pattern:

function render_wedocs_helpful_feedback_block($attributes, $content, $block) {
    // ... existing code with indentation corrected
}

🤖 Prompt for AI Agents

In @src/blocks/HelpfulFeedback/render.php around lines 13 - 19, The file
contains top-level render logic that must be wrapped in the project's standard
render callback; create a function named
render_wedocs_helpful_feedback_block($attributes, $content, $block) and move the
existing code (including the get_post_type() check and ob_start()/ob_get_clean()
flow) into that function, adjust indentation, and return the buffered output
(use return ob_get_clean() instead of echo); ensure the function signature
matches other blocks so it can be used as the render callback.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Unsanitized superglobal access: $_SERVER['REMOTE_ADDR'].

Direct access to $_SERVER['REMOTE_ADDR'] without sanitization. This value can be spoofed in some server configurations and should be sanitized.

🔒 Suggested fix

-        $user_ip = $_SERVER['REMOTE_ADDR'] ?? '';
+        $user_ip = isset($_SERVER['REMOTE_ADDR']) ? sanitize_text_field(wp_unslash($_SERVER['REMOTE_ADDR'])) : '';

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	$user_ip = $_SERVER['REMOTE_ADDR'] ?? '';
	$user_ip = isset($_SERVER['REMOTE_ADDR']) ? sanitize_text_field(wp_unslash($_SERVER['REMOTE_ADDR'])) : '';

🤖 Prompt for AI Agents

In @src/blocks/HelpfulFeedback/render.php at line 26, The code directly assigns
$_SERVER['REMOTE_ADDR'] to $user_ip without sanitization; change the assignment
so you read the value safely (e.g., $raw_ip = $_SERVER['REMOTE_ADDR'] ?? '';),
then validate it with filter_var($raw_ip, FILTER_VALIDATE_IP) and only assign
the validated value to $user_ip (or set to an empty string/null if invalid).
Update the code around the $user_ip variable in render.php to use this
validation and avoid trusting the superglobal raw value.

[coderabbitai]

🛠️ Refactor suggestion | 🟠 Major

Remove unused import.

The useBlockProps import is not used since the Save component returns null for server-side rendering. This unused import adds unnecessary code to the bundle.

♻️ Proposed fix

-import { useBlockProps } from '@wordpress/block-editor';
-
 const Save = () => {
     return null;
 };

🤖 Prompt for AI Agents

In @src/blocks/HelpfulFeedback/save.js around lines 1 - 5, Remove the unused
import by deleting the "useBlockProps" import statement at the top of the file
since the Save component returns null for server-side rendering; update the
import list in src/blocks/HelpfulFeedback/save.js so only necessary imports
remain (keep the Save function as-is returning null).

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Potential XSS risk with thankYouMessage in template literal.

The thankYouMessage is inserted directly into the HTML template without escaping. While it comes from a data attribute, if the server-side doesn't properly sanitize this value, it could lead to XSS.

🔒 Suggested fix: Escape the thank you message

+        // Helper function to escape HTML
+        escapeHtml(text) {
+            const div = document.createElement('div');
+            div.textContent = text;
+            return div.innerHTML;
+        }

         const thankYouContent = `
             <div class="wedocs-feedback-thank-you">
                 <div class="wedocs-feedback-title" style="color: #28a745; margin-bottom: 16px;">
-                    ${thankYouMessage}
+                    ${this.escapeHtml(thankYouMessage)}
                 </div>

Committable suggestion skipped: line range outside the PR's diff.

🤖 Prompt for AI Agents

In @src/blocks/HelpfulFeedback/view.js around lines 141 - 154, The template
injects thankYouMessage directly into thankYouContent, creating an XSS risk; fix
it by escaping or encoding the message before interpolation (e.g., create an
escapeHtml utility or use a DOM text node and textContent) and replace
thankYouMessage with escapedThankYouMessage in the thankYouContent construction;
update the code that builds thankYouContent (the template literal block) to use
the escaped value and ensure any helper is reused wherever thankYouMessage is
interpolated.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Function guard pattern may cause unexpected behavior.

Using function_exists() to guard function declaration means if get_help_icon_svg is defined elsewhere (e.g., in another block's render.php loaded first), this block will use that implementation instead. Consider namespacing or using a class method to avoid conflicts.

♻️ Suggested approach using a class or unique function name

-if (!function_exists('get_help_icon_svg')) {
-	function get_help_icon_svg($type, $styles) {
+if (!function_exists('wedocs_get_help_icon_svg')) {
+	function wedocs_get_help_icon_svg($type, $styles) {

Then update the call on line 182:

-			<?php echo get_help_icon_svg($icon_type, $icon_styles); ?>
+			<?php echo wedocs_get_help_icon_svg($icon_type, $icon_styles); ?>

Committable suggestion skipped: line range outside the PR's diff.

🤖 Prompt for AI Agents

In @src/blocks/HelpfulModal/render.php around lines 140 - 151, The declared
global function get_help_icon_svg can collide with other blocks; refactor it
into a uniquely namespaced/static class method (e.g.,
HelpfulModal::getHelpIconSvg or HelpfulModal_get_help_icon_svg) and move the SVG
map into that class, then replace all calls to get_help_icon_svg(...) with the
new static method name to avoid function_exists guards and unintended override;
ensure the method signature and return behavior remain the same.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Document-level keydown listener added per block instance.

Each block instance adds a new keydown listener to document. If multiple blocks exist on a page, this creates redundant listeners. Consider using event delegation or a singleton pattern.

♻️ Suggested improvement

+// Track if escape handler is already registered
+let escapeHandlerRegistered = false;
+const modalInstances = new Set();

 function initializeHelpBlock(block) {
     // ... existing code ...
     
+    modalInstances.add(modal);
+    
-    // Close on escape key
-    document.addEventListener('keydown', function(e) {
-        if (e.key === 'Escape' && modal.classList.contains('show')) {
-            closeModal();
-        }
-    });
+    // Register escape handler once
+    if (!escapeHandlerRegistered) {
+        document.addEventListener('keydown', function(e) {
+            if (e.key === 'Escape') {
+                modalInstances.forEach(m => {
+                    if (m.classList.contains('show')) {
+                        m.classList.remove('show');
+                        document.body.style.overflow = '';
+                    }
+                });
+            }
+        });
+        escapeHandlerRegistered = true;
+    }

Committable suggestion skipped: line range outside the PR's diff.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

# First, find wedocs.php and view the context around lines 179-180
find . -name "wedocs.php" -type f

Repository: weDevsOfficial/wedocs-plugin

Length of output: 84

---

🏁 Script executed:

# View the context around lines 179-180 in wedocs.php
sed -n '170,210p' ./wedocs.php

Repository: weDevsOfficial/wedocs-plugin

Length of output: 1414

---

🏁 Script executed:

# Search for where wedocs-admin-script is registered
rg "wedocs-admin-script" -n

Repository: weDevsOfficial/wedocs-plugin

Length of output: 330

---

🏁 Script executed:

# View the Assets.php file to see script registration
sed -n '1,100p' ./includes/Assets.php

Repository: weDevsOfficial/wedocs-plugin

Length of output: 3344

---

🏁 Script executed:

# Check the full Assets.php to see the admin_enqueue method
sed -n '150,170p' ./includes/Assets.php

Repository: weDevsOfficial/wedocs-plugin

Length of output: 817

---

🏁 Script executed:

# Check if there are any other registrations or if the order is guaranteed
# Look at the class structure to see how Assets is instantiated
grep -rn "new Assets" . --include="*.php"

Repository: weDevsOfficial/wedocs-plugin

Length of output: 54

---

🏁 Script executed:

# Check how the plugin initializes - look at the main wedocs.php file
sed -n '1,50p' ./wedocs.php

Repository: weDevsOfficial/wedocs-plugin

Length of output: 1728

---

🏁 Script executed:

# Look for the plugin initialization and where Assets is instantiated
grep -rn "Assets" ./wedocs.php | head -20

Repository: weDevsOfficial/wedocs-plugin

Length of output: 142

---

🏁 Script executed:

# Find where the main plugin class is instantiated and when Assets is initialized
sed -n '200,250p' ./wedocs.php

Repository: weDevsOfficial/wedocs-plugin

Length of output: 1430

---

🏁 Script executed:

# Check when init_classes is called - look for the main plugin initialization
sed -n '80,150p' ./wedocs.php

Repository: weDevsOfficial/wedocs-plugin

Length of output: 1824

---

🏁 Script executed:

# Look for the init_actions method to see the order of hook registration
grep -n "init_actions" ./wedocs.php
sed -n '160,175p' ./wedocs.php

Repository: weDevsOfficial/wedocs-plugin

Length of output: 601

---

🏁 Script executed:

# Let me verify the execution order by checking the hooks more carefully
# Get the full init_actions and constructor
sed -n '100,110p' ./wedocs.php

Repository: weDevsOfficial/wedocs-plugin

Length of output: 358

---

🏁 Script executed:

# Check the bottom of wedocs.php to see when WeDocs is instantiated
tail -20 ./wedocs.php

Repository: weDevsOfficial/wedocs-plugin

Length of output: 810

---

🏁 Script executed:

# Find where WeDocs::init() is called
grep -n "WeDocs::init()" ./wedocs.php

Repository: weDevsOfficial/wedocs-plugin

Length of output: 102

---

🏁 Script executed:

# Get the context around line 326
sed -n '320,330p' ./wedocs.php

Repository: weDevsOfficial/wedocs-plugin

Length of output: 202

---

🏁 Script executed:

# Let me trace the execution order more carefully
# Check if there's any conditional logic around enqueuing in register_blocks
sed -n '175,195p' ./wedocs.php

Repository: weDevsOfficial/wedocs-plugin

Length of output: 864

---

Enqueue wedocs-admin-script only in admin/editor context and after registration is guaranteed.

The script is enqueued on the init hook without verifying registration has completed, creating a potential race condition since both Assets::register() and register_blocks() are hooked to init with the same priority. Additionally, enqueuing on init means the script loads on the frontend unnecessarily—the comment itself indicates this is for block editor support only. Move the enqueue to admin_enqueue_scripts or wrap it with is_admin() / current_user_can( 'edit_posts' ) to ensure it only loads where needed.

🤖 Prompt for AI Agents

In @wedocs.php around lines 179 - 180, The code enqueues 'wedocs-admin-script'
on init which can race with Assets::register() / register_blocks() and also
loads on the frontend; change it so the script is enqueued only after
registration and only in admin/editor context by moving the enqueue call into an
admin_enqueue_scripts callback (or guard it with is_admin() ||
current_user_can('edit_posts')) and ensure it runs after Assets::register() /
register_blocks() so 'wedocs-admin-script' is registered before calling
wp_enqueue_script.

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @src/blocks/TableOfContents/ColorsControls.js:
- Around line 1-14: Update the import/notes so TabPanel is not treated as
experimental: ensure TabPanel is imported as the stable TabPanel (no
__experimental prefix) and only DropdownContentWrapper, HStack, Text, and ZStack
use the __experimental* names; remove TabPanel from any comment or component
list that claims five experimental components and leave the four actual
experimental imports unchanged.

🧹 Nitpick comments (5)

src/blocks/TableOfContents/ColorsControls.js (5)

22-28: Consider using useSetting for consistency.

The codebase uses useSetting('color.palette') in BorderAndShadowControls.js to fetch theme colors, but this component uses select('core/block-editor').getSettings(). For consistency and to follow newer WordPress patterns, consider using:

const themeColors = useSetting('color.palette');
const themeGradients = useSetting('color.gradients');

Based on learnings from related code in the codebase.

♻️ Proposed refactor using useSetting

+import { useSetting } from '@wordpress/block-editor';
+
 const ColorsControls = ({ attributes, setAttributes, device }) => {
 	const { colorsControls } = attributes;
 	const currentColors = colorsControls[device] || {};
 
-	// Fetch theme colors and gradients
-	const { themeColors, themeGradients } = useSelect((select) => {
-		const editorSettings = select('core/block-editor').getSettings();
-		return {
-			themeColors: editorSettings.colors,
-			themeGradients: editorSettings.gradients,
-		};
-	});
+	const themeColors = useSetting('color.palette');
+	const themeGradients = useSetting('color.gradients');

---

47-47: Consider explicit className handling.

The pattern className={isOpen && 'is-open'} works but is less clear than explicit alternatives. Consider using a ternary operator for better readability:

className={isOpen ? 'is-open' : ''}

Also applies to: 101-101, 216-216

---

30-319: Consider extracting common color control logic.

The three color controls (Text, Background, Link) share significant structural duplication:

• Similar Dropdown wrapper structure
• Repeated ColorPalette configuration (colors prop)
• Nearly identical onChange handler patterns

Consider extracting a reusable helper component or function to reduce duplication and improve maintainability.

Example refactor approach

const updateColorAttribute = (colorKey, colorValue) => {
  setAttributes({
    colorsControls: {
      ...colorsControls,
      [device]: {
        ...currentColors,
        [colorKey]: colorValue,
      },
    },
  });
};

const colorPaletteProps = {
  enableAlpha: true,
  colors: [{ colors: themeColors, name: __('Theme', 'wedocs') }],
};

Then reuse these in each control to eliminate repetition.

---

165-166: Good use of nullish coalescing for GradientPicker.

The explicit conversion to null (instead of undefined) for the GradientPicker value is good practice. Consider adding a brief comment explaining this difference from the ColorPalette components, as it may help future maintainers understand why this picker is treated differently.

---

322-346: Consider clarifying "Reset All" scope.

The "Reset All" button only resets colors for the current device, not all devices. The button label could be more explicit to avoid user confusion:

text={__('Reset All Colors', 'wedocs')}
// or
text={sprintf(__('Reset %s Colors', 'wedocs'), device)}

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8a5d8d0 and 98c5994.

📒 Files selected for processing (3)

• package.json
• src/blocks/TableOfContents/ColorsControls.js
• src/blocks/TableOfContents/controls/ListItems.js

🚧 Files skipped from review as they are similar to previous changes (2)

• package.json
• src/blocks/TableOfContents/controls/ListItems.js

🧰 Additional context used

🧬 Code graph analysis (1)

src/blocks/TableOfContents/ColorsControls.js (1)

src/blocks/commonControls/BorderAndShadowControls.js (1)

• themeColors (24-24)

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

# First, verify the file exists and check its imports
cat -n src/blocks/TableOfContents/ColorsControls.js | head -20

Repository: weDevsOfficial/wedocs-plugin

Length of output: 788

---

🏁 Script executed:

# Check usage of experimental components across the entire codebase
rg -n '__experimental(DropdownContentWrapper|HStack|TabPanel|Text|ZStack)' --type=js

Repository: weDevsOfficial/wedocs-plugin

Length of output: 1400

---

🏁 Script executed:

# Check if there are any tests for ColorsControls.js
fd -e test.js -e spec.js -e test.ts -e spec.ts | xargs rg -l 'ColorsControls' 2>/dev/null || echo "No test files found"

Repository: weDevsOfficial/wedocs-plugin

Length of output: 283

---

🏁 Script executed:

# Check WordPress package versions in package.json to understand component stability
cat package.json | grep -A5 '@wordpress'

Repository: weDevsOfficial/wedocs-plugin

Length of output: 710

---

TabPanel is not an experimental API; correct the component list.

The component uses four experimental WordPress components (DropdownContentWrapper, HStack, Text, ZStack), not five—TabPanel is imported without the __experimental prefix and is stable. While reliance on experimental APIs carries a small risk of future breaking changes, this pattern is consistent across the codebase (also used in BorderAndShadowControls, DimensionsControls, AiDocWriterPreview, and others), indicating an established approach. The existing ESLint disable comment and test coverage mitigate this concern.

🤖 Prompt for AI Agents

In @src/blocks/TableOfContents/ColorsControls.js around lines 1 - 14, Update the
import/notes so TabPanel is not treated as experimental: ensure TabPanel is
imported as the stable TabPanel (no __experimental prefix) and only
DropdownContentWrapper, HStack, Text, and ZStack use the __experimental* names;
remove TabPanel from any comment or component list that claims five experimental
components and leave the four actual experimental imports unchanged.

[coderabbitai]

Actionable comments posted: 8

🤖 Fix all issues with AI agents

In @src/blocks/AdvanceContributors/render.php:
- Around line 501-503: The call to render_wedocs_advance_contributors_block(
$attributes, $content, $block ) discards the function's returned $output; either
echo the return value where it’s invoked or change the function to directly
print (echo) instead of returning; locate the function
render_wedocs_advance_contributors_block and either (a) replace the bare call
with echo render_wedocs_advance_contributors_block( $attributes, $content,
$block ); or (b) modify the function so it outputs $output (echo) before
returning or returns void, ensuring the rendered content is actually sent to the
response.
- Line 458: The fallback uses PHP date() which ignores WP timezone; change the
assignment for $last_modified so the fallback uses wp_date() with a
timezone-aware timestamp: replace the date($date_format_string) call with
wp_date($date_format_string, current_time('timestamp')) while keeping the
existing use of get_the_modified_date($date_format_string, $post) for the post
case (refer to the $last_modified variable and functions wp_date(),
current_time(), and get_the_modified_date()).
- Around line 116-289: The nested definition of generate_responsive_css inside
render_wedocs_advance_contributors_block causes a "Cannot redeclare" fatal error
when the outer function runs multiple times; fix by moving
generate_responsive_css out of render_wedocs_advance_contributors_block (define
it at file scope) or, as a quick patch, wrap its declaration with a
function_exists('generate_responsive_css') check so it’s only defined once and
then update any calls inside render_wedocs_advance_contributors_block to use
that single global function.

In @src/blocks/Contributors/render.php:
- Line 336: The $last_modified assignment uses PHP's date() which ignores WP
timezone settings; update the fallback to use wp_date($date_format_string) so
that $last_modified = $post ? get_the_modified_date($date_format_string, $post)
: wp_date($date_format_string); ensuring timezone-aware formatting; keep
get_the_modified_date(...) unchanged.
- Around line 104-155: The 'all' branch misuses get_post_field and allows
duplicates: treat the main author and wedocs_contributors consistently by
retrieving the main author with get_post_field('post_author', $post->ID) and
normalizing wedocs_contributors into an array before iterating; build a unique
contributor_ids array (or use array_unique) to prevent duplicate additions, push
each contributor only if not already seen, and use get_userdata() for each id;
update variables $author_id/$authors to reflect these types and remove the
redundant push of $author_id that causes duplicates.

In @src/blocks/DocsGrid/render.php:
- Around line 176-182: The code sets $args['posts_per_page'] to the string '-1'
when $docs_per_page === 'all'; change that to the integer -1 so WP_Query
receives an integer (update the assignment in the render logic where
$args['posts_per_page'] is set for the 'all' branch); ensure $args['paged']
remains 1 in that branch.
- Around line 325-328: The file defines render_wedocs_docs_grid() but never
invokes it; add a top-level call to render_wedocs_docs_grid($attributes,
$content, $block) at the end of render.php (matching the Contributors/render.php
pattern) so the file-level render entrypoint executes when WordPress includes
the file, or alternatively update the block registration to supply
'render_callback' => 'render_wedocs_docs_grid' so WordPress will call that
function; ensure you pass the expected parameters ($attributes, $content,
$block) when invoking.

In @src/blocks/HelpfulModal/render.php:
- Line 107: The $modal_styles variable is declared but never populated—mirror
the pattern used for $modal_content_styles and $heading_styles by building
$modal_styles with sprintf() (e.g., include modal container CSS properties you
need: width, max-width, position, background, padding, etc.) before it is passed
into the JS payload so view.js:215-216 can use it; alternatively, if no
container-level styles are required, remove $modal_styles from the payload or
add a brief comment explaining it is intentionally empty and optional. Ensure
you reference and update the $modal_styles variable in
src/blocks/HelpfulModal/render.php where the other style vars are constructed so
the JS consumer receives meaningful data.

🧹 Nitpick comments (8)

src/blocks/DocsGrid/render.php (3)

187-187: Remove unused $total_pages variable or implement pagination controls.

The variable is assigned but never used. If pagination is intended, the pagination UI should be implemented; otherwise, remove this unused variable.

Proposed fix (if pagination is not needed)

     $docs_query = new WP_Query($args);
     $docs = $docs_query->posts;
-    $total_pages = $docs_query->max_num_pages;

---

232-233: Remove unused $total_articles variable.

This variable is initialized to 0 but never used or incremented. As flagged by static analysis.

Proposed fix

                 $sections = get_posts($sections_query_args);
-                $total_articles = 0;
                 ?>

---

188-216: Inline JavaScript should use wp_add_inline_script or be properly escaped.

Outputting raw JavaScript via echo $toggle_script bypasses WordPress's script handling and could pose maintenance challenges. Consider registering this script properly or at minimum, ensure the output is late enough in the render to avoid issues.

src/blocks/Contributors/render.php (2)

160-169: Mock contributor fallback may expose unexpected data in production.

Displaying a "Demo Author" with a fake email and ID=1 (which is typically the admin user) could be confusing in production. Consider returning an empty state message instead.

Proposed alternative

     if (empty($contributors)) {
-        // For demo purposes, add mock contributors if none found
-        $contributors = [
-            (object) [
-                'ID' => 1,
-                'display_name' => 'Demo Author',
-                'user_email' => 'demo@example.com'
-            ]
-        ];
+        // Return empty if no contributors found
+        return '<div class="wedocs-contributors wedocs-contributors--empty">' . 
+               esc_html__('No contributors found.', 'wedocs') . '</div>';
     }

---

383-395: Inline CSS is duplicated on every block render.

The responsive CSS and hover styles are output inline for each block instance. For pages with multiple contributor blocks, this creates duplicate CSS. Consider enqueueing these shared styles once via wp_add_inline_style().

src/blocks/AdvanceContributors/render.php (2)

10-14: Missing function_exists guard - inconsistent with other render files.

Both DocsGrid/render.php and Contributors/render.php wrap their render functions with function_exists() checks. This file is missing that guard, which could cause issues if the file is included multiple times.

Proposed fix

 if (!defined('ABSPATH')) {
     exit;
 }
+
+if ( ! function_exists( 'render_wedocs_advance_contributors_block' ) ) {
 function render_wedocs_advance_contributors_block($attributes, $content, $block) {

And close the guard at the end of the file (after line 502):

     return $output;
 }
+}
 render_wedocs_advance_contributors_block( $attributes, $content, $block );

---

104-113: Mock contributor fallback - same concern as Contributors block.

Displaying mock data with ID=1 in production could be confusing or misleading. Consider a more graceful empty state.

src/blocks/HelpfulModal/render.php (1)

66-142: Consider extracting a style-building helper function.

The style-building code follows a consistent pattern with multiple sprintf calls. While the current implementation is correct and safe (proper use of esc_attr()), extracting this into a reusable helper function would reduce code duplication and improve maintainability.

♻️ Example refactor using a helper function

function build_css_properties($properties) {
    $css = [];
    foreach ($properties as $property => $value) {
        if (is_array($value)) {
            foreach ($value as $key => $val) {
                $css[] = sprintf('%s-%s: %s', $property, $key, esc_attr($val));
            }
        } else {
            $css[] = sprintf('%s: %s', $property, esc_attr($value));
        }
    }
    return implode('; ', $css) . ';';
}

// Usage example:
$container_styles = build_css_properties([
    'background-color' => $container_background_color,
    'padding' => $container_padding,
    'margin' => $container_margin,
    // ... more properties
]);

Note: This is an optional optimization and the current implementation is functionally correct.

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 98c5994 and 0275c9f.

📒 Files selected for processing (5)

• src/blocks/AdvanceContributors/render.php
• src/blocks/Contributors/render.php
• src/blocks/DocsGrid/render.php
• src/blocks/HelpfulModal/render.php
• src/blocks/TableOfContents/Inspector.js

🚧 Files skipped from review as they are similar to previous changes (1)

• src/blocks/TableOfContents/Inspector.js

🧰 Additional context used

🧬 Code graph analysis (4)

src/blocks/DocsGrid/render.php (2)

src/blocks/DocsGrid/save.js (1)

• attributes (4-16)

src/blocks/DocsGrid/edit.js (1)

• attributes (20-48)

src/blocks/Contributors/render.php (1)

src/blocks/helpers/block-styles.php (8)

• wedocs_build_background_styles (134-152)
• wedocs_build_spacing_styles (58-70)
• wedocs_build_border_styles (81-101)
• wedocs_build_shadow_styles (109-123)
• wedocs_build_element_styles (179-228)
• wedocs_generate_block_id (160-162)
• wedocs_styles_to_css (236-242)
• wedocs_generate_responsive_css (251-281)

src/blocks/HelpfulModal/render.php (2)

src/blocks/TableOfContents/Inspector.js (1)

• attributes (16-38)

src/blocks/HelpfulModal/edit.js (1)

• attributes (55-104)

src/blocks/AdvanceContributors/render.php (4)

src/blocks/TableOfContents/Inspector.js (1)

• attributes (16-38)

src/blocks/TableOfContents/view.js (1)

• content (153-153)

src/components/Documentations/ParentDocs.js (1)

• contributors (54-58)

src/blocks/helpers/block-helpers.js (1)

• border (173-173)

🪛 PHPMD (2.15.0)

src/blocks/DocsGrid/render.php

187-187: Avoid unused local variables such as '$total_pages'. (undefined)

(UnusedLocalVariable)

---

232-232: Avoid unused local variables such as '$total_articles'. (undefined)

(UnusedLocalVariable)

src/blocks/Contributors/render.php

16-16: Avoid unused parameters such as '$content'. (undefined)

(UnusedFormalParameter)

---

16-16: Avoid unused parameters such as '$block'. (undefined)

(UnusedFormalParameter)

src/blocks/AdvanceContributors/render.php

14-14: Avoid unused parameters such as '$content'. (undefined)

(UnusedFormalParameter)

---

14-14: Avoid unused parameters such as '$block'. (undefined)

(UnusedFormalParameter)

🔇 Additional comments (9)

src/blocks/DocsGrid/render.php (2)

9-12: LGTM - ABSPATH guard properly implemented.

The direct access prevention is correctly placed at the top of the file.

---

14-42: LGTM - Pagination style function with proper escaping.

The get_pagination_style_tag function correctly uses esc_attr() for all CSS variable values and is properly guarded against redeclaration.

src/blocks/Contributors/render.php (1)

10-13: LGTM - ABSPATH guard properly implemented.

src/blocks/AdvanceContributors/render.php (1)

52-99: LGTM - Contributor fetching logic is well-structured.

The switch statement properly handles all display modes with appropriate null checks and deduplication for revision authors.

src/blocks/HelpfulModal/render.php (5)

1-8: LGTM!

The direct access prevention check follows WordPress best practices.

---

10-64: LGTM!

The attribute extraction pattern is consistent and provides sensible defaults for all configurable properties. The array-based attributes (padding, margin, border, typography) are properly structured with fallbacks.

---

157-175: LGTM!

The modal data array is well-structured for JavaScript consumption. All values are properly sourced from the block attributes. (Note: The empty $modal_styles issue is addressed in a separate comment.)

---

177-204: LGTM!

The HTML output follows WordPress security best practices:

• User-controlled text is escaped with esc_html()
• Attributes are escaped with esc_attr()
• Translation functions are used correctly with proper placeholders
• JSON data is safely encoded with wp_json_encode()
• Conditional rendering for the last updated timestamp is implemented correctly

---

144-155: Current approach is acceptable for single-block usage.

The get_help_icon_svg function is only used within this HelpfulModal block and not shared across other blocks, making the inline definition with function_exists guard appropriate. No relocation is necessary.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Critical: Nested function causes fatal error on multiple block renders.

The generate_responsive_css function is defined inside render_wedocs_advance_contributors_block. PHP will attempt to redefine this function each time the outer function is called, causing a "Cannot redeclare" fatal error when multiple AdvanceContributors blocks are on the same page.

Move this function outside the render function or wrap it with a function_exists guard.

Option 1: Move function outside (recommended)

+// Helper function to generate responsive CSS - defined outside render function
+if ( ! function_exists( 'generate_responsive_css' ) ) {
+    function generate_responsive_css($block_id, $controls, $device_suffix = '') {
+        // ... function body ...
+    }
+}
+
 function render_wedocs_advance_contributors_block($attributes, $content, $block) {
     // ... existing code ...
     
-    // Helper function to generate responsive CSS
-    function generate_responsive_css($block_id, $controls, $device_suffix = '') {
-        // ... function body ...
-    }

Option 2: Wrap with function_exists guard (quick fix)

     // Helper function to generate responsive CSS
+    if ( ! function_exists( 'generate_responsive_css' ) ) {
     function generate_responsive_css($block_id, $controls, $device_suffix = '') {
         // ... existing function body ...
     }
+    }

🤖 Prompt for AI Agents

In @src/blocks/AdvanceContributors/render.php around lines 116 - 289, The nested
definition of generate_responsive_css inside
render_wedocs_advance_contributors_block causes a "Cannot redeclare" fatal error
when the outer function runs multiple times; fix by moving
generate_responsive_css out of render_wedocs_advance_contributors_block (define
it at file scope) or, as a quick patch, wrap its declaration with a
function_exists('generate_responsive_css') check so it’s only defined once and
then update any calls inside render_wedocs_advance_contributors_block to use
that single global function.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Use wp_date() instead of date() for timezone-aware formatting.

Same issue as in Contributors/render.php - native date() ignores WordPress timezone settings.

Proposed fix

-        $last_modified = $post ? get_the_modified_date($date_format_string, $post) : date($date_format_string);
+        $last_modified = $post ? get_the_modified_date($date_format_string, $post) : wp_date($date_format_string);

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	$last_modified = $post ? get_the_modified_date($date_format_string, $post) : date($date_format_string);
	$last_modified = $post ? get_the_modified_date($date_format_string, $post) : wp_date($date_format_string);

🤖 Prompt for AI Agents

In @src/blocks/AdvanceContributors/render.php at line 458, The fallback uses PHP
date() which ignores WP timezone; change the assignment for $last_modified so
the fallback uses wp_date() with a timezone-aware timestamp: replace the
date($date_format_string) call with wp_date($date_format_string,
current_time('timestamp')) while keeping the existing use of
get_the_modified_date($date_format_string, $post) for the post case (refer to
the $last_modified variable and functions wp_date(), current_time(), and
get_the_modified_date()).

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Function return value is discarded.

The function returns $output but line 503 calls it without capturing or echoing the result. The rendered content will be lost.

Proposed fix

     return $output;
 }
-render_wedocs_advance_contributors_block( $attributes, $content, $block );
+echo render_wedocs_advance_contributors_block( $attributes, $content, $block );

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	return $output;
	}
	render_wedocs_advance_contributors_block( $attributes, $content, $block );
	return $output;
	}
	echo render_wedocs_advance_contributors_block( $attributes, $content, $block );

🤖 Prompt for AI Agents

In @src/blocks/AdvanceContributors/render.php around lines 501 - 503, The call
to render_wedocs_advance_contributors_block( $attributes, $content, $block )
discards the function's returned $output; either echo the return value where
it’s invoked or change the function to directly print (echo) instead of
returning; locate the function render_wedocs_advance_contributors_block and
either (a) replace the bare call with echo
render_wedocs_advance_contributors_block( $attributes, $content, $block ); or
(b) modify the function so it outputs $output (echo) before returning or returns
void, ensuring the rendered content is actually sent to the response.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Logic error in 'all' display mode - duplicate contributors and type mismatch.

The 'all' case has several issues:

1. Line 127-128: get_post_field('wedocs_contributors', ...) returns a post field value, then array_values($author_id) is called assuming it's an array - this will likely fail or produce unexpected results.
2. Lines 134-136 add the $author_id again after already iterating through $authors, causing potential duplicates.
3. The logic between 'main_author' (line 106) and 'all' (line 127) is inconsistent - both use 'wedocs_contributors' but handle the result differently.

Compare with AdvanceContributors/render.php lines 74-98 which uses get_post_field('post_author', ...) consistently.

Suggested fix aligning with AdvanceContributors pattern

         case 'all':
         default:
-            // Get all contributors who have edited the post
-            $author_id = get_post_field('wedocs_contributors', $post->ID);
-            $authors = array_values($author_id); // return auhtors id.
-            foreach($authors as $author){
-                $contributors[]= get_userdata($author);
-            }
-
-
-            if ($author_id && ($author_user = get_userdata($author_id))) {
-                $contributors[] = $author_user;
+            // Get post author
+            $author_id = get_post_field('post_author', $post->ID);
+            if ($author_id && ($author_user = get_userdata($author_id))) {
+                $contributors[] = $author_user;
             }

             // Get additional contributors from post meta or revisions
             if ($post) {
                 $revisions = wp_get_post_revisions($post->ID);
                 $contributor_ids = [$author_id];

                 foreach ($revisions as $revision) {
                     $revision_author = get_post_field('post_author', $revision->ID);
                     if (!in_array($revision_author, $contributor_ids)) {
                         $contributor_ids[] = $revision_author;
                         $user = get_userdata($revision_author);
                         if ($user) {
                             $contributors[] = $user;
                         }
                     }
                 }
             }
             break;

🤖 Prompt for AI Agents

In @src/blocks/Contributors/render.php around lines 104 - 155, The 'all' branch
misuses get_post_field and allows duplicates: treat the main author and
wedocs_contributors consistently by retrieving the main author with
get_post_field('post_author', $post->ID) and normalizing wedocs_contributors
into an array before iterating; build a unique contributor_ids array (or use
array_unique) to prevent duplicate additions, push each contributor only if not
already seen, and use get_userdata() for each id; update variables
$author_id/$authors to reflect these types and remove the redundant push of
$author_id that causes duplicates.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Use wp_date() instead of date() for timezone-aware formatting.

The native date() function doesn't respect WordPress timezone settings. Use wp_date() for consistent date formatting.

Proposed fix

-        $last_modified = $post ? get_the_modified_date($date_format_string, $post) : date($date_format_string);
+        $last_modified = $post ? get_the_modified_date($date_format_string, $post) : wp_date($date_format_string);

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	$last_modified = $post ? get_the_modified_date($date_format_string, $post) : date($date_format_string);
	$last_modified = $post ? get_the_modified_date($date_format_string, $post) : wp_date($date_format_string);

🤖 Prompt for AI Agents

In @src/blocks/Contributors/render.php at line 336, The $last_modified
assignment uses PHP's date() which ignores WP timezone settings; update the
fallback to use wp_date($date_format_string) so that $last_modified = $post ?
get_the_modified_date($date_format_string, $post) :
wp_date($date_format_string); ensuring timezone-aware formatting; keep
get_the_modified_date(...) unchanged.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Use integer -1 instead of string '-1' for posts_per_page.

WordPress's WP_Query expects an integer for posts_per_page. Using a string may cause unexpected behavior.

Proposed fix

     if ($docs_per_page !== 'all') {
         $args['posts_per_page'] = intval($docs_per_page);
         $args['paged'] = $current_page;
     } else {
-        $args['posts_per_page'] = '-1';
+        $args['posts_per_page'] = -1;
         $args['paged'] = 1;
     }

🤖 Prompt for AI Agents

In @src/blocks/DocsGrid/render.php around lines 176 - 182, The code sets
$args['posts_per_page'] to the string '-1' when $docs_per_page === 'all'; change
that to the integer -1 so WP_Query receives an integer (update the assignment in
the render logic where $args['posts_per_page'] is set for the 'all' branch);
ensure $args['paged'] remains 1 in that branch.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Search for how render_wedocs_docs_grid is being called
rg -n "render_wedocs_docs_grid" --type php

Repository: weDevsOfficial/wedocs-plugin

Length of output: 247

---

🏁 Script executed:

#!/bin/bash
# Find block registration files
fd -e json -e php "block|register" src/blocks/DocsGrid/ || true
cat src/blocks/DocsGrid/*.json 2>/dev/null || true

# Check Contributors/render.php to see the pattern
if [ -f src/blocks/Contributors/render.php ]; then
  tail -20 src/blocks/Contributors/render.php
fi

# Look for block registration patterns
rg -n "render_callback|register_block_type" --type php src/blocks/ -A 3 | head -50

Repository: weDevsOfficial/wedocs-plugin

Length of output: 4187

---

🏁 Script executed:

#!/bin/bash
# Get the full render.php file
wc -l src/blocks/DocsGrid/render.php
cat -n src/blocks/DocsGrid/render.php

Repository: weDevsOfficial/wedocs-plugin

Length of output: 18192

---

Add invocation of render_wedocs_docs_grid() at the file level or reconfigure block registration.

The render_wedocs_docs_grid() function is declared (lines 44–328) but never invoked. With block.json specifying "render": "file:./render.php", WordPress includes this file but does not automatically call named functions. The block will fail to render without a top-level invocation. Either call the function with block attributes at the end of render.php (following the Contributors/render.php pattern), or configure a render_callback in block registration.

🤖 Prompt for AI Agents

In @src/blocks/DocsGrid/render.php around lines 325 - 328, The file defines
render_wedocs_docs_grid() but never invokes it; add a top-level call to
render_wedocs_docs_grid($attributes, $content, $block) at the end of render.php
(matching the Contributors/render.php pattern) so the file-level render
entrypoint executes when WordPress includes the file, or alternatively update
the block registration to supply 'render_callback' => 'render_wedocs_docs_grid'
so WordPress will call that function; ensure you pass the expected parameters
($attributes, $content, $block) when invoking.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

# First, let's examine the render.php file to understand the context
cat -n src/blocks/HelpfulModal/render.php | sed -n '100,180p'

Repository: weDevsOfficial/wedocs-plugin

Length of output: 3849

---

🏁 Script executed:

# Search for any modalStyles usage in JS files
rg -n "modalStyles" --type=js -g "**/HelpfulModal/**"

Repository: weDevsOfficial/wedocs-plugin

Length of output: 420

---

🏁 Script executed:

# Also check if $modal_styles is used anywhere else in PHP
rg -n "\$modal_styles" src/blocks/HelpfulModal/

Repository: weDevsOfficial/wedocs-plugin

Length of output: 54

---

Unused CSS initialization for modal element.

The $modal_styles variable is initialized as an empty string on line 107 but never populated, unlike other style variables ($modal_content_styles, $heading_styles, etc.) which are built via sprintf() calls. While modalStyles is passed to JavaScript and checked in view.js:215-216, it remains empty. Either populate this variable with appropriate modal styles (following the pattern of other style variables) or document why it's intentionally left empty as an optional property.

🤖 Prompt for AI Agents

In @src/blocks/HelpfulModal/render.php at line 107, The $modal_styles variable
is declared but never populated—mirror the pattern used for
$modal_content_styles and $heading_styles by building $modal_styles with
sprintf() (e.g., include modal container CSS properties you need: width,
max-width, position, background, padding, etc.) before it is passed into the JS
payload so view.js:215-216 can use it; alternatively, if no container-level
styles are required, remove $modal_styles from the payload or add a brief
comment explaining it is intentionally empty and optional. Ensure you reference
and update the $modal_styles variable in src/blocks/HelpfulModal/render.php
where the other style vars are constructed so the JS consumer receives
meaningful data.