[jira] Updated: (OFBIZ-2255) Security update (Link to hidden form change) for Visual Theme selection
[ https://issues.apache.org/jira/browse/OFBIZ-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Busco updated OFBIZ-2255: --- Attachment: VisualThemeLinkToForm.patch Security update (Link to hidden form change) for Visual Theme selection --- Key: OFBIZ-2255 URL: https://issues.apache.org/jira/browse/OFBIZ-2255 Project: OFBiz Issue Type: Bug Components: framework Reporter: Bruno Busco Attachments: VisualThemeLinkToForm.patch Please find attached a patch to fix this. Thank you, -Bruno -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2255) Security update (Link to hidden form change) for Visual Theme selection
[ https://issues.apache.org/jira/browse/OFBIZ-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Busco updated OFBIZ-2255: --- Summary: Security update (Link to hidden form change) for Visual Theme selection (was: Securety update (Link to hidden form change) for Visual Theme selection) Security update (Link to hidden form change) for Visual Theme selection --- Key: OFBIZ-2255 URL: https://issues.apache.org/jira/browse/OFBIZ-2255 Project: OFBiz Issue Type: Bug Components: framework Reporter: Bruno Busco Attachments: VisualThemeLinkToForm.patch Please find attached a patch to fix this. Thank you, -Bruno -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-2255) Securety update (Link to hidden form change) for Visual Theme selection
Securety update (Link to hidden form change) for Visual Theme selection --- Key: OFBIZ-2255 URL: https://issues.apache.org/jira/browse/OFBIZ-2255 Project: OFBiz Issue Type: Bug Components: framework Reporter: Bruno Busco Attachments: VisualThemeLinkToForm.patch Please find attached a patch to fix this. Thank you, -Bruno -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Delaying Release Branch 9.3 for about 2 weeks (was: Press Release for Release Branch 9.3)
This will let that a framework-only installation will be usable by users. They will be able to login and configure their home portal page choosing between the framework resourced portlets. -Bruno 2009/3/27 David E Jones david.jo...@hotwaxmedia.com: I apologize, I thought we had discussed this and based on replies that there was a general understanding of what the point of a portal component in the framework would be. The general idea is to have a webapp that is part of the framework that any user can go to and see a home screen sort of thing that is appropriate for their role(s). In other words we would have a number of portal pages pre-configured for different roles, and permissions to determine ability to access each. If a user has a permission then the portal page is available to them, and there could more than one portal page. One of the nice things about the portal idea is that we can have a large library of portlets, which would just be thinly wrapped screens and shouldn't be too hard to build (not automatic, but not tons of work either). With these in place a user can customize the OOTB portal pages or maybe even create their own. Anyway, this OOTB application would be a generic place to see the portal pages available and such. The reason to have it in the framework is to have it be a fundamental part of the project that other components can build on, mostly by configuring portal pages and pointing to portlets made available in that component or others in depends on. In short this enables an alternate, and easily configurable, UI. -David On Mar 26, 2009, at 7:16 PM, Hans Bakker wrote: Hi David, this sounds fine...thanks for taking the lead in this, excellent! I do not quite understand what idea you have moving the myportal into the framework because it think most of it is already there? regards Hans On Thu, 2009-03-26 at 10:19 -0600, David E Jones wrote: I'm thinking we should delay the release branch for a couple of weeks. Some reasons: 1. more opportunity to collaborate with the PRC on the press release 2. time to find and fix more issue relating to the new security policy of no fields submitted to service-backed events in the URL, ie the link to form conversion thingy that is underway (I thought we were closer than we are, and I'm guessing it will take a little time for all of these to shake out) 3. time to get myportal generalized and moved to framework 4. time to get the new OFBiz home page and sub-content in place, and time for more people (outside of the PMC so far) to offer feedback on it 5. opportunity to compile a larger list of new features (basically effort going into expanding the Main New Features page), and perhaps other marketing related things in and outside of OFBiz (ie: if you are a service or derivative work or whatever provider, this is your chance to fancy up your web site and other things before the PR push related to the release branch!) 6. other things? In short, there are a few things up in the air that would be nice to have happen around the same time as the release branch. It's true that the cutoff date for the release branch is somewhat arbitrary, or in other words that features in the branch aren't as big a deal as the focus for the release branch is stabilization and not new features. Still, this release branch should be the main stabilized branch for the next 1-2 years for OFBiz, so fixing issues we know are in the trunk before the branch will help things considerably. We haven't voted on an official date or anything, and won't until the actual date to release, so this is all about communication for the sake of coordination. Comments more than welcome. In fact, I demand that you comment right now! ;) -David On Mar 25, 2009, at 4:32 PM, David E Jones wrote: I've started putting together some ideas for the press release for our upcoming release branch. The time is a little tight... I had planned on doing this last week but it got lost among other things. To facilitate collaboration on this I've created a confluence page for it here: http://docs.ofbiz.org/display/OFBADMIN/Press+Release+for+Release+Branch+9.3 Before writing the actual press release I thought we should do some brainstorming, so please add thoughts there (if you are a committer) or respond to this message with other thoughts. I'm going to send a message to the ASF PRC to ask for their help and guidance on this. It may be that they write the actual press release, so our brainstorming thoughts and details we add there are probably the most important part of what we as a community put into this. Thanks! -David -- Antwebsystems.com: Quality OFBiz services for competitive rates
[jira] Created: (OFBIZ-2256) Secure URLs
Secure URLs --- Key: OFBIZ-2256 URL: https://issues.apache.org/jira/browse/OFBIZ-2256 Project: OFBiz Issue Type: Bug Components: ALL COMPONENTS Affects Versions: Release Branch 9.3 Reporter: Jacques Le Roux You may add here in coments any URL that must be secured. And after they are secured use \-secured\- to show the URL -secured- in following comments (here I escaped \- to show how to do it) Some URLs from the user ML Page:(Show and Edit yield same issue) https://localhost:8443/manufacturing/control/ShowProductionRun?productionRunId=1 https://localhost:8443/manufacturing/control/EditProductionRun?productionRunId=1 Links: https://localhost:8443/manufacturing/control/scheduleProductionRun?productionRunId=1statusId=PRUN_SCHEDULED https://localhost:8443/manufacturing/control/changeProductionRunStatusToPrinted?productionRunId=1 https://localhost:8443/manufacturing/control/quickChangeProductionRunStatus?productionRunId=1statusId=PRUN_COMPLETED https://localhost:8443/manufacturing/control/quickChangeProductionRunStatus?productionRunId=1statusId=PRUN_CLOSED https://localhost:8443/manufacturing/control/cancelProductionRun?productionRunId=1 Page: https://localhost:8443/manufacturing/control/ProductionRunTasks?productionRunId=1 Links: https://localhost:8443/manufacturing/control/deleteProductionRunRoutingTask?workEffortId=10001productionRunId=1 Page: https://localhost:8443/manufacturing/control/ProductionRunComponents?productionRunId=1 Links: https://localhost:8443/manufacturing/control/deleteProductionRunComponent?workEffortId=10001fromDate=2009-03-25%2018:17:52.023productId=ETH_BRANDworkEffortGoodStdTypeId=PRUNT_PROD_NEEDEDproductionRunId=1 Page: https://localhost:8443/manufacturing/control/ProductionRunFixedAssets?productionRunId=1 Links: https://localhost:8443/manufacturing/control/removeWorkEffortFixedAssetAssign?workEffortId=10001fixedAssetId=DEMO_MACHINE_GROUPfromDate=2009-03-25%2018:17:50.858productionRunId=1 Page: https://localhost:8443/manufacturing/control/EditRoutingTaskAssoc?workEffortId=10010 Links: https://localhost:8443/manufacturing/control/RemoveRoutingTaskAssoc?workEffortId=10010workEffortIdFrom=10010workEffortIdTo=TASK01fromDate=2009-03-26%2013:55:55.447workEffortAssocTypeId=ROUTING_COMPONENT Page: https://localhost:8443/manufacturing/control/EditRoutingProductLink?workEffortId=10010 Links: https://localhost:8443/manufacturing/control/removeRoutingProductLink?workEffortId=10010productId=PC001fromDate=2009-03-26%2013:55:27.000workEffortGoodStdTypeId=ROU_PROD_TEMPLATE Page: https://localhost:8443/manufacturing/control/FindCalendar Links: https://localhost:8443/manufacturing/control/RemoveCalendar?calendarId=DEFAULT Page: https://localhost:8443/manufacturing/control/ListCalendarWeek Links: https://localhost:8443/manufacturing/control/RemoveCalendarWeek?calendarWeekId=DEFAULT Page: https://localhost:8443/manufacturing/control/EditCostCalcs Links: https://localhost:8443/manufacturing/control/removeCostComponentCalc?costComponentCalcId=EXAMPLE_COST Here are some more as of 758871: Page: https://localhost:8443/ecommerce/control/orderstatus?orderId=WSCO10001 Links: https://localhost:8443/ecommerce/control/cancelOrderItem?orderItemSeqId=3 Page: https://localhost:8443/ecommerce/control/updatePostalAddress Links: https://localhost:8443/ecommerce/control/createPartyContactMechPurpose?contactMechId=10003useValues=true Page: https://localhost:8443/ecommerce/control/viewprofile Links: https://localhost:8443/ecommerce/control/setprofiledefault/viewprofile?productStoreId=9000defaultPayMeth=10001partyId=1 https://localhost:8443/ecommerce/control/deleteCustomerTaxAuthInfo?partyId=1taxAuthPartyId=ON_TAXMANtaxAuthGeoId=ONfromDate=2009-03-26%2017:48:43.350 https://localhost:8443/ecommerce/control/readmessage?communicationEventId=10001 Page: https://localhost:8443/ecommerce/control/messagelist?showSent=true Links: https://localhost:8443/ecommerce/control/readmessage?communicationEventId=1 Page: https://localhost:8443/ordermgr/control/orderview?orderId=WSCO1 Links: https://localhost:8443/facility/control/createShipment?primaryOrderId=WSCO1primaryShipGroupSeqId=1statusId=SHIPMENT_INPUToriginFacilityId=WebStoreWarehouseexternalLoginKey=EL830506554502 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2256) Secure URLs
[ https://issues.apache.org/jira/browse/OFBIZ-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-2256: --- Description: You may add here in coments any URL that must be secured. And after they have been secured use \-secured\- to show the -secured- URLs in following comments (here I escaped - using \ to show how to do it) Some URLs from the user ML Page:(Show and Edit yield same issue) https://localhost:8443/manufacturing/control/ShowProductionRun?productionRunId=1 https://localhost:8443/manufacturing/control/EditProductionRun?productionRunId=1 Links: https://localhost:8443/manufacturing/control/scheduleProductionRun?productionRunId=1statusId=PRUN_SCHEDULED https://localhost:8443/manufacturing/control/changeProductionRunStatusToPrinted?productionRunId=1 https://localhost:8443/manufacturing/control/quickChangeProductionRunStatus?productionRunId=1statusId=PRUN_COMPLETED https://localhost:8443/manufacturing/control/quickChangeProductionRunStatus?productionRunId=1statusId=PRUN_CLOSED https://localhost:8443/manufacturing/control/cancelProductionRun?productionRunId=1 Page: https://localhost:8443/manufacturing/control/ProductionRunTasks?productionRunId=1 Links: https://localhost:8443/manufacturing/control/deleteProductionRunRoutingTask?workEffortId=10001productionRunId=1 Page: https://localhost:8443/manufacturing/control/ProductionRunComponents?productionRunId=1 Links: https://localhost:8443/manufacturing/control/deleteProductionRunComponent?workEffortId=10001fromDate=2009-03-25%2018:17:52.023productId=ETH_BRANDworkEffortGoodStdTypeId=PRUNT_PROD_NEEDEDproductionRunId=1 Page: https://localhost:8443/manufacturing/control/ProductionRunFixedAssets?productionRunId=1 Links: https://localhost:8443/manufacturing/control/removeWorkEffortFixedAssetAssign?workEffortId=10001fixedAssetId=DEMO_MACHINE_GROUPfromDate=2009-03-25%2018:17:50.858productionRunId=1 Page: https://localhost:8443/manufacturing/control/EditRoutingTaskAssoc?workEffortId=10010 Links: https://localhost:8443/manufacturing/control/RemoveRoutingTaskAssoc?workEffortId=10010workEffortIdFrom=10010workEffortIdTo=TASK01fromDate=2009-03-26%2013:55:55.447workEffortAssocTypeId=ROUTING_COMPONENT Page: https://localhost:8443/manufacturing/control/EditRoutingProductLink?workEffortId=10010 Links: https://localhost:8443/manufacturing/control/removeRoutingProductLink?workEffortId=10010productId=PC001fromDate=2009-03-26%2013:55:27.000workEffortGoodStdTypeId=ROU_PROD_TEMPLATE Page: https://localhost:8443/manufacturing/control/FindCalendar Links: https://localhost:8443/manufacturing/control/RemoveCalendar?calendarId=DEFAULT Page: https://localhost:8443/manufacturing/control/ListCalendarWeek Links: https://localhost:8443/manufacturing/control/RemoveCalendarWeek?calendarWeekId=DEFAULT Page: https://localhost:8443/manufacturing/control/EditCostCalcs Links: https://localhost:8443/manufacturing/control/removeCostComponentCalc?costComponentCalcId=EXAMPLE_COST Here are some more as of 758871: Page: https://localhost:8443/ecommerce/control/orderstatus?orderId=WSCO10001 Links: https://localhost:8443/ecommerce/control/cancelOrderItem?orderItemSeqId=3 Page: https://localhost:8443/ecommerce/control/updatePostalAddress Links: https://localhost:8443/ecommerce/control/createPartyContactMechPurpose?contactMechId=10003useValues=true Page: https://localhost:8443/ecommerce/control/viewprofile Links: https://localhost:8443/ecommerce/control/setprofiledefault/viewprofile?productStoreId=9000defaultPayMeth=10001partyId=1 https://localhost:8443/ecommerce/control/deleteCustomerTaxAuthInfo?partyId=1taxAuthPartyId=ON_TAXMANtaxAuthGeoId=ONfromDate=2009-03-26%2017:48:43.350 https://localhost:8443/ecommerce/control/readmessage?communicationEventId=10001 Page: https://localhost:8443/ecommerce/control/messagelist?showSent=true Links: https://localhost:8443/ecommerce/control/readmessage?communicationEventId=1 Page: https://localhost:8443/ordermgr/control/orderview?orderId=WSCO1 Links: https://localhost:8443/facility/control/createShipment?primaryOrderId=WSCO1primaryShipGroupSeqId=1statusId=SHIPMENT_INPUToriginFacilityId=WebStoreWarehouseexternalLoginKey=EL830506554502 was: You may add here in coments any URL that must be secured. And after they are secured use \-secured\- to show the URL -secured- in following comments (here I escaped \- to show how to do it) Some URLs from the user ML Page:(Show and Edit yield same issue) https://localhost:8443/manufacturing/control/ShowProductionRun?productionRunId=1 https://localhost:8443/manufacturing/control/EditProductionRun?productionRunId=1 Links: https://localhost:8443/manufacturing/control/scheduleProductionRun?productionRunId=1statusId=PRUN_SCHEDULED
[jira] Closed: (OFBIZ-2255) Security update (Link to hidden form change) for Visual Theme selection
[ https://issues.apache.org/jira/browse/OFBIZ-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-2255. -- Resolution: Fixed Fix Version/s: SVN trunk Assignee: Bruno Busco Thanks Bruno, Your patch is in trunk at revision: 759044 Security update (Link to hidden form change) for Visual Theme selection --- Key: OFBIZ-2255 URL: https://issues.apache.org/jira/browse/OFBIZ-2255 Project: OFBiz Issue Type: Bug Components: framework Reporter: Bruno Busco Assignee: Bruno Busco Fix For: SVN trunk Attachments: VisualThemeLinkToForm.patch Please find attached a patch to fix this. Thank you, -Bruno -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Press Release for Release Branch 9.3
Maybe that's why Ubuntu renumbered Dapper Drake from 6.04 to 6.06 ? (Actually I think it was from real delays they got) Jacques PS : don't you think OFBiz is sufficiently important to have versions names like Ubuntu does ? Could be Wind not superstitious. Mmm... I'm bad at marketing, noway... :D From: Shi Yusen sh...@langhua.cn Just for fun: symbolpronounce meaning 9 immediately,now . click 4 die 9.4 now click and die HAHA Anyway, happy the great release is coming. Shi Yusen/Beijing Langhua Ltd. 在 2009-03-26四的 11:37 -0600，David E Jones写道： While not superstitious I do find numerology to be interesting... Could you explain some of the background behind 9.4? Thanks, -David On Mar 26, 2009, at 11:33 AM, Shi Yusen wrote: Personally, I would prefer keeping 9.3 rather than 9.4 for the version number. 9.4 is a very bad number in Chinese. :) Or 9.5? Shi Yusen/Beijing Langhua Ltd. 在 2009-03-25三的 16:32 -0600，David E Jones写道： I've started putting together some ideas for the press release for our upcoming release branch. The time is a little tight... I had planned on doing this last week but it got lost among other things. To facilitate collaboration on this I've created a confluence page for it here: http://docs.ofbiz.org/display/OFBADMIN/Press+Release+for+Release+Branch+9.3 Before writing the actual press release I thought we should do some brainstorming, so please add thoughts there (if you are a committer) or respond to this message with other thoughts. I'm going to send a message to the ASF PRC to ask for their help and guidance on this. It may be that they write the actual press release, so our brainstorming thoughts and details we add there are probably the most important part of what we as a community put into this. Thanks! -David
Re: Delaying Release Branch 9.3 for about 2 weeks (was: Press Release for Release Branch 9.3)
+ 1 Bilgin On Mar 26, 2009, at 6:19 PM, David E Jones wrote: I'm thinking we should delay the release branch for a couple of weeks. Some reasons: 1. more opportunity to collaborate with the PRC on the press release 2. time to find and fix more issue relating to the new security policy of no fields submitted to service-backed events in the URL, ie the link to form conversion thingy that is underway (I thought we were closer than we are, and I'm guessing it will take a little time for all of these to shake out) 3. time to get myportal generalized and moved to framework 4. time to get the new OFBiz home page and sub-content in place, and time for more people (outside of the PMC so far) to offer feedback on it 5. opportunity to compile a larger list of new features (basically effort going into expanding the Main New Features page), and perhaps other marketing related things in and outside of OFBiz (ie: if you are a service or derivative work or whatever provider, this is your chance to fancy up your web site and other things before the PR push related to the release branch!) 6. other things? In short, there are a few things up in the air that would be nice to have happen around the same time as the release branch. It's true that the cutoff date for the release branch is somewhat arbitrary, or in other words that features in the branch aren't as big a deal as the focus for the release branch is stabilization and not new features. Still, this release branch should be the main stabilized branch for the next 1-2 years for OFBiz, so fixing issues we know are in the trunk before the branch will help things considerably. We haven't voted on an official date or anything, and won't until the actual date to release, so this is all about communication for the sake of coordination. Comments more than welcome. In fact, I demand that you comment right now! ;) -David On Mar 25, 2009, at 4:32 PM, David E Jones wrote: I've started putting together some ideas for the press release for our upcoming release branch. The time is a little tight... I had planned on doing this last week but it got lost among other things. To facilitate collaboration on this I've created a confluence page for it here: http://docs.ofbiz.org/display/OFBADMIN/Press+Release+for+Release+Branch+9.3 Before writing the actual press release I thought we should do some brainstorming, so please add thoughts there (if you are a committer) or respond to this message with other thoughts. I'm going to send a message to the ASF PRC to ask for their help and guidance on this. It may be that they write the actual press release, so our brainstorming thoughts and details we add there are probably the most important part of what we as a community put into this. Thanks! -David
[jira] Commented: (OFBIZ-1235) Create the theme for the form widget
[
https://issues.apache.org/jira/browse/OFBIZ-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12689866#action_12689866
]
Jacopo Cappellato commented on OFBIZ-1235:
--
Guo,
thank you so much for your work; your last patch is in svn with rev. 759086
I know it is still a work in progress, but I think it will be easier for you
and me to work incrementally; of course feel free to send more patches as they
are ready.
I did a small change: instead of using lowagie HtmlEncoder I have used the
StringUtil methods.
Also, please move the MacroFormRenderer class from the screen to the form
package: I didn't do this myself to avoid to you headaches because I know that
you are still modifying the class.
Jacopo
Create the theme for the form widget
Key: OFBIZ-1235
URL: https://issues.apache.org/jira/browse/OFBIZ-1235
Project: OFBiz
Issue Type: New Feature
Components: framework
Affects Versions: SVN trunk
Environment: all the platform
Reporter: WeizhanGuo
Assignee: Jacopo Cappellato
Fix For: SVN trunk
Attachments: ftlMacroRenderer.patch, ftlMacroRenderer.patch,
widget.patch
We are creating the theme for the ofbiz widget form, why we create this? We
found it's very difficultty to extend the current form widget, all the widget
generation code is hard code in HtmlFormRenderer or others, we need to change
those file if we want to add some function to the form, like ajax.
And yes, we have some ajax function in ofbiz now, but the code of
HtmlFormRenderer with ajax is much harder for understanding. like the code:
if(ajaxEnabled). In fact , we want to implement the dojo function in ofbiz
without mess.
So we decide to extract the hard code is responsible for the html form
generation to the ftl files, like the struts2 does. If you know well about
struts2, then you will also know the form theme we are creating.
Those ftl files is responsible for the html code generation, like text.ftl:
input type=text#rt/
name=${rp.name?default()?html}#rt/
#include class.ftl /
#if rp.value?exists
#escape x as x?html value=${rp.value} /#escape #rt/
/#if
#if rp.textSize?exists
size=${rp.textSize?html}#rt/
/#if
#if rp.maxlength?exists
maxlength=${rp.maxlength?html}#rt/
/#if
#if rp.textId?exists
id=${rp.textId?html}#rt/
/#if
#if rp.event?exists rp.action?exists
${rp.event?html}=${rp.action?html}#rt/
/#if
#if rp.clientAutocomplete?exists !rp.clientAutocomplete
autocomplete=off#rt/
/#if
/
Then, in the renderTextField method, we use the ftl file to generate the html
text instand of the hard code.
Finally,we can have different themes like simple/text.ftl ajax/text.ftl and
dojo/text.ftl. By setting the theme with code theme=simple/ajax/dojo , the
corresponding theme file like text.ftl will be loaded. The attachment is the
dojo theme capture.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1825) Colors and localisation for the calendar
[
https://issues.apache.org/jira/browse/OFBIZ-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12689858#action_12689858
]
Jacques Le Roux commented on OFBIZ-1825:
Hi Marco, Todor,
I wanted to put the calendar localisation in the 9.4 release which will be
release soon.
But if you think it can't be done in the following 2 weeks simply tell me and I
will remove this issue from the 9.4 schedule
Thanks
Colors and localisation for the calendar
Key: OFBIZ-1825
URL: https://issues.apache.org/jira/browse/OFBIZ-1825
Project: OFBiz
Issue Type: Improvement
Components: ALL COMPONENTS
Affects Versions: SVN trunk
Reporter: Jacques Le Roux
Assignee: Jacques Le Roux
Priority: Minor
Fix For: Release Branch 9.3
Attachments: calendar.patch, calendar_sequence.patch,
calendarDateSelectColor.patch, calendarDateSelectColor.patch,
calendarModified.patch, CommonScreens.patch, Existing.jpg,
LocalizedDate_it.patch, Proposition.jpg, WE_CAL.gif
I tried to change the calendar colors, to be more in the OFBiz way. Please
let me you know what you think.
I also changed some colors to respect our CSS best practices (no color names).
Here are some remarks :
Colors
* I kept the 3 chars scheme when it's was obvious. For instance we don't
need to set #00 or #ff when actually #000 or #fff is sufficient.
* I used Wikipedia as reference http://en.wikipedia.org/wiki/Web_colors for
choising colors. While doing this change I wondered if we could not authorise
and even recommend to use sandard names for colors as shown in Wikipedia
page. I found it easier to recall a color by its names than by an hexa
number...! As long as we would use this Wikipedia reference I think it could
be possible to use names instead of hexa, WDYT ?
* The days initials are not centered but at left (It's late and I did not
found the reason)
We need to provide a localisation mean. From
http://electronicholas.com/calendar?style=defaultformat=natural it should
not be too hard. I propose a simple way, maybe we can do better
* More calendar formats in a calendar.properties file (like the euro or
american ones)
* For the moment I think all string are harcoded in calendar_date_select.js
Date.weekdays = $w(S M T W T F S);
Date.first_day_of_week = 0;
Date.months = $w(January February March April May June July August
September October November December );
_translations = {
OK: OK,
Now: Now,
Today: Today
}
A very simple way (but not very clever I must admit) could be to set a
property for the language to use in calendar.properties file and use it in a
switch statement with hardcoded strings in calendar_date_select.js. Is
anybody aware of better ways to do that in Javascript or Prototype ?
BTW I think we should delete calendarstyles.css and calendarTable.css. If
it's ok, I will do it when I will upate the attached patch later.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: whitespace patches
Done, please comment if any problem http://docs.ofbiz.org/x/mg Jacques From: Jacques Le Roux jacques.le.r...@les7arts.com I was ready to change/refactor this page, notably, in the 1st section, I will suggest to use Anyedit plugin in Eclipse for trailing spaces. But I'd like to make a proposition before. Like Adrian (http://markmail.org/thread/sesxygbc6kj5r2yc) I really prefer to use 2 spaces indentation in FTL, could we change our conventions to use 2 spaces in FTL/HTML files ? Also I'd like to know if we should use 2 spaces for XML. There are plenty of files where 2 spaces is used (notably in *model*.xml files) and I found this often annoying when dealing whith those files (parching, merging, commiting changes, etc.). IMO, 4 space should be olny used in java files and groovy, and 2 spaces everywhere else (but I may miss some types of files to be put in the 4 spaces group, if you see one please react) Jacques From: Jacques Le Roux jacques.le.r...@les7arts.com Yes, good point. I will wait to see Adam's progress... If nobody see a problem with the changes he proposed (seems OK nobody growled) Jacques From: Stephen Rufle sru...@salmonllc.com If this the removal of trailing spaces is done, would it be good to also update your comment on http://docs.ofbiz.org/display/OFBADMIN/Coding+Conventions Change the AnyEdit plug in section to have Remove trailing whitespace to true Jacques Le Roux wrote: I did something like that sometimes ago, but only to transform tabs into spaces. I'm not against cleaning this aspect of the code. We could do it now, I mean before freezing 9.3, since there has been already a lot of changes recently So +1 Jacques From: BJ Freeman bjf...@free-man.net sorry missed that part Adam Heath sent the following on 3/13/2009 11:19 AM: BJ Freeman wrote: My thought was the it could be run before patches were made. Sure, but we have tons of existing code that isn't compliant, that needs to be fixed. I was asking whether I should do that now, or wait for a bit for others to speak up. -- Stephen P Rufle sru...@salmonllc.com H1:480-626-8022 H2:480-802-7173 Yahoo IM: stephen_rufle AOL IM: stephen1rufle
[jira] Updated: (OFBIZ-2256) Secure URLs
[ https://issues.apache.org/jira/browse/OFBIZ-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-2256: --- Affects Version/s: (was: Release Branch 9.3) SVN trunk Fix Version/s: Release Branch 9.3 Secure URLs --- Key: OFBIZ-2256 URL: https://issues.apache.org/jira/browse/OFBIZ-2256 Project: OFBiz Issue Type: Bug Components: ALL COMPONENTS Affects Versions: SVN trunk Reporter: Jacques Le Roux Fix For: Release Branch 9.3 You may add here in coments any URL that must be secured. And after they have been secured use \-secured\- to show the -secured- URLs in following comments (here I escaped - using \ to show how to do it) Some URLs from the user ML Page:(Show and Edit yield same issue) https://localhost:8443/manufacturing/control/ShowProductionRun?productionRunId=1 https://localhost:8443/manufacturing/control/EditProductionRun?productionRunId=1 Links: https://localhost:8443/manufacturing/control/scheduleProductionRun?productionRunId=1statusId=PRUN_SCHEDULED https://localhost:8443/manufacturing/control/changeProductionRunStatusToPrinted?productionRunId=1 https://localhost:8443/manufacturing/control/quickChangeProductionRunStatus?productionRunId=1statusId=PRUN_COMPLETED https://localhost:8443/manufacturing/control/quickChangeProductionRunStatus?productionRunId=1statusId=PRUN_CLOSED https://localhost:8443/manufacturing/control/cancelProductionRun?productionRunId=1 Page: https://localhost:8443/manufacturing/control/ProductionRunTasks?productionRunId=1 Links: https://localhost:8443/manufacturing/control/deleteProductionRunRoutingTask?workEffortId=10001productionRunId=1 Page: https://localhost:8443/manufacturing/control/ProductionRunComponents?productionRunId=1 Links: https://localhost:8443/manufacturing/control/deleteProductionRunComponent?workEffortId=10001fromDate=2009-03-25%2018:17:52.023productId=ETH_BRANDworkEffortGoodStdTypeId=PRUNT_PROD_NEEDEDproductionRunId=1 Page: https://localhost:8443/manufacturing/control/ProductionRunFixedAssets?productionRunId=1 Links: https://localhost:8443/manufacturing/control/removeWorkEffortFixedAssetAssign?workEffortId=10001fixedAssetId=DEMO_MACHINE_GROUPfromDate=2009-03-25%2018:17:50.858productionRunId=1 Page: https://localhost:8443/manufacturing/control/EditRoutingTaskAssoc?workEffortId=10010 Links: https://localhost:8443/manufacturing/control/RemoveRoutingTaskAssoc?workEffortId=10010workEffortIdFrom=10010workEffortIdTo=TASK01fromDate=2009-03-26%2013:55:55.447workEffortAssocTypeId=ROUTING_COMPONENT Page: https://localhost:8443/manufacturing/control/EditRoutingProductLink?workEffortId=10010 Links: https://localhost:8443/manufacturing/control/removeRoutingProductLink?workEffortId=10010productId=PC001fromDate=2009-03-26%2013:55:27.000workEffortGoodStdTypeId=ROU_PROD_TEMPLATE Page: https://localhost:8443/manufacturing/control/FindCalendar Links: https://localhost:8443/manufacturing/control/RemoveCalendar?calendarId=DEFAULT Page: https://localhost:8443/manufacturing/control/ListCalendarWeek Links: https://localhost:8443/manufacturing/control/RemoveCalendarWeek?calendarWeekId=DEFAULT Page: https://localhost:8443/manufacturing/control/EditCostCalcs Links: https://localhost:8443/manufacturing/control/removeCostComponentCalc?costComponentCalcId=EXAMPLE_COST Here are some more as of 758871: Page: https://localhost:8443/ecommerce/control/orderstatus?orderId=WSCO10001 Links: https://localhost:8443/ecommerce/control/cancelOrderItem?orderItemSeqId=3 Page: https://localhost:8443/ecommerce/control/updatePostalAddress Links: https://localhost:8443/ecommerce/control/createPartyContactMechPurpose?contactMechId=10003useValues=true Page: https://localhost:8443/ecommerce/control/viewprofile Links: https://localhost:8443/ecommerce/control/setprofiledefault/viewprofile?productStoreId=9000defaultPayMeth=10001partyId=1 https://localhost:8443/ecommerce/control/deleteCustomerTaxAuthInfo?partyId=1taxAuthPartyId=ON_TAXMANtaxAuthGeoId=ONfromDate=2009-03-26%2017:48:43.350 https://localhost:8443/ecommerce/control/readmessage?communicationEventId=10001 Page: https://localhost:8443/ecommerce/control/messagelist?showSent=true Links: https://localhost:8443/ecommerce/control/readmessage?communicationEventId=1 Page: https://localhost:8443/ordermgr/control/orderview?orderId=WSCO1 Links: https://localhost:8443/facility/control/createShipment?primaryOrderId=WSCO1primaryShipGroupSeqId=1statusId=SHIPMENT_INPUToriginFacilityId=WebStoreWarehouseexternalLoginKey=EL830506554502 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2243) In hyperlink and sub-hyperlink elements, replacement of target parameters by parameter sub-elements
[ https://issues.apache.org/jira/browse/OFBIZ-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-2243: --- Affects Version/s: (was: Release Branch 9.3) SVN trunk Fix Version/s: Release Branch 9.3 In hyperlink and sub-hyperlink elements, replacement of target parameters by parameter sub-elements --- Key: OFBIZ-2243 URL: https://issues.apache.org/jira/browse/OFBIZ-2243 Project: OFBiz Issue Type: Improvement Components: ALL COMPONENTS Affects Versions: SVN trunk Reporter: Jacques Le Roux Fix For: Release Branch 9.3 This issue is intended to replace, in all hyperlink and sub-hyperlink elements used in forms, screens and menus widgets, target parameters by parameter sub-elements using Eclipse regexp S/R -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Press Release for Release Branch 9.3
I guess Microsoft is the first to use this style. Windows 3.0, Windows 3.1, Windows 95, actually Windows 4.0, Windows 98, actually Windows 4.1... 在 2009-03-27五的 09:09 +0100，Jacques Le Roux写道： Maybe that's why Ubuntu renumbered Dapper Drake from 6.04 to 6.06 ? (Actually I think it was from real delays they got) Jacques PS : don't you think OFBiz is sufficiently important to have versions names like Ubuntu does ? Could be Wind not superstitious. Mmm... I'm bad at marketing, noway... :D From: Shi Yusen sh...@langhua.cn Just for fun: symbolpronounce meaning 9 immediately,now . click 4 die 9.4 now click and die HAHA Anyway, happy the great release is coming. Shi Yusen/Beijing Langhua Ltd. 在 2009-03-26四的 11:37 -0600，David E Jones写道： While not superstitious I do find numerology to be interesting... Could you explain some of the background behind 9.4? Thanks, -David On Mar 26, 2009, at 11:33 AM, Shi Yusen wrote: Personally, I would prefer keeping 9.3 rather than 9.4 for the version number. 9.4 is a very bad number in Chinese. :) Or 9.5? Shi Yusen/Beijing Langhua Ltd. 在 2009-03-25三的 16:32 -0600，David E Jones写道： I've started putting together some ideas for the press release for our upcoming release branch. The time is a little tight... I had planned on doing this last week but it got lost among other things. To facilitate collaboration on this I've created a confluence page for it here: http://docs.ofbiz.org/display/OFBADMIN/Press+Release+for+Release+Branch+9.3 Before writing the actual press release I thought we should do some brainstorming, so please add thoughts there (if you are a committer) or respond to this message with other thoughts. I'm going to send a message to the ASF PRC to ask for their help and guidance on this. It may be that they write the actual press release, so our brainstorming thoughts and details we add there are probably the most important part of what we as a community put into this. Thanks! -David
Re: Press Release for Release Branch 9.3
Not sure if it's really the 1st (you know IT industry existed for 3 decades when Microsoft appeared). Adding the month Ubuntu is a bit more precise Jacques From: Shi Yusen sh...@langhua.cn I guess Microsoft is the first to use this style. Windows 3.0, Windows 3.1, Windows 95, actually Windows 4.0, Windows 98, actually Windows 4.1... 在 2009-03-27五的 09:09 +0100，Jacques Le Roux写道： Maybe that's why Ubuntu renumbered Dapper Drake from 6.04 to 6.06 ? (Actually I think it was from real delays they got) Jacques PS : don't you think OFBiz is sufficiently important to have versions names like Ubuntu does ? Could be Wind not superstitious. Mmm... I'm bad at marketing, noway... :D From: Shi Yusen sh...@langhua.cn Just for fun: symbolpronounce meaning 9 immediately,now . click 4 die 9.4 now click and die HAHA Anyway, happy the great release is coming. Shi Yusen/Beijing Langhua Ltd. 在 2009-03-26四的 11:37 -0600，David E Jones写道： While not superstitious I do find numerology to be interesting... Could you explain some of the background behind 9.4? Thanks, -David On Mar 26, 2009, at 11:33 AM, Shi Yusen wrote: Personally, I would prefer keeping 9.3 rather than 9.4 for the version number. 9.4 is a very bad number in Chinese. :) Or 9.5? Shi Yusen/Beijing Langhua Ltd. 在 2009-03-25三的 16:32 -0600，David E Jones写道： I've started putting together some ideas for the press release for our upcoming release branch. The time is a little tight... I had planned on doing this last week but it got lost among other things. To facilitate collaboration on this I've created a confluence page for it here: http://docs.ofbiz.org/display/OFBADMIN/Press+Release+for+Release+Branch+9.3 Before writing the actual press release I thought we should do some brainstorming, so please add thoughts there (if you are a committer) or respond to this message with other thoughts. I'm going to send a message to the ASF PRC to ask for their help and guidance on this. It may be that they write the actual press release, so our brainstorming thoughts and details we add there are probably the most important part of what we as a community put into this. Thanks! -David
[jira] Updated: (OFBIZ-2257) Change the date function from bsh script to date EL in FormWidgetExampleForms.xml
[ https://issues.apache.org/jira/browse/OFBIZ-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] WeizhanGuo updated OFBIZ-2257: -- Attachment: example.patch Change the date function from bsh script to date EL in FormWidgetExampleForms.xml - Key: OFBIZ-2257 URL: https://issues.apache.org/jira/browse/OFBIZ-2257 Project: OFBiz Issue Type: Bug Components: framework Reporter: WeizhanGuo Priority: Minor Attachments: example.patch Change the date function from bsh script to date EL in FormWidgetExampleForms.xml There is no example in the module list, I select the framework as the module -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-2257) Change the date function from bsh script to date EL in FormWidgetExampleForms.xml
Change the date function from bsh script to date EL in FormWidgetExampleForms.xml - Key: OFBIZ-2257 URL: https://issues.apache.org/jira/browse/OFBIZ-2257 Project: OFBiz Issue Type: Bug Components: framework Reporter: WeizhanGuo Priority: Minor Attachments: example.patch Change the date function from bsh script to date EL in FormWidgetExampleForms.xml There is no example in the module list, I select the framework as the module -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-2258) Update the Chinese password incorrect tip from 密码不争取 to 密码不正确
Update the Chinese password incorrect tip from 密码不争取 to 密码不正确 - Key: OFBIZ-2258 URL: https://issues.apache.org/jira/browse/OFBIZ-2258 Project: OFBiz Issue Type: Bug Components: framework Reporter: WeizhanGuo Priority: Trivial Attachments: passwordTips.patch Update the Chinese password incorrect tip from 密码不争取 to 密码不正确, 密码不争取 is incorrect -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2258) Update the Chinese password incorrect tip from 密码不争取 to 密码不正确
[ https://issues.apache.org/jira/browse/OFBIZ-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] WeizhanGuo updated OFBIZ-2258: -- Attachment: passwordTips.patch Update the Chinese password incorrect tip from 密码不争取 to 密码不正确 - Key: OFBIZ-2258 URL: https://issues.apache.org/jira/browse/OFBIZ-2258 Project: OFBiz Issue Type: Bug Components: framework Reporter: WeizhanGuo Priority: Trivial Attachments: passwordTips.patch Update the Chinese password incorrect tip from 密码不争取 to 密码不正确, 密码不争取 is incorrect -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: new functionality in the controller
Hi Hans, I don't see any xsl file related, so I suppose that this is a file you use locally ? I'd suggest to create a new page (Something titled like Navigating back to a screen) under the FAQ and to put a link to it in the Development tips section. Actually, at this stage, though Development tips section seems appropriate, it's not so important to have it in a place or another. Things are not already completly well organised. But having it somewhere easily reachable (using wiki search) and *modifiable* by everyone is a plus. Thanks Jacques PS : please when you will be editing the main FAQ page, as recommended at top, use the Wiki Markup mode, thanks From: Hans Bakker mailingl...@antwebsystems.com To: Jacques Le Roux jacques.le.r...@les7arts.com on which wiki page? i have documented this in the xsl file. On Fri, 2009-03-27 at 12:36 +0100, Jacques Le Roux wrote: I think a way to avoid the hassle David reported is to write directly indications (at large, for any substantial effort) in the wiki and to refer/amend them after. It's maybe obvious, but we are still few to do that... Of course, organizing the wiki for a community is another issue... Maybe we could enact some simple rules... ? Jacques From: Pranay Pandey pranay.pan...@hotwaxmedia.com +1 This should be available on wiki. Thanks Regards -- Pranay Pandey On Mar 27, 2009, at 2:01 AM, Jacques Le Roux wrote: Thanks for the clear explanation Hans! Maybe we could write something in the wiki about all that? Jacques From: Hans Bakker mailingl...@antwebsystems.com In the development of the mypage/myportal component I ran into a problem where i needed to show a screen (view) from different places and be able to return to the place it was called from. In the past we did that with donePage variables which was a bit messy. We discussed this in the mailing list and David came up with a solution to this problem which will save a lot of screen/form code. how does it work? In the controller.xml it is now possible to save the last view displayed and return to it at a later stage. In the response tag a parameter is added: 'save-last-view' response name=success type=view value=justAView save-last-view=true/ This will save the view that WAS displayed, not the one that is going to be displayed. Then later on it is possible to override a view with this saved view with response name=success type=view-last value=justAView/ This is working pretty good, however when i was using it in the new portal functions i found the following problems: 1. it is only possible to store the last view, not the one that is going the be displayed. If there was a 'lookup' view after the 'real' last one, that lookup got saved. So there is a need to save the 'current' view 2. sometimes you want to be able to save 2 views. A 'current' view and a 'home' view. An example is the portal page, create an email, add a role (return to email) , send the email (return to portal page=home) so i extended the implementation from David with the following tag extensions using the same pattern as the 'view-last/save-last-view': save-last-view save-current-view save-home-view view-Last view-home This is all committed with a number of other changes in revision: 758522. regards, Hans -- Antwebsystems.com: Quality OFBiz services for competitive rates -- Antwebsystems.com: Quality OFBiz services for competitive rates
[jira] Closed: (OFBIZ-2258) Update the Chinese password incorrect tip from 密码不争取 to 密码不正确
[ https://issues.apache.org/jira/browse/OFBIZ-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-2258. -- Resolution: Fixed Assignee: Jacques Le Roux Thanks Guo, Your patchis in trunk at revision: 759166 You guess what ? I did not notice :) It's easy from French to English, I don't know from Chinese to English, seems harder ;) Update the Chinese password incorrect tip from 密码不争取 to 密码不正确 - Key: OFBIZ-2258 URL: https://issues.apache.org/jira/browse/OFBIZ-2258 Project: OFBiz Issue Type: Bug Components: framework Reporter: WeizhanGuo Assignee: Jacques Le Roux Priority: Trivial Attachments: passwordTips.patch Update the Chinese password incorrect tip from 密码不争取 to 密码不正确, 密码不争取 is incorrect -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2257) Change the date function from bsh script to date EL in FormWidgetExampleForms.xml
[
https://issues.apache.org/jira/browse/OFBIZ-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12689929#action_12689929
]
Adrian Crum commented on OFBIZ-2257:
This looks good. I would like to see one minor change to make the description
more accurate:
value xml:lang=enSame as above, uses the \${date:nowTimestamp()} UEL
function to get the now timestamp/value
Change the date function from bsh script to date EL in
FormWidgetExampleForms.xml
-
Key: OFBIZ-2257
URL: https://issues.apache.org/jira/browse/OFBIZ-2257
Project: OFBiz
Issue Type: Bug
Components: framework
Reporter: WeizhanGuo
Priority: Minor
Attachments: example.patch
Change the date function from bsh script to date EL in
FormWidgetExampleForms.xml
There is no example in the module list, I select the framework as the module
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2258) Update the Chines e password incorrect tip from 密码不争取 to 密码不正确
[ https://issues.apache.org/jira/browse/OFBIZ-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12689945#action_12689945 ] WeizhanGuo commented on OFBIZ-2258: --- That's very different between Chinese and French, I don't konw any French too, but I think they are both the elegant language :) Update the Chinese password incorrect tip from 密码不争取 to 密码不正确 - Key: OFBIZ-2258 URL: https://issues.apache.org/jira/browse/OFBIZ-2258 Project: OFBiz Issue Type: Bug Components: framework Reporter: WeizhanGuo Assignee: Jacques Le Roux Priority: Trivial Attachments: passwordTips.patch Update the Chinese password incorrect tip from 密码不争取 to 密码不正确, 密码不争取 is incorrect -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
more whitespace stuff
My last set of whitespaces changes in java files missed a bunch of pure whitespace lines. I'm going to have to flood svn with 2.5M of changes. Sorry about this, I should have checked closer when I did it the last time.
Re: more whitespace stuff
It's okay - at least it will reduce compile time. -Adrian Adam Heath wrote: My last set of whitespaces changes in java files missed a bunch of pure whitespace lines. I'm going to have to flood svn with 2.5M of changes. Sorry about this, I should have checked closer when I did it the last time.
[jira] Updated: (OFBIZ-2256) Secure URLs
[ https://issues.apache.org/jira/browse/OFBIZ-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pratik Khera updated OFBIZ-2256: Attachment: OFBIZ-2256.patch Hello Jacques, I have fixed the issues for some of these URL's and here is the patch and right now i am working on rest of them. Page: https://localhost:8443/ordermgr/control/orderview?orderId=WSCO1 Links: https://localhost:8443/facility/control/createShipment?primaryOrderId=WSCO1primaryShipGroupSeqId=1statusId=SHIPMENT_INPUToriginFacilityId=WebStoreWarehouseexternalLoginKey=EL830506554502 Page: https://localhost:8443/ecommerce/control/messagelist?showSent=true Links: https://localhost:8443/ecommerce/control/readmessage?communicationEventId=1 Page: https://localhost:8443/ecommerce/control/orderstatus?orderId=WSCO10001 Links: https://localhost:8443/ecommerce/control/cancelOrderItem?orderItemSeqId=3 Secure URLs --- Key: OFBIZ-2256 URL: https://issues.apache.org/jira/browse/OFBIZ-2256 Project: OFBiz Issue Type: Bug Components: ALL COMPONENTS Affects Versions: SVN trunk Reporter: Jacques Le Roux Fix For: Release Branch 9.3 Attachments: OFBIZ-2256.patch You may add here in coments any URL that must be secured. And after they have been secured use \-secured\- to show the -secured- URLs in following comments (here I escaped - using \ to show how to do it) Some URLs from the user ML Page:(Show and Edit yield same issue) https://localhost:8443/manufacturing/control/ShowProductionRun?productionRunId=1 https://localhost:8443/manufacturing/control/EditProductionRun?productionRunId=1 Links: https://localhost:8443/manufacturing/control/scheduleProductionRun?productionRunId=1statusId=PRUN_SCHEDULED https://localhost:8443/manufacturing/control/changeProductionRunStatusToPrinted?productionRunId=1 https://localhost:8443/manufacturing/control/quickChangeProductionRunStatus?productionRunId=1statusId=PRUN_COMPLETED https://localhost:8443/manufacturing/control/quickChangeProductionRunStatus?productionRunId=1statusId=PRUN_CLOSED https://localhost:8443/manufacturing/control/cancelProductionRun?productionRunId=1 Page: https://localhost:8443/manufacturing/control/ProductionRunTasks?productionRunId=1 Links: https://localhost:8443/manufacturing/control/deleteProductionRunRoutingTask?workEffortId=10001productionRunId=1 Page: https://localhost:8443/manufacturing/control/ProductionRunComponents?productionRunId=1 Links: https://localhost:8443/manufacturing/control/deleteProductionRunComponent?workEffortId=10001fromDate=2009-03-25%2018:17:52.023productId=ETH_BRANDworkEffortGoodStdTypeId=PRUNT_PROD_NEEDEDproductionRunId=1 Page: https://localhost:8443/manufacturing/control/ProductionRunFixedAssets?productionRunId=1 Links: https://localhost:8443/manufacturing/control/removeWorkEffortFixedAssetAssign?workEffortId=10001fixedAssetId=DEMO_MACHINE_GROUPfromDate=2009-03-25%2018:17:50.858productionRunId=1 Page: https://localhost:8443/manufacturing/control/EditRoutingTaskAssoc?workEffortId=10010 Links: https://localhost:8443/manufacturing/control/RemoveRoutingTaskAssoc?workEffortId=10010workEffortIdFrom=10010workEffortIdTo=TASK01fromDate=2009-03-26%2013:55:55.447workEffortAssocTypeId=ROUTING_COMPONENT Page: https://localhost:8443/manufacturing/control/EditRoutingProductLink?workEffortId=10010 Links: https://localhost:8443/manufacturing/control/removeRoutingProductLink?workEffortId=10010productId=PC001fromDate=2009-03-26%2013:55:27.000workEffortGoodStdTypeId=ROU_PROD_TEMPLATE Page: https://localhost:8443/manufacturing/control/FindCalendar Links: https://localhost:8443/manufacturing/control/RemoveCalendar?calendarId=DEFAULT Page: https://localhost:8443/manufacturing/control/ListCalendarWeek Links: https://localhost:8443/manufacturing/control/RemoveCalendarWeek?calendarWeekId=DEFAULT Page: https://localhost:8443/manufacturing/control/EditCostCalcs Links: https://localhost:8443/manufacturing/control/removeCostComponentCalc?costComponentCalcId=EXAMPLE_COST Here are some more as of 758871: Page: https://localhost:8443/ecommerce/control/orderstatus?orderId=WSCO10001 Links: https://localhost:8443/ecommerce/control/cancelOrderItem?orderItemSeqId=3 Page: https://localhost:8443/ecommerce/control/updatePostalAddress Links: https://localhost:8443/ecommerce/control/createPartyContactMechPurpose?contactMechId=10003useValues=true Page: https://localhost:8443/ecommerce/control/viewprofile Links: https://localhost:8443/ecommerce/control/setprofiledefault/viewprofile?productStoreId=9000defaultPayMeth=10001partyId=1 https://localhost:8443/ecommerce/control/deleteCustomerTaxAuthInfo?partyId=1taxAuthPartyId=ON_TAXMANtaxAuthGeoId=ONfromDate=2009-03-26%2017:48:43.350
