Back to Modular Theme with PAGE BUILDER - Clear Support

prema770
prema770

We're lucky to have found the Clear theme. Makes it very easy for untrained people to maintain a site Our development scenario is that we have a build environment and a production environment In migrating the pages from build to production we

  • Copied relevant partials etc
  • Copied the static content page
  • Copied the entry in the meta file The page is front end visible but does not appear in the backend interface

Could we please have a migration procedure?

Thanks for any tips

Charis
Charis

prema770 said:

We're lucky to have found the Clear theme. Makes it very easy for untrained people to maintain a site Our development scenario is that we have a build environment and a production environment In migrating the pages from build to production we

  • Copied relevant partials etc
  • Copied the static content page
  • Copied the entry in the meta file The page is front end visible but does not appear in the backend interface

Could we please have a migration procedure?

Thanks for any tips

Hello!
As i see you have a regular licence for Clear Theme and the procedure to install your theme is very easy. You have created a project with the specific theme.This project has a Project ID. On regular licence you can use this project ID on one site only. You just have to go to "Updates & plugins" and click attach project.Then you add your project ID and click attach to project. If you need any custom work you can make it directly on Octobercms Environment.

prema770
prema770

Hi Charis Thanks for your response. May we ask you to consider a couple more scenarios?

  1. We have a development server and a live server and we understand that a single project ID will cover both. If after we develop on the dev server, making both changes and adding to CRUD theme pages these will be stored as content and indexed in the meta files. At the moment, as the two content folders are out of sync a straight copy dev => live can overwrite any content that has been since added to live. Right now we use a merge tool to get around this.

Questions:

  • Do we need a license for the dev server as well as live?
  • Is there a simpler way of syncing content?
  1. We also hold an extended license for the Success theme. We're very happy with this. We asked this question before but unfortunately didn't fully get the answer Question:
    • We purchase the license and the theme is made available within our account
    • We assign the theme to a project - life is good
    • The project is updated
    • We now want to apply the extended license to another project - different site that uses a different plugin set.
    • We expect the theme to be available to any number of projects as it is an extended license
    • On our account, once it is assigned to one project it is no longer available for reassignment so we resort to manual download and merging Again - Is there a better way? are we missing something?

Any comments tips welcome

Charis
Charis

prema770 said:

Hi Charis Thanks for your response. May we ask you to consider a couple more scenarios?

  1. We have a development server and a live server and we understand that a single project ID will cover both. If after we develop on the dev server, making both changes and adding to CRUD theme pages these will be stored as content and indexed in the meta files. At the moment, as the two content folders are out of sync a straight copy dev => live can overwrite any content that has been since added to live. Right now we use a merge tool to get around this.

Questions:

  • Do we need a license for the dev server as well as live?
  • Is there a simpler way of syncing content?
  1. We also hold an extended license for the Success theme. We're very happy with this. We asked this question before but unfortunately didn't fully get the answer Question:
    • We purchase the license and the theme is made available within our account
    • We assign the theme to a project - life is good
    • The project is updated
    • We now want to apply the extended license to another project - different site that uses a different plugin set.
    • We expect the theme to be available to any number of projects as it is an extended license
    • On our account, once it is assigned to one project it is no longer available for reassignment so we resort to manual download and merging Again - Is there a better way? are we missing something?

Any comments tips welcome

Hello Mike!
I will answer to your questions:

  • Do we need a license for the dev server as well as live?
    No, you only need one license for this situation as long the theme will be used to one site. More information can be found here: https://octobercms.com/help/license/faqs

  • Is there a simpler way of syncing content?
    Currently i don't know any easy way to sync content, for now at least(e.g:installing a githubsync plugin). There are some ways to make a github sync with your live server, you can search on internet how to do it.

You say
"We asked this question before but unfortunately didn't fully get the answer "
We talk for this on my private email and as you told me you misunderstanding the "Paid Themes" logic.
Μore analytically:
"You sent me this message with the steps you are making:

  1. Theme purchase
  2. Create a new project
  3. Attach the theme to the new project
  4. Paste ID in OCMS backend
  5. Install theme in OCMS Fine up to here
  6. Check for link under themes tab
  7. Go to another project
  8. Look for success theme to attach
  9. Not available
  10. Check through reattach options - not available"

After i explain you that this logic is wrong for paid themes, you answer me:
"Looks like my misunderstanding - apologies for the inconvenience. So when I create an additional site I will use the same ProjectID for each new site. Somehow I thought that I needed to create a new ProjectID for each new site I'll do some study on how the project architecture works"

So i thought you understand the logic behind paid themes and projects.
Steps from 6 to 10 are wrong. The project logic is different on a paid theme.
You create the project with theme and plugins and then to use it on your new website you just use the Project ID to transfer everything your project has. With the extended licence you can use Success theme to a Project and then use that Project ID to unlimited number of different sites. Unfortunately you can't add a paid theme to more than one projects. Maybe this could be done with Extended license but as far as i know is not.

You also can read this:
https://octobercms.com/blog/post/marketplace-algorithm-update-and-deleting-projects
"Once a plugin or theme is reattached to a project, it becomes locked to that project, unless that project is deleted too. This means you still cannot individually remove a paid product from a project, they only become available when the project is deleted permanently."

I hope I helped. For any questions please let me know, Ι will be very pleased to help you.

prema770
prema770

Hi Charis Thanks heaps for your full explanation. Just to be sure! I have two sites, all plugins are paid. For example:

Site 1: Success theme + formbuilder Site 2: Success theme + Octocart

Here's what would appear to work

  • Have a new project project ID - used only for Success theme Use this project ID
    • For my site 1 and site 2 projects I can't change project ID because they are needed for other paid plugins that also require updates
    • I should download new versions of the Success theme and update manually

Will go with that for now but would be happy to hear further tips if there are any :-)

1-5 of 5