FTP EA Ex Block 4.1.0

Here are simple step‑by‑step ways to add an image on this Add Page screen (Gutenberg/block editor plus some custom blocks shown):

Option A — Use the built‑in Image block

1. Click the + (Add block) button where you want the image (or from the top toolbar).
2. In the block inserter choose Media → Image (you can type “Image” to quickly filter).
3. Either:
   • Click Upload to add a new file from your computer, or
   • Click Media Library to pick an existing image, or
   • Drag & drop an image into the block area.
4. After inserting, use the block toolbar and settings panel (right side) to:
   • Set alignment (left/center/right/wide/full), size, and crop,
   • Add Alt text, title and caption,
   • Add a link (none / media file / custom URL),
   • Adjust width, dimensions and other style settings.
5. Save or Update the page.

Option B — Use Gallery, Cover, or Media & Text blocks

• For multiple images, choose Gallery.
• For an image with overlay text, choose Cover.
• For side-by-side image + text, choose Media & Text.

Option C — Use theme/product specific blocks shown on this page

• You also have a “SMART IMAGE” block (and plugin blocks) in the inserter. Use it the same way: insert that block and then upload/select the image — these blocks may include extra styling or options specific to your theme/plugin.

Extra tips

• To set the page’s Featured Image (if needed), open the Document settings (right sidebar) → Featured image → Set featured image.
• Keyboard: press / in an empty block to quickly insert a block by name.
• Always add meaningful Alt text for accessibility and SEO.

If you tell me whether you want a single image, gallery, featured image, or a Smart Image from a plugin, I can give more precise steps for that case.

You’re on the WP editor page that shows the block inserter (MEDIA → Video). Here are simple ways to add a video from that view.

A. Using the Gutenberg (block) editor

1. Edit the page/post. (You’re already on the Add Page / post editor.)
2. Click the + block inserter where you want the video.
3. Under MEDIA choose “Video” (you can also type “Video” in the search box).
4. Insert the block and choose one of:
   • Upload — upload a video file from your computer.
   • Media Library — select a file already in WordPress.
   • Insert from URL — paste a direct video file URL.
5. Optional block settings (right sidebar): set poster image (cover), autoplay, loop, muted, playback controls (depends on theme/WordPress version).
6. Save/Update the page.

Notes:

• If you want to insert a YouTube/Vimeo link, use the “YouTube” or “Vimeo” embed block (or the generic “Embed” block) instead of the Video block — paste the video page URL and WordPress will embed it.
• For large self-hosted files prefer hosting externally (YouTube/Cloud storage) to avoid bandwidth and performance issues.

B. Using Elementor (if you prefer visual builder)

1. Click “Edit with Elementor” at the top of the editor.
2. In Elementor’s widget panel, drag the “Video” widget into the page.
3. In the widget settings, choose source (YouTube, Vimeo, Self Hosted), paste URL or select media, set player options (autoplay, loop, controls) and style.
4. Update the page.

If you tell me whether you want a self-hosted file or an embedded YouTube/Vimeo video, I can give step-by-step with exact clicks for that option.

Here are simple ways to add a map on the page you’re editing (Gutenberg block editor / Elementor), plus a plugin option:

A. Using Google Maps embed (works in Gutenberg or Classic Editor)

1. In Google Maps find the location, click Share → Embed a map → Copy the iframe HTML.
2. In your WP editor:
   • Gutenberg: click + → search “Custom HTML” → paste the iframe → Preview.
   • Classic editor: switch to Text (HTML) tab and paste the iframe.
3. Adjust width/height in the iframe (use width=”100%” for responsiveness). Example: <iframe src=”…” width=”100%” height=”450″ style=”border:0;” allowfullscreen=”” loading=”lazy”></iframe>

B. Using the Gutenberg “Embed” or “HTML” alternatives

• You can also use the “Embed” block → “Custom” (for some map services) or the “Shortcode” block if you have a map shortcode from a plugin.

C. Using Elementor

1. Edit with Elementor → find the “Google Maps” widget (or “HTML” widget).
2. Drag the Google Maps widget and enter the place or API settings, or drag HTML widget and paste the iframe.
3. Configure height, zoom and responsive settings in the widget panel.

D. Using a plugin (recommended for markers, multiple maps, styling, or API keys)

• Install a plugin like “WP Google Maps”, “MapPress”, “Leaflet Map”, or a Maps widget provided by your theme/elementor add-on.
• Activate, create a map in the plugin settings, then insert via Gutenberg block, shortcode, or Elementor widget provided by that plugin.

Tips

• If using Google Maps API features (dynamic maps), you’ll need an API key and a plugin/Elementor Pro widget.
• For mobile responsiveness, prefer width=”100%” and control height with CSS or widget settings.
• If you want weather/interactive maps, your admin already has “Weather Map by OWM” and “Radar Map by Windy” blocks (visible in the Location Weather block group) — you can drag those if they fit your needs.

If you tell me whether you’re using Gutenberg or Elementor and whether you want a simple embedded map or advanced features (markers, multiple locations), I’ll give exact steps for your case.

Here’s a concise step-by-step guide to contributing (submitting) a plugin to the WordPress Plugin Directory.

1. Meet the basics

• License: Your plugin must be GPL-compatible (or public-domain) and include a license header in files.
• No obfuscated/encoded code. All code must be auditable.
• Follow WordPress coding standards, security best practices (sanitize/escape/prepare), and avoid including premium/licensed third‑party code without proper rights.

1. Prepare your plugin files

• Main plugin PHP file with plugin header (Plugin Name, Plugin URI, Description, Version, Author, Author URI, License, Text Domain).
• Use unique prefix for functions, classes and DB keys.
• Internationalization: load_plugin_textdomain and .pot/.po/.mo files.
• Use proper read/write behavior (avoid writing into core/theme folders).
• Include uninstall.php or register_uninstall_hook to clean up options if appropriate.

1. Create a readme.txt (required)

• Use the WordPress readme.txt format (required sections: == Description ==, == Installation ==, == Frequently Asked Questions ==, == Screenshots ==, == Changelog ==, == Upgrade Notice ==, etc.).
• Add accurate tested up to and stable tag entries.
• Use proper tags and short description.

1. Provide assets (recommended)

• Icons: icon-128×128.png and icon-256×256.png (or the currently required sizes).
• Banner and screenshots to make the plugin listing attractive and informative.
• Clear description, feature list, and FAQ entries.

1. Test thoroughly

• Test on multiple WP versions and with latest PHP versions.
• Check for PHP notices/warnings, JS console errors.
• Run security checks (WPScan/linter/static analyzers), and ensure nonces & capability checks where needed.

1. Create a WordPress.org account

• If you don’t already have one, register at WordPress.org.

1. Submit the plugin

• Go to the Plugin Directory “Add New Plugin” (Add Your Plugin / Plugin upload) page on WordPress.org and submit the ZIP of your plugin or the plugin slug and repository info.
• Provide the assets, description, and readme content when prompted.

1. After submission — review and SVN

• WordPress.org reviewers will review your submission. They may ask for changes — respond promptly.
• If approved you’ll be given a Subversion (SVN) repository URL for your plugin slug.
• Use SVN to push future updates. (You can also use tools that bridge Git to SVN if desired.) Basic SVN flow:
  • svn checkout https://plugins.svn.wordpress.org/your-plugin-slug
  • copy files into trunk/, commit: svn commit -m “Initial commit”
  • create tags for each release: svn copy trunk tags/1.0.0 -m “Tagging 1.0.0”

1. Maintain the plugin

• Keep your readme’s Tested up to and stable tag updated.
• Release security patches quickly; respond to support threads.
• Follow the directory’s guidelines for attribution, trademarks, and bundled libraries.

1. Helpful resources

• WordPress Plugin Developer Handbook (search “Plugin Developer Handbook WordPress”).
• WordPress.org Plugin Directory submission page (search “Add New Plugin WordPress.org”).

If you want, I can:

• Check your plugin header/readme text if you paste it here.
• Generate a readme.txt template for you.
• Show an example SVN commit sequence with your plugin slug.