Content Workflow issue with Upgrade

Post here for help with installing or upgrading mojoPortal pre-compiled release packages. When posting in this forum, please provide all relevant details. You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

Post here for help with installation of mojoPortal pre-compiled release packages

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.

You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

This thread is closed to new posts. You must sign in to post in the forums.
12/21/2011 3:54:00 PM
Gravatar
Total Posts 130

Content Workflow issue with Upgrade

Hello,

I have recently upgraded from 2.3.5.3 MSSQL to 2.3.7.5 MSSQL multi-site mode.  I enabled content workflow on the Parent Site (SiteID1) with my Admin account and am able to Save the html content module as a draft, but do not get the icons for request approval, discard changes etc.  This functionality was present prior to the upgrade. When I open the WYSIWYG Editor for the same html module, I can "Update Draft" (and this is as the Admin) but there is no setting to publish the changes.

I read the Content Workflow page and added this to the web.config:  <add key="EnableContentWorkflow" value="true" /> and have restarted the app pool. I've updated my skin file after going through the release notes and don't remember seeing anything for the Content Workflow. I checked the mp_SiteSettingsEx table in the db and EnableContentWorkflow is set to True. 

Any ideas for what could be amiss?  Maybe I've overlooked something?

Thanks,

Beth

12/21/2011 4:35:42 PM
Gravatar
Total Posts 1203
Proud member of the mojoPortal team

Help support mojoPortal!
Add-on modules

Re: Content Workflow issue with Upgrade

Hi Beth, I know there have been a couple of bugs related to draft editing and approvals since 2.3.5.3 (like this and this), but I think they have all been addressed as of 2.3.7.5. I just took a look at our development site, which is built from source as of a few days ago. and as Administrator I'm seeing all of the draft approval icons, between the "settings" and "edit" icons (when viewing the instance on the page). You are Administrator, not Content Administrator, right?

I did just notice that when you're in the editor view, the only options at the bottom are Update Draft (button) Compare Draft to Live (link) and Cancel (link). Did there used to be submit for approval/approve buttons or links there in the past? I can't remember if that's how it used to work.

Jamie

12/22/2011 7:51:41 AM
Gravatar
Total Posts 130

Re: Content Workflow issue with Upgrade

Hi Jamie,

I am definitely using my Admin (not Content Admin) account. In the older install I only have the Update Draft (button) Compare Draft to Live (link) and Cancel (link), no additional options until after you've updated the draft.

I'm wondering if maybe something went wrong during the upgrade. This is a test copy anyway and I'll be performing the final upgrade over the Holiday break.  If there are any ideas for what might of gone wrong I am all ears though.

~ Beth

12/22/2011 10:14:34 AM
Gravatar
Total Posts 18439

Re: Content Workflow issue with Upgrade

Hi Beth,

You are using the source code right? How did you  obtain it? using TortosieHG or downloading a .zip generated by codeplex? The later is known to result in some strange results.

When you deploy to your production site are you deploying your own build or the pre-compiled release packages I produce?

To be honest for those like you and Jamie who use the source code and have a staging environment it is much more helpful to me if you update your dev/staging environment to the latest code before I make a release, that way if you  find any problems in testing I can fix them right away and you can pull the latest and build again to verify the fix and this helps me avoid bugs in the final release. Fairly often I have to patch the release packages when bugs get reported after the release. I test as well as I can and always run the latest code on my sites to try and shake out any bugs before a release but its not like I have a team of QA people at my disposal so I rely on the community and it is much easier and faster to fix bugs when people are working against the latest code from the repository.

Best,

Joe

12/22/2011 12:08:52 PM
Gravatar
Total Posts 130

Re: Content Workflow issue with Upgrade

Hellllllo!

I'm using the source code which I obtained through TortoiseHG.  I was careful to follow your upgrading instructions. I deploy from my own build, not the pre-compiled release. 

I totally understand how challenging it must be to catch some bugs while developing the next version ... the solution is gigantic and the bugs are often subtle and don't show up until you are using it for the daily, in-depth work (as well as my Site Editors for 32 sites!).

In that regard I'm happy to help the community, but as you can see I haven't been the most diligent in upgrading regularly :-P  The amount of sites (and skins) I have makes it a bit of an ordeal, but I hope to be better than upgrading once a year!

Since I have the full source if you want me to pull down some changes you've made and test them out, I'm happy to do so.  It's in both our interests

~ Beth

12/22/2011 12:24:13 PM
Gravatar
Total Posts 18439

Re: Content Workflow issue with Upgrade

Hi Beth,

It would be extremely helpful if you could pull down all the changesets for the very latest code and update your working copy to the latest code, rebuild the solution. Then I know you have the exact same code as me and if you find any problems I'll fix them right away then you can pull/update and build again and we can be sure that workflow or anything else is working correctly for you before the new release. I plan to make the release next Wednesday so anything you can test between now and Tuesday would be really great help. I'm pretty sure the workflow stuff is working correctly now but if you could verify that on your end it would be ideal.

Thanks so much for your help!

Best,

Joe

12/22/2011 3:14:20 PM
Gravatar
Total Posts 130

Re: Content Workflow issue with Upgrade

Joe,

I will do my best ... my vacation starts at 5p today (through New Years) and I'll be traveling to family tomorrow ... I'll make some time on Monday to pull it down and test it out since I can't make any guarantees over the holiday.  Sorry I likely won't be able to get to it sooner!

~ Beth

You must sign in to post in the forums. This thread is closed to new posts.