Forums

Building a StartingPointPackage for 5.7

Permalink
I'm beginning to build a StartingPointPackage for 5.7.

I'm reading the tutorial:
http://legacy-documentation.concrete5.org/tutorials/concrete5-5-5-c...

but it's for 5.5. My questions are:
1) Is there something more up to date?
2) Is there any change in StartingPointPackage from 5.5 to 5.7 ?
3) In the tutorial, the link to the package format is dead. Where is the equivalent for 5.7?

Thanks for help!
 
VonUniGE replied on at Permalink Reply
I've found that in 5.7, the documentation related to "Starting Point Package" is located in a page named "Enabling Full Content Swap" (http://documentation.concrete5.org/developers/designing-for-concret... ).

The problem is that I don't found the Sample Content Generator in the market and if I install the version from github (https://github.com/concrete5/addon_sample_content_generator... ), I obtain a new page in the dashboard called "Generate Install Data" but nothing seems to work and some bits of php code are displayed in the page, such as: 
controller->getTask() == 'get_files') { ?>
VonUniGE replied on at Permalink Reply
Ok, I had to put:
short_open_tag = On

in /etc/php5/apache2/php.ini
MrKDilkington replied on at Permalink Reply
MrKDilkington
Hi VonUniGE,

I recommend looking into using the Migration Tools for creating your starting point package.

"The export tools built into the 5.7 migration tool also replace the Sample Content Generator, which add-on and theme developers can use to generate sample content. Unlike the Sample Content Generator add-on, the migration tool can build XML exports of just portions of your site, making it much easier to work with than the old add-on."

http://andrewembler.com/2015/11/upgrade-concrete5-sites-57-using-ou...
https://www.concrete5.org/community/forums/customizing_c5/5.6-to-5.7...
VonUniGE replied on at Permalink Reply
Thanks for your help.

Following your method, I've succeeded to export my site to a content.xml and import it as a package.

I had to manually modify the content.xml and change my topic tree from:
<trees>
   <tree type="topic" default="1">
      <topic name="abc"></topic>
    </tree>
</trees>

to 
<trees>
   <tree type="topic" name="xyz">
      <topic name="abc"></topic>
    </tree>
</trees>

It's maybe a bug in the migration tools add-on. What do you think?
MrKDilkington replied on at Permalink Reply
MrKDilkington
For other following this discussion, a GitHub issue was created for this.

"Tree element in content.xml raise an error #3588"
https://github.com/concrete5/concrete5/issues/3588...