Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook
Devcon 2020 Goes Virtual! LEARN MORE >

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Ability to "clone" a workspace with a new name....

Collapse
X
Collapse
 
  • Page of 2
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 template Next
    #1

    Ability to "clone" a workspace with a new name....

    Is there a simple method to be able to "clone" an existing workspace into a new folder with a new name?
    Tags: None
    #2
    Re: Ability to "clone" a workspace with a new name....

    Dion,

    Oddly, one of the first questions I asked myself when beginning to learn. I couldn't settle on a project naming convention for a time and was constantly in need of renaming. Was surprised to find no "save as" or "clone project" or forum instructions on same. Just guessed and experimented in the end.

    If the project name remains the same and you just want to change directories, then create a new directory and simply move all the subordinate content. I did (and continue to do this) during some version control operations.

    If the the directory and the project name changes, I have had some problems just changing the project files. There appear to be internal references (which is to be expected). What I've done several times and successfully is:
    1. Create a new directory
    2. Create a new project of the desired NEW name
    3. Set your desired defaults (e.g., open HTML in "source" mode, show line numbers in various windows, etc).
    4. Then move select content (A5W pages, A5WCMP [components], and JPG/PNG [images]).
    5. You can naturally export/import components from old to new... but it's easier/faster to copy them and they will be picked up when you relaunch the new app.
    6. You can port any DBF or active-link-DBF files also... but I usually use the opportunity to pull any I need from the remote database and thus ensure they are fresh anyway.
    7. In my case, I have some anomalies with the v12 install and have had to de-install and re-install a couple of times to resolve issues that could not otherwise be diagnosed/fixed. This includes "security file" issues. The de/re-install fixed the problems and migrating the project to a new name seems to have cleared up the security issues (I didn't copy the security files and allowed the new install and project to create new ones).
    8. It's a bit tedious... but not all that bad. Has taken me as little as 15 or 20 minutes before.


    That's my two bits.

    Comment

      #3
      Re: Ability to "clone" a workspace with a new name....

      Or use this fully functional batch file to duplicate a workspace with a new name: http://msgboard.alphasoftware.com/al...-a-Web-Project
      Steve Wood
      See my profile on IADN

      Comment

        #4
        Re: Ability to "clone" a workspace with a new name....

        Alrighty. In the future I'm going to go with Steve's approach.

        In win/unix for enterprise work I'd script/automate everything in korn shell or windows batch scripting. But I haven't got around to do any automation with A5 yet.

        Thanks.

        Comment

          #5
          Re: Ability to "clone" a workspace with a new name....

          An important side note is that the batch does not clone the project.settings file. This file contains the web project publishing Profiles. It is important to start with a fresh copy because that file contains a Security GUID for each Profile that must be unique if there is any opportunity that a given user might touch both web applications during the same session.
          Steve Wood
          See my profile on IADN

          Comment

            #6
            Re: Ability to "clone" a workspace with a new name....

            Great input. Thanks Steve!!!!

            Comment

              #7
              Re: Ability to "clone" a workspace with a new name....

              Thanks Steve...just what I was looking for this morning. I love it when that happens!
              Brad Weaver, President
              ComputerAid International
              Ottawa ON Canada
              Versailles KY USA
              www.compuaid.com

              Comment

                #8
                Re: Ability to "clone" a workspace with a new name....

                Thanks Steve, that kind of thing is what I was looking for last week when migrating a workspace from V11 to V12. I needed to duplicate the project to a new source folder and I didn't want to duplicate any of the hundreds of temporary or thousands of backup files Alpha Five generates. I used "backup workspace" and "restore workspace" - which, btw, had an issue that I'm going to start a new post on.

                Comment

                  #9
                  Re: Ability to "clone" a workspace with a new name....

                  Hello,
                  I realise this is an old thread, but I came across this doing search as the script it refers to, and it is exactly what I needed. (Great work Steve), But I have come across a little problem wondering if anyone has any ideas.
                  After creating a new work space and publishing, the new copy works fine except for the Reports, when I run the report it keep suggesting that I republish the reports for the SQL to be updated and run, I have republished several times but can’t seem to get the report to work e.g. keep prompting me to republish the report files..
                  Also the original workspace when published works fine, the reports still work, but they are much slower to load in PDF viewer???
                  Any suggestion anyone..

                  Comment

                    #10
                    Re: Ability to "clone" a workspace with a new name....

                    Sorry Ricky, nothing useful from me. I'm working entirely in the mobile space and have used everything except reports... I find other ways (e.g. creative LISTS) to present information instead. As a result I haven't seen your particular bugaboo.

                    Comment

                      #11
                      Re: Ability to "clone" a workspace with a new name....

                      Steve; your batch file is a gem !

                      I cloned a mobile project and changed all my connection string references I could find, recreated the security tables in the new database and published the site; however, when I try to log in I get "Login information incorrect" message; I could not find any references to connection strings in the login component and assume that recreating the security backend would work...

                      What am I missing?

                      Thanks

                      Comment

                        #12
                        Re: Ability to "clone" a workspace with a new name....

                        Terence, are the Alpha Security Tables being stored in SQL for your project?

                        If so, I have same type of problem "Login information incorrect" just after applying a WAS update and re-publishing my recent code changes. (Extremely frustrating) I had same type of problem trying to do the initial conversion from DBF to SQL for the Security tables. I really think there is a problem here. Perhaps something to do with 1) encrypting/decrypting connection string as project stores it un-encrypted but when viewed on server they have become encrypted, 2) publishing active link DBF files to link to corresponding SQL security tables, 3) working with published projects that are in a subfolder from the root pub, or 4) correctly publishing/reading the a5i file or the "*.securitySettings" files.

                        Comment

                          #13
                          Re: Ability to "clone" a workspace with a new name....

                          Terence, the batch file does not copy the security files. Just go manually copy the file named project.security_settings over to your new project.
                          Steve Wood
                          See my profile on IADN

                          Comment

                            #14
                            Re: Ability to "clone" a workspace with a new name....

                            Rich/Steve; thanks - I actually deleted and recreated the tables in MySQL - but Rich you may have triggered my memory - there is setting where you specify the "default or actual" connection string and I may have forgotten to check/set that property. I'll have to check on that ...

                            Comment

                              #15
                              Re: Ability to "clone" a workspace with a new name....

                              Update:
                              - I checked the publish profile AlphaDAO string and set it to actual
                              - Published the site to my VPS AA5 server
                              - My mySQL is hosted on another Linux VPS
                              - I have allowed access to the mySQL server using the AA5 server IP

                              The only issue I can think of is the AJAX request (may be) uses JSON and since this is another domain then JSONP is not being used hence the failure.

                              Would hope Alpha could weigh in on this... although this article does say "Support for Cross-Domain Ajax Callbacks facilitates getting data from third-party services..."

                              http://appdevelopermagazine.com/1294...d-Hybrid-Apps/

                              Comment

                              Previous 1 2 template Next
                              Working...
                              X