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

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

"fixing publishing history"

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    "fixing publishing history"

    What is this about?

    Can I safely turn it off?

    Where do I turn it off?
    Gary S. Traub, Ph.D.


    #2
    Re: "fixing publishing history"

    The only time you should see a dialog about "fixing publishing history" is a condition where the history has a problem such as the same page or component being listed twice in the history. This should be extremely rare, but has been found in some histories built in V10 and early V11 builds and has lead to objects being included in the publish process when they should not be included. The cleanup should not be terminated, but allowed to run to completion. It should not recur after it has run once.

    Comment


      #3
      Re: "fixing publishing history"

      I get that message EVERY time I publish anything even a single component or page. And it takes quite a long time to complete. Very annoying!
      Gary S. Traub, Ph.D.

      Comment


        #4
        Re: "fixing publishing history"

        May I make a suggestion. I have noticed that you seem to experience unusual issues. Not the issues like most others and I have like not fully understanding the operation of the Alpha software. Maybe you have a hardware problem like a memory timing issue, bad memory, hard drive with some bad clusters, or a network timing issue. I think I would run some hardware diagnostics to make sure that hardware is not a problem.
        Win 10 64 Development, Win 7 64 WAS 11-1, 2, Win 10 64 AA-1,2, MySql, dbForge Studio The Best MySQL GUI Tool IMHO. http://www.devart.com/dbforge/mysql/studio/

        Comment


          #5
          Re: "fixing publishing history"

          Hi Frank,

          Suggestions are always welcomed:) And your post got me hopeful - I installed v11 on a completely different machine, but still running windows 7 - same problems ....

          This is just really annoying because I cannot get any work done.
          Gary S. Traub, Ph.D.

          Comment


            #6
            Re: "fixing publishing history"

            I'm also getting it every single time I publish. It only take a few seconds for me though. Also, since you said listed twice in publish history. EVERY single time I publish, even if I havn't made any changes (literally publish, then click publish again) These files always get published.
            Code:
            security:{C:\Users\KyleMcNally\Documents\janiking-app-v11\jkapp.WebProjects\Default.WebProject\Project.SecuritySettings}
            copyfile:{C:\Users\KyleMcNally\Documents\janiking-app-v11\jkapp.WebProjects\Default.WebProject\Pages.SecuritySettings}
            copyfile:{C:\Users\KyleMcNally\Documents\janiking-app-v11\jkapp.WebProjects\Default.WebProject\images\emails\cmm.png}
            copyfile:{C:\Users\KyleMcNally\Documents\janiking-app-v11\jkapp.WebProjects\Default.WebProject\images\emails\cutcosts.png}
            copyfile:{C:\Users\KyleMcNally\Documents\janiking-app-v11\jkapp.WebProjects\Default.WebProject\images\emails\pgatour.png}
            copyfile:{C:\Users\KyleMcNally\Documents\janiking-app-v11\jkapp.WebProjects\Default.WebProject\images\emails\trustyourkeys.booklet.png}
            copyfile:{C:\Users\KyleMcNally\Documents\janiking-app-v11\jkapp.WebProjects\Default.WebProject\images\emails\trustyourkeys.folder.png}
            copyfile:{C:\Users\KyleMcNally\Documents\janiking-app-v11\jkapp.WebProjects\Default.WebProject\javascript\js.js}
            copyfile:{C:\Users\KyleMcNally\Documents\janiking-app-v11\jkapp.WebProjects\Default.WebProject\jkapp.aex}
            copyfile:{C:\Users\KyleMcNally\Documents\janiking-app-v11\jkapp.WebProjects\Default.WebProject\ProjectProperties.projectProperties}
            copyfile:{C:\Users\KyleMcNally\Documents\janiking-app-v11\jkapp.WebProjects\Default.WebProject\QuickPublish.settings}
            copyfile:{C:\Users\KyleMcNally\Documents\janiking-app-v11\jkapp.WebProjects\Default.WebProject\robots.txt}
            copyfile:{C:\Users\KyleMcNally\Documents\janiking-app-v11\jkapp.WebProjects\Default.WebProject\statuscodes\401.html}
            copyfile:{C:\Users\KyleMcNally\Documents\janiking-app-v11\jkapp.WebProjects\Default.WebProject\statuscodes\404.html}
            css:<ProjectStyle>
            CSS:Airport
            css:Day
            CSS:jkapp
            copyfile:{C:\Users\KyleMcNally\Documents\janiking-app-v11\jkapp.alb}
            copyfile:{C:\Users\KyleMcNally\Documents\janiking-app-v11\jkapp.alm}
            copyfile:{C:\Users\KyleMcNally\Documents\janiking-app-v11\jkapp.alx}
            css:A5System

            Comment


              #7
              Re: &quot;fixing publishing history&quot;

              OK, so I cleared my publishing history, republished everything, and now it's not showing up. Try that, also after doing that it is only publishing
              Code:
              copyfile:{C:\Users\KyleMcNally\Documents\janiking-app-v11\jkapp.WebProjects\Default.WebProject\jkapp.aex}
              copyfile:{C:\Users\KyleMcNally\Documents\janiking-app-v11\jkapp.WebProjects\Default.WebProject\ProjectProperties.projectProperties}
              css:<ProjectStyle>
              copyfile:{C:\Users\KyleMcNally\Documents\janiking-app-v11\jkapp.alb}
              copyfile:{C:\Users\KyleMcNally\Documents\janiking-app-v11\jkapp.alm}
              copyfile:{C:\Users\KyleMcNally\Documents\janiking-app-v11\jkapp.alx}
              every single time, and that's probably because I have publish support files and compile aex functions selected.

              Comment


                #8
                Re: &quot;fixing publishing history&quot;

                That is strange. It seems like the only difference between your machine and my machine is hardware. I have the publish support files selected as well. When I publish it only publishes the changed file(s).
                Win 10 64 Development, Win 7 64 WAS 11-1, 2, Win 10 64 AA-1,2, MySql, dbForge Studio The Best MySQL GUI Tool IMHO. http://www.devart.com/dbforge/mysql/studio/

                Comment


                  #9
                  Re: &quot;fixing publishing history&quot;

                  I am still having this problem. So frustrating ....
                  Gary S. Traub, Ph.D.

                  Comment


                    #10
                    Re: &quot;fixing publishing history&quot;

                    The way it publishes is completely erratic. Sometimes it publishes everything, sometimes not. It always publishes certain css and stuff even though nothing changed. It also depends where you are publishing from - the web CP, the component, right click, etc etc... Yes, very annoying indeed.
                    Peter
                    AlphaBase Solutions, LLC

                    [email protected]
                    https://www.alphabasesolutions.com


                    Comment


                      #11
                      Re: &quot;fixing publishing history&quot;

                      My vote would be, and has been, to have an option to completely remove history or publish only new-changed files, AND to only publish the files I select, no others. That would be an at-your-own-risk option. I 100% of the time click to clear history because I want to publish what I want to publish.
                      Steve Wood
                      See my profile on IADN

                      Comment


                        #12
                        Re: &quot;fixing publishing history&quot;

                        I second that.

                        I 100% of the time click to clear history because I want to publish what I want to publish.
                        Doesn't that mean that EVERYTHING publishes?
                        Peter
                        AlphaBase Solutions, LLC

                        [email protected]
                        https://www.alphabasesolutions.com


                        Comment


                          #13
                          Re: &quot;fixing publishing history&quot;

                          No, I mean I clear history even when I specifically select one or n individual items. I'm never going to rely on History to decide what needs to be published. I jump around between Local, Remote and Preview -- I don't know if it maintains different sets of history for each of those. But as you say, it is inconsistent so I take it out of the equation and wish it could be skipped. Also, on a large application it takes quite a bit of time to determine what needs to be published based on History.
                          Steve Wood
                          See my profile on IADN

                          Comment


                            #14
                            Re: &quot;fixing publishing history&quot;

                            By the way, when I cleared publish history, it resolved the issue, for me, at least as far as I can tell.
                            Gary S. Traub, Ph.D.

                            Comment


                              #15
                              Re: &quot;fixing publishing history&quot;

                              Originally posted by drgarytraub View Post
                              By the way, when I cleared publish history, it resolved the issue, for me, at least as far as I can tell.
                              I don't use the Publish to <others> besides the local webroot.
                              I have teamviewer on the remote host and use the file transfer for local <webroot> to remote <webroot>.
                              Teamviewer 7 is SMART SFTP it will only replace those files in the remote webroot that have changed.
                              There serveral apps in that way I manage that way on serveral servers [US/EU].

                              Eric

                              Comment

                              Working...
                              X