How to Edit Information of an Elementor Widget or Gutenberg Block?

What It Does

The Edit Information screen lets you update a cloud-uploaded Elementor widget or Gutenberg block’s title, description, assets, visibility, and other metadata from the WDesignKit app, without re-pushing the widget’s code.

Requirement — this feature is part of WDesignKit, make sure it’s installed & activated to enjoy all its powers.

Why It Matters

A widget’s metadata is what other users (or you, later) see before deciding to use it: its title, description, preview, and tags. Being able to correct or improve that information without touching the widget’s code means you can fix a typo, add a demo link, or reclassify a widget in seconds.

What You Get

• Full control over a cloud widget’s title, description, short introduction, demo URL, and tutorial URL.
• A way to declare external JS/CSS/jQuery dependencies and their file sizes.
• Visibility, category, tag, publish date, and featured image controls in one place.

Benefits

Editing metadata separately from code means a quick correction doesn’t require a full re-push, and keeping a widget’s listing information accurate makes it easier to find and trust, whether it’s private in your workspace or public on the marketplace.

Capabilities

• Title, Description, Short Introduction — the widget’s listing text.
• Demo URL, Tutorial URL — optional links to a live preview and a walkthrough.
• Features — an optional list of the widget’s feature highlights.
• External JS / CSS / jQuery files — declare each file’s name and size (KB); add more with the corresponding +Add more button.
• Status — Private (only you, shareable through a workspace) or Public (visible to all WDesignKit users); private by default.
• Date, Page Builder, Category, Tags, Featured Image — the remaining listing and organization fields.

How It Works

Editing information is a metadata-only update against the widget’s existing cloud record — it does not repackage or re-upload the widget’s PHP/JSON/CSS/JS files, which is why the widget has to already be uploaded to the WDesignKit server before this screen is available. Saving writes the changes straight to that cloud record, and they appear immediately on the widget’s public page on the WDesignKit website if the widget is set to Public.

How to Use It

Note: to edit the information of your widget or block, it must already be uploaded to the WDesignKit server. See “How to Export Elementor Widget or Gutenberg Block From Your Site to Cloud” if you haven’t pushed it yet.

1. Log into the WDesignKit app, then go to Widgets > Uploaded.
2. Find the widget or block you want to edit, click the three dots, then click Edit.
3. On the edit page, update whichever fields need changing: Title, Description, Short Introduction, Demo URL, Tutorial URL, Features, external JS/CSS/jQuery files, Status, Date, Page Builder, Category, Tags, or Featured Image.
4. Click Save to update the information.

Your updates show up in the widget’s single page on the WDesignKit website.

Use Cases

• You uploaded a widget with a placeholder title/description and want to write a real one.
• You want to switch a widget from Private to Public to share it on the marketplace.
• You added an external JS/CSS dependency after the initial push and need to declare it for anyone reusing the widget.

Limitations

• This screen only edits metadata — code changes still require re-pushing the widget, not the Edit Information form.
• The widget must already exist on the WDesignKit cloud; local-only widgets have nothing to edit here yet.
• Switching Status to Public makes the widget visible to all WDesignKit users; there’s no partial/limited-audience public option beyond workspace sharing.

Troubleshooting

• Edit option isn’t available for a widget — the widget hasn’t been pushed to the cloud yet; push it first, then Edit becomes available under Widgets > Uploaded.
• Saved changes don’t show on the widget’s public page — check the Status field; changes to a Private widget only show to you and anyone it’s shared with through a workspace, not on the public marketplace page.
• Added an external JS/CSS file but users report it’s missing — declaring the file name and size here documents the dependency for the listing, it does not upload the file itself; confirm the asset is actually bundled in the widget’s own files before publishing.

Sourcing note: the three Troubleshooting items above are derived from the documented Edit Information workflow and its stated fields/requirements (this page), not from a searched support-ticket sample this run — disclosed rather than presented as ticket-verified.