sharelink

<p>WP Composer Sync is a WordPress plugin that keeps a WordPress installation’s composer.json synchronised with the plugins installed.</p>
<h3>Usage</h3>
<p>Once installed the plugin should be largely set and forget, however there a couple of gotchas.</p>
<p>1) Commercial plugins that are not available from the WordPress.org plugins repository <strong>will still be added</strong> you will need to manually modify the repository (eg. wpackagist, wp-premium or using a custom installer or repository) or add your custom plugins first. WP Composer Sync will then honor these repositories and keep them synchronised as well.<br />
2) When composer installs a package, it completely empties the target directory before installing the new files. As such, the WordPress path should be designated for WordPress core files only, as anything else (e.g. plugins, themes, and wp-config.php) will be wiped away on install or update. It is recommended that you <em>keep your wp-config.php file in the parent directory of the WordPress path</em> (WordPress can find it there automatically) and <em>replace the wp-content directory with a symlink</em> to your real wp-content folder. See  <a href="https://github.com/balbuf/composer-wp" title="Balbuf's Composer-WP" rel="nofollow ugc">link</a> for more details.<br />
3) Compposer require versioning wildcards (eg. *, 1.*, etc) will not be honoured (as WordPress does not adhere to this). They will be replaced by the exact version number in use by WordPress.</p>
<h3>About</h3>
<h3>Why?</h3>
<p>Composer is a great way to manage WordPress and its plugins. However in real life it runs the risk of becoming outdated with the actual contents of the website when admin users are installing plugins via wp-admin or S/FTP.</p>
<h3>How?</h3>
<p>Using WordPress’s “plugins_loaded” action and <a href="https://github.com/balbuf/composer-wp" title="Balbuf's Composer-WP" rel="nofollow ugc">link</a>, this plugin will check your composer.json file for any outdated or unfound plugins and will automatically add them to the require section.</p>
<h4>Roadmap</h4>
<p>The plugin is production ready however there are some additional functions and features which will be added in the future:</p>
<p>1) Add ability to select bewteen https://github.com/balbuf/composer-wp and wpackagist<br />
2) Currently only syncs plugin and wordpress core, add ability to sync themes<br />
3) Research some ways to monitor plugin-uploads and changes more effectively (eg. <a href="https://codex.wordpress.org/Plugin_API/Action_Reference/upgrader_process_complete" title="Upgrader_Process_complete" rel="nofollow ugc">link</a> <a href="https://github.com/WordPress/WordPress/blob/master/wp-admin/includes/class-plugin-upgrader.php" title="2" rel="nofollow ugc">link</a>,  <a href="https://www.sitepoint.com/wordpress-plugin-updates-right-way/" title="Wordpress Updates" rel="nofollow ugc">link</a> and <a href="https://codex.wordpress.org/Creating_Tables_with_Plugins#Adding_an_Upgrade_Function" title="Adding an upgrade function" rel="nofollow ugc">link</a> or Transients <a href="https://code.tutsplus.com/tutorials/a-guide-to-the-wordpress-http-api-automatic-plugin-updates--wp-25181" title="1" rel="nofollow ugc">link</a> <a href="https://stackoverflow.com/questions/32196219/my-plugin-not-updating-properly-issue-with-upgrader-process-complete/50914655#50914655" title="2" rel="nofollow ugc">link</a> or <a href="https://wordpress.stackexchange.com/questions/123732/get-latest-plugin-version-from-wp-api" title="Plugins API" rel="nofollow ugc">link</a>)</p>


WP Composer Sync

WP Composer Sync is a Wordpress plugin that keeps a Wordpress installation's composer.json synchronised with the plugins installed.

sbouey

<p>The Falang for WPBakery plugin makes your WPBakery page translation simpler. You need to have your site working with the Falang system for translation.</p>
<p>You don’t have to duplicate the page anymore to translate it, just translate only what is necessary. It’s easier to maintain and all parameters are the same for all languages.</p>
<h4>Free vs Pro</h4>
<p>Free verion support vc_btn,vc_column,vc_message,vc_section,vc_tta_section</p>
<p>Pro version support</p>
<ul>
<li>
<p>WPBakery :<br />
vc_cta,vc_custom_heading, vc_hoverbox, vc_line_chart, vc_pie,vc_progress_bar, vc_raw_html, vc_round_chart, vc_single_image, vc_text_separator</p>
</li>
<li>
<p>martfury :<br />
banner_large, banner_medium, banner_small, counter, faqs, icon_box, icons_list, image_box, member</p>
</li>
<li>
<p>plethora<br />
button,counter,headinggroup,hoverbox,teaserbox….</p>
</li>
<li>
<p>Woodmart<br />
Text Block, Button, Section Title, Info Box, Promo banner, Responsive Text block, Testimonial</p>
</li>
<li>
<p>Ultimate<br />
Info Circle</p>
</li>
<li>Naapo<br />
Vertical Tab</li>
</ul>
<p>other elements on demand.</p>
<h4>Concept</h4>
<p>Translate static text ,url, textarea, from the main language to other languages.</p>
<p>WPBakery 7.0 and 6.7.0 don’t need anymore change to be working with Falang for WPBakery.</p>
<p>Witht the 6.6.0 version of WPBakery you have too add a Filter to allow the translation tab to be displayed.<br />
wp-content/plugins/js_composer/include/classes/core/class-wpb-map.php 925<br />
add this line :<br />
self::$sc[ $tag ] = apply_filters(‘vc_element_settings_filter’, self::$sc[ $tag ], $tag );</p>
<h3>Known issues</h3>
<p>Between the 1.5 and the previous version the datastorage for content html translation is changed.<br />
The front-end translation will work but when you edit an old widget with content , the translation is removed.</p>


Falang for WPBakery Lite

The Falang for WPBakery plugin makes your WPBakery page translation simpler.

WP Composer Sync vs Falang for WPBakery Lite