Jump to content
ryan

Profile Export module (also upgrade PW 2.0 to 2.1)

Recommended Posts

Thank you again Ryan!

May I ask a couple of feature related questions? I have just tried out this module for the first time and noticed the following:

1) It is not possible to exclude modules.

Admin related modules are not needed in many cases (such as ProcessDatabaseBackups, ProcessWireUpgrade, ProcessExportProfile, etc...) and it would be nice to be able to optionally exclude them.

2) Custom folders?

Since I followed what is recommended here:


I already have one custom folder called "lib" in my /site folder and my template files use its content. However, the exporter ignored this custom folder. Did I overlook something or is it really the case and I have to manually copy "such things" over?

3) Extra lines inserted into the end of config.php?

I also have extra lines inserted into the end of config.php. It would be nice, if it was possible to optionally inject these extra lines of code to the end of config.php, so that the ProcessWire installer uses the "core config.php" file, but modifies it by adding extra lines to it, lines that are required by the Profile. I have a require_once(dirname(__FILE__).'/lib/Flog.php'); piece of code, and although it is possible to include config.php in the Profile itself, being able to automatically "extend" config.php during the installation process seems to be a better solution.

Or maybe I am just overlooking something :) Sorry if it is just a silly request and there is already a proper way of doing this, of which I know nothing about.

Edit: maybe it is not just config.php but .htaccess too that we should be able to extend the above described (or similar) way.

Edited by szabesz

Share this post


Link to post
Share on other sites

had an issue today when using a name like "example.com transfer profile"

it showed up in the select box but after clicking on "continue" it said "no site profile found"

Share this post


Link to post
Share on other sites

Is there any reason why the profile exporter would not export ALL the content of the email field?

I used the default system email field on another template (member's emails). They are not getting exported at all.

Is there a way to export them? Or should I not use the system email field for this purpose?

What about users? Are they not supposed to be imported as well?

Thanks. :)

Share this post


Link to post
Share on other sites

Hi,

I got an issue with this module when trying to make a fresh install with my exported profile.

Everything is working well until I try to connect to the existing database. A lot of error occurs, preventing me to continue the installation.

Here is a screenshot of the errors log.

Any idea where is this come from?

Thanks and thanks a lot for this awesome cms and community forum.

Étienne

Capture du 2016-09-09 11-29-56.png

Share this post


Link to post
Share on other sites
36 minutes ago, Jason Huck said:

Can anyone confirm whether this module works with PW3?

Gave it a quick try. It installed without error and created a .zip file, but it failed to copy over the contents of my /templates directory, and the web-based installer in a fresh PW3 installation fails to see the profile. I guess I'll just manually copy everything over for now.

Share this post


Link to post
Share on other sites
14 hours ago, Jason Huck said:

Can anyone confirm whether this module works with PW3?

Works okay for me, although I always use the directory option rather than ZIP because I'm exporting/importing locally.

Share this post


Link to post
Share on other sites
On 21.1.2016 at 11:51 PM, bernhard said:

had an issue today when using a name like "example.com transfer profile"

it showed up in the select box but after clicking on "continue" it said "no site profile found"

Same here. Try not use a dot (.) in profile name.

Share this post


Link to post
Share on other sites
On 3.10.2016 at 7:35 PM, Jason Huck said:

Can anyone confirm whether this module works with PW3?

I used ProcessExportProfile in Processwire 3.0.3. 

The name fields can not have point character ".". If, than the site-profile is not detected.

The generated config.php file needs the namespace at top, if generating new Classes in the config, like:

<?php namespace ProcessWire;
//...
if(!defined("PROCESSWIRE")) die();
//...
$config->custom_footer_scripts = new FilenameArray(); //own array for js at bottom of page

I like ProcessExportProfile for new Projects — i hope the module is not buried.

  • Like 1

Share this post


Link to post
Share on other sites

@ryan, could you please add an option to include setlocale() in the exported config.php if it is defined. Now that PW is giving warnings if setlocale() is missing it would be nice not to have to remember to manually add this each time a profile is installed.

  • Like 3

Share this post


Link to post
Share on other sites

Hello all. I've tested a few times the export of a working profile and there seems to be something that I am missing or doing wrong. I am using latest PW version as of now and just setup a multilanguage profile (default one) with minimal touch but just adding a few modules needed for my new project. 

As soon as I export the profile adding a simple name (test) and giving a name Test with some description text and a small image for the preview, it proceeds well and exports the profile, however if I try to reinstall it later it does not show in the profile installer.

Is there anything I could do to make sure the exported profile would work upon moving to a new host or being set by someone else? I was thinking that some modules could cause the issue so tried to disable some of those but had the same result. Sometimes it works, sometimes it does not.

Any ideas/hints where to look for a possible reason? Btw, I am using Apache 2.4 and PHP 5.6 with MySQL 5.6 if that matters.

Share this post


Link to post
Share on other sites

Nevermind, I figured it out looking at the content of the folder. It appeared that for some reason there were no profile nor template files iin the appropriate folders. Choosing to create a zipped profile made the export promptly with all the files needed. Tested again to export the profile to a folder and this time it worked like a charm.

Thanks for the nice mod, @ryan and anyone else involved in the coding/testing. I simply can't get enough of PW ;)

Share this post


Link to post
Share on other sites

The current version of ProcessExportProfile  module seems to be having issues with not populating data in the exported SQL correctly.

I'm getting errors like:

SQLSTATE[42000]: Syntax error or access violation: 1067 Invalid default value for 'created'

The problem seems to be here:

CREATE TABLE `modules` (
  `id` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `class` varchar(128) CHARACTER SET ascii NOT NULL,
  `flags` int(11) NOT NULL DEFAULT '0',
  `data` text NOT NULL,
  `created` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',
  PRIMARY KEY (`id`),
  UNIQUE KEY `class` (`class`)
) ENGINE=MyISAM AUTO_INCREMENT=188 DEFAULT CHARSET=utf8;

The timestamp value that is exported is an invalid value with mySQL 5.7.14 that I'm using, so the import fails with the mySQL error.

There also seem to be a whole lot of records (ie all the core modules) like the following which also fail on insert:

INSERT INTO `modules` (`id`, `class`, `flags`, `data`, `created`) VALUES('1', 'FieldtypeTextarea', '1', '', '0000-00-00 00:00:00');

Modules that I've installed myself work fine as they have a valid date.

Exported profiles did work in the past, so I'm not sure if this is a Processwire issue, or different mySQL configuration that's being more strict about date formats.

Edited by kongondo
Moved post here to the module's support forum.

Share this post


Link to post
Share on other sites

im trying to export a live site so i can set it up locally,

but when i try to export it i get this error 

Naamloos.png

Share this post


Link to post
Share on other sites

Today I noticed that none of the /assets/files are being included in the generated zip file nor using the directory option. The permissions are set and my PW 3.0.109 ProcessModule has no problem r/w any folder in the assets directory. Has anyone experienced this, or can offer some insight?

In addition, it would be nice to have the assets folder contents listed with selectable sub-folders to be included in the final output.

[edit] ProcessExportProfile 3.0.0

Share this post


Link to post
Share on other sites

Hello there, 

noob here:

I have processwire on a  virtualbox (debian) and I now have a server where I want to have my current work. In the backend I installed "Export Site Profile". On the server there is only debian 9 so far. What is the next step? Do I fist have to install processwire on the server and copy the zip of my current project in some place after the installation?

 

Thank you in advance.

Share this post


Link to post
Share on other sites

Hello,

14 hours ago, Marcel said:

What is the next step?

You can use a site profile (even an exported one) only during the installation process of ProcessWire, that is why you need to put your exported and extracted site profile in the root directory of the site next to install.php, meaning alongside with all the other site profiles ProcessWire comes with. Start the installation process as normal and pick your exported site profile when prompted to choose one.

Share this post


Link to post
Share on other sites

Ok, thanks. So I put the 

site-project-export.zip

into the 

/var/www/html

and then I follow the installation process in the browser, right?

Share this post


Link to post
Share on other sites

Almost but you need to extract the zip file. Your exported site profile should look like as if it was just another one bundled with ProcessWire. Eg.:

site-beginner
site-blank
site-classic
site-default
site-languages
site-myexportedprofile
site-regular

 

Share this post


Link to post
Share on other sites

Sorry as noob I just want to be sure

1. unzip the exported zip file in /var/www/html (the structure is site-project-export>assets | install | modules | templates | config.php

2. get to the browser and follow install process

 

right?

Share this post


Link to post
Share on other sites

Today I exported a site profile. After installing a new PW instance and put my site-boilerplate folder in the root, and deleted the default site-profiles, PW just outputs an error on the install screen "no profiles found". I'm puzzled. When I put the default site profiles back in, it recognizes them all - except my own.

Is this module even maintained anymore?

After reading this thread, I also checked for any special characters in the profile name, there's nothing like that. I also compared the .json and .sql files in the install-folder: they look identical to me in structure.

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By David Karich
      ProcessWire InputfieldRepeaterMatrixDuplicate
      Thanks to the great ProModule "RepeaterMatrix" I have the possibility to create complex repeater items. With it I have created a quite powerful page builder. Many different content modules, with many more possible design options. The RepeaterMatrix module supports the cloning of items, but only within the same page. Now I often have the case that very design-intensive pages and items are created. If you want to use a content module on a different page (e.g. in the same design), you have to rebuild each item manually every time.
      This module extends the commercial ProModule "RepeaterMatrix" by the function to duplicate repeater items from one page to another page. The condition is that the target field is the same matrix field from which the item is duplicated. This module is currently understood as proof of concept. There are a few limitations that need to be considered. The intention of the module is that this functionality is integrated into the core of RepeaterMatrix and does not require an extra module.
      Check out the screencast
      What the module can do
      Duplicate multible repeater items from one page to another No matter how complex the item is Full support for file and image fields Multilingual support Support of Min and Max settings Live synchronization of clipboard between multiple browser tabs. Copy an item and simply switch the browser tab to the target page and you will immediately see the past button Support of multiple RepeaterMatrix fields on one page Configurable which roles and fields are excluded Configurable dialogs for copy and paste Duplicated items are automatically pasted to the end of the target field and set to hidden status so that changes are not directly published Automatic clipboard update when other items are picked Automatically removes old clipboard data if it is not pasted within 6 hours Delete clipboard itself by clicking the selected item again Benefit: unbelievably fast workflow and content replication What the module can't do
      Before an item can be duplicated in its current version, the source page must be saved. This means that if you make changes to an item and copy this, the old saved state will be duplicated Dynamic loading is currently not possible. Means no AJAX. When pasting, the target page is saved completely No support for nested repeater items. Currently only first level items can be duplicated. Means a repeater field in a repeater field cannot be duplicated. Workaround: simply duplicate the parent item Dynamic reloading and adding of repeater items cannot be registered. Several interfaces and events from the core are missing. The initialization occurs only once after the page load event Changelog
      2.0.0
      Feature: Copy multiple items at once! The fundament for copying multiple items was created by @Autofahrn - THX! Feature: Optionally you can disable the copy and/or paste dialog Bug fix: A fix suggestion when additional and normal repeater fields are present was contributed by @joshua - THX! 1.0.4
      Bug fix: Various bug fixes and improvements in live synchronization Bug fix: Items are no longer inserted when the normal save button is clicked. Only when the past button is explicitly clicked Feature: Support of multiple repeater fields in one page Feature: Support of repeater Min/Max settings Feature: Configurable roles and fields Enhancement: Improved clipboard management Enhancement: Documentation improvement Enhancement: Corrected few typos #1 1.0.3
      Feature: Live synchronization Enhancement: Load the module only in the backend Enhancement: Documentation improvement 1.0.2
      Bug fix: Various bug fixes and improvements in JS functions Enhancement: Documentation improvement Enhancement: Corrected few typos 1.0.1
      Bug fix: Various bug fixes and improvements in the duplication process 1.0.0
      Initial release Support this module
      If this module is useful for you, I am very thankful for your small donation: Donate 5,- Euro (via PayPal – or an amount of your choice. Thank you!)
      Download this module (Version 2.0.0)
      > Github: https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate
      > PW module directory: https://modules.processwire.com/modules/inputfield-repeater-matrix-duplicate/
      > Old stable version (1.0.4): https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate/releases/tag/1.0.4
    • By Robin S
      A new module that hasn't had a lot of testing yet. Please do your own testing before deploying on any production website.
      Custom Paths
      Allows any page to have a custom path/URL.
      Note: Custom Paths is incompatible with the core LanguageSupportPageNames module. I have no experience working with LanguageSupportPageNames or multi-language sites in general so I'm not in a position to work out if a fix is possible. If anyone with multi-language experience can contribute a fix it would be much appreciated!
      Screenshot

      Usage
      The module creates a field named custom_path on install. Add the custom_path field to the template of any page you want to set a custom path for. Whatever path is entered into this field determines the path and URL of the page ($page->path and $page->url). Page numbers and URL segments are supported if these are enabled for the template, and previous custom paths are managed by PagePathHistory if that module is installed.
      The custom_path field appears on the Settings tab in Page Edit by default but there is an option in the module configuration to disable this if you want to position the field among the other template fields.
      If the custom_path field is populated for a page it should be a path that is relative to the site root and that starts with a forward slash. The module prevents the same custom path being set for more than one page.
      The custom_path value takes precedence over any ProcessWire path. You can even override the Home page by setting a custom path of "/" for a page.
      It is highly recommended to set access controls on the custom_path field so that only privileged roles can edit it: superuser-only is recommended.
      It is up to the user to set and maintain suitable custom paths for any pages where the module is in use. Make sure your custom paths are compatible with ProcessWire's $config and .htaccess settings, and if you are basing the custom path on the names of parent pages you will probably want to have a strategy for updating custom paths if parent pages are renamed or moved.
      Example hooks to Pages::saveReady
      You might want to use a Pages::saveReady hook to automatically set the custom path for some pages. Below are a couple of examples.
      1. In this example the start of the custom path is fixed but the end of the path will update dynamically according to the name of the page:
      $pages->addHookAfter('saveReady', function(HookEvent $event) { $page = $event->arguments(0); if($page->template == 'my_template') { $page->custom_path = "/some-custom/path-segments/$page->name/"; } }); 2. The Custom Paths module adds a new Page::realPath method/property that can be used to get the "real" ProcessWire path to a page that might have a custom path set. In this example the custom path for news items is derived from the real ProcessWire path but a parent named "news-items" is removed:
      $pages->addHookAfter('saveReady', function(HookEvent $event) { $page = $event->arguments(0); if($page->template == 'news_item') { $page->custom_path = str_replace('/news-items/', '/', $page->realPath); } }); Caveats
      The custom paths will be used automatically for links created in CKEditor fields, but if you have the "link abstraction" option enabled for CKEditor fields (Details > Markup/HTML (Content Type) > HTML Options) then you will see notices from MarkupQA warning you that it is unable to resolve the links.
      Installation
      Install the Custom Paths module.
      Uninstallation
      The custom_path field is not automatically deleted when the module is uninstalled. You can delete it manually if the field is no longer needed.
       
      https://github.com/Toutouwai/CustomPaths
      https://modules.processwire.com/modules/custom-paths/
    • By teppo
      Hey folks!
      I'm happy to finally introduce a project I've been working on for quite a while now: it's called Wireframe, and it is an output framework for ProcessWire.
      Note that I'm posting this in the module development area, maily because this project is still in rather early stage. I've built a couple of sites with it myself, and parts of the codebase have been powering some pretty big and complex sites for many years now, but this should still be considered a soft launch 🙂
      --
      Long story short, Wireframe is a module that provides the "backbone" for building sites (and apps) with ProcessWire using an MVC (or perhaps MVVM... one of those three or four letter acronyms anyway) inspired methodology. You could say that it's an output strategy, but I prefer the term "output framework", since in my mind the word "strategy" means something less tangible. A way of doing things, rather than a tool that actually does things.
      Wireframe (the module) provides a basic implementation for some familiar MVC concepts, such as Controllers and a View layer – the latter of which consists of layouts, partials, and template-specific views. There's no "model" layer, since in this context ProcessWire is the model. As a module Wireframe is actually quite simple – not even nearly the biggest one I've built – but there's still quite a bit of stuff to "get", so I've put together a demo & documentation site for it at https://wireframe-framework.com/.
      In addition to the core module, I'm also working on a couple of site profiles based on it. My current idea is actually to keep the module very light-weight, and implement most of the "opinionated" stuff in site profiles and/or companion modules. For an example MarkupMenu (which I released a while ago) was developed as one of those "companion modules" when I needed a menu module to use on the site profiles.
      Currently there are two public site profiles based on Wireframe:
      site-wireframe-docs is the demo&docs site mentioned above, just with placeholder content replaced with placeholder content. It's not a particularly complex site, but I believe it's still a pretty nice way to dig into the Wireframe module. site-wireframe-boilerplate is a boilerplate (or starter) site profile based on the docs site. This is still very much a work in progress, but essentially I'm trying to build a flexible yet full-featured starter profile you can just grab and start building upon. There will be a proper build process for resources, it will include most of the basic features one tends to need from site to site, etc. --
      Requirements and getting started:
      Wireframe can be installed just like any ProcessWire module. Just clone or download it to your site/modules/ directory and install. It doesn't, though, do a whole lot of stuff on itself – please check out the documentation site for a step-by-step guide on setting up the directory structure, adding the "bootstrap file", etc. You may find it easier to install one of the site profiles mentioned above, but note that this process involves the use of Composer. In the case of the site profiles you can install ProcessWire as usual and download or clone the site profile directory into your setup, but after that you should run "composer install" to get all the dependencies – including the Wireframe module – in place. Hard requirements for Wireframe are ProcessWire 3.0.112 and PHP 7.1+. The codebase is authored with current PHP versions in mind, and while running it on 7.0 may be possible, anything below that definitely won't work. A feature I added just today to the Wireframe module is that in case ProcessWire has write access to your site/templates/ directory, you can use the module settings screen to create the expected directories automatically. Currently that's all, and the module won't – for an example – create Controllers or layouts for you, so you should check out the site profiles for examples on these. (I'm probably going to include some additional helper features in the near future.)
      --
      This project is loosely based on an earlier project called pw-mvc, i.e. the main concepts (such as Controllers and the View layer) are very similar. That being said, Wireframe is a major upgrade in terms of both functionality and architecture: namespaces and autoloader support are now baked in, the codebase requires PHP 7, Controllers are classes extending \Wireframe\Controller (instead of regular "flat" PHP files), implementation based on a module instead of a collection of drop-in files, etc.
      While Wireframe is indeed still in a relatively early stage (0.3.0 was launched today, in case version numbers matter) for the most part I'm happy with the way it works, and likely won't change it too drastically anytime soon – so feel free to give it a try, and if you do, please let me know how it went. I will continue building upon this project, and I am also constantly working on various side projects, such as the site profiles and a few unannounced helper modules.
      I should probably add that while Wireframe is not hard to use, it is more geared towards those interested in "software development" type methodology. With future updates to the module, the site profiles, and the docs I hope to lower the learning curve, but certain level of "developer focus" will remain. Although of course the optimal outcome would be if I could use this project to lure more folks towards that end of the spectrum... 🙂
      --
      Please let me know what you think – and thanks in advance!
    • By tcnet
      PageViewStatistic for ProcessWire is a module to log page visits of the CMS. The records including some basic information like IP-address, browser, operating system, requested page and originate page. Please note that this module doesn't claim to be the best or most accurate.
      Advantages
      One of the biggest advantage is that this module doesn't require any external service like Google Analytics or similar. You don't have to modify your templates either. There is also no JavaScript or image required.
      Disadvantages
      There is only one disadvantage. This module doesn't record visits if the browser loads the page from its browser cache. To prevent the browser from loading the page from its cache, add the following meta tags to the header of your page:
      <meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate" /> <meta http-equiv="Pragma" content="no-cache" /> <meta http-equiv="Expires" content="0" /> How to use
      The records can be accessed via the Setup-menu of the CMS backend. The first dropdown control changes the view mode. There are 4 different view modes.
      View mode "Day" shows all visits of the selected day individually with IP-address, browser, operating system, requested page and originate page. Click the update button to see new added records. View mode "Month" shows the total of all visitors per day from the first to the last day of the selected month. View mode "Year" shows the total of all visitors per month from the first to the last month of the selected year. View mode "Total" shows the total of all visitors per year for all recorded years. Please note that multiple visits from the same IP address within the selected period are counted as a single visitor.
      Settings
      You can access the module settings by clicking the Configuration button at the bottom of the records page. The settings page is also available in the menu: Modules->Configure->ProcessPageViewStat.
      IP2Location
      This module uses the IP2Location database from: http://www.ip2location.com. This database is required to obtain the country from the IP address. IP2Location updates this database at the begin of every month. The settings of ProcessPageViewStat offers the ability to automatically download the database monthly. Please note, that automatically download will not work if your webspace doesn't allow allow_url_fopen.
      Dragscroll
      This module uses DragScroll. A JavaScript available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability in view mode "Day" to drag the records horizontally with the mouse pointer.
      parseUserAgentStringClass
      This module uses the PHP class parseUserAgentStringClass available from: http://www.toms-world.org/blog/parseuseragentstring/. This class is required to filter out the browser type and operating system from the server request.
      Special Feature
      PageViewStatistic for ProcessWire can record the time a visitor viewed the page. This feature is deactivated by default. To activate open the module configuration page and activate "Record view time". If activated you will find a new column "S." in the records which means the time of view in seconds. With every page request, a Javascript code is inserted directly after the <body> tag. Every time the visitor switches to another tab or closes the tab, this script reports the number of seconds the tab was visible. The initial page request is recorded only as a hyphen (-).
       
    • By MoritzLost
      This module allows you to integrate hCaptcha bot / spam protection into ProcessWire forms. hCaptcha is a great alternative to Google ReCaptcha, especially if you are in the EU and need to comply with privacy regulations.

      The development of this module is sponsored by schwarzdesign.
      The module is built as an Inputfield, allowing you to integrate it into any ProcessWire form you want. It's primarily intended for frontend forms and can be added to Form Builder forms for automatic spam protection. There's a step-by-step guide for adding the hCaptcha widget to Form Builder forms in the README, as well as instructions for API usage.
      Features
      Inputfield that displays an hCaptcha widget in ProcessWire forms. The inputfield verifies the hCaptcha response upon submission, and adds a field error if it is invalid. All hCaptcha configuration options for the widget (theme, display size etc) can be changed through the inputfield configuration, as well as programmatically. hCaptcha script options can be changed through a hook. Error messages can be translated through ProcessWire's site translations. hCaptcha secret keys and site-keys can be set for each individual inputfield or globally in your config.php. Error codes and failures are logged to help you find configuration errors. Please check the README for setup instructions.
      Links
      Github Repository and documentation InputfieldHCaptcha in the module directory Screenshots (configuration)

      Screenshots (hCaptcha widget)

       
       

       
×
×
  • Create New...