Databases
StackOverflow2013
Postsdbo
POMagento Built in Calendar not working in admin back end
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMagento Built in Calendar not working in admin back end
    primarykey
    data
    text
    <p>I am struck at a strange point..</p> <p>I am maintaining a Magento store which sells flowers. I have created an option for delivery date, which is of date type. Its work fine on front end, Calendar pops up, user can select the date, can change the date, can do anything, Which is normally allowed on the Calendar..</p> <p>In the back end, when I try to add an Order, I select a product, click on configure button to add add the delivery date and quantity, Calendar does not work. Although it appears when clicked on the Calendar image, but its greyed out (like it is not enabled) if I try to click on it, it just vanishes, I can't select a date, can't do even a single click on Calendar and it disappears and I am unable to create the order</p> <p>interestingly, if I manually enter the date in Calendar text field, then I can create order (delivery date is a mandatory option).</p> <p>I tried to dig the solution by going into phtml files, php files and ended at sale/orders/create where call to configure button is made. After this, I am unable to find product options popup (on which delivery date is selected) but I am unable to fix this issue.</p> <p>I tried to get google and forum helps, but at a failure yet.</p> <p>Calendar is working totally okay at front end, but its not working at backend.</p> <p>Can somebody help me? Any guideline? Where I can find product option dialog? any clue? I am trying to resolve the issue for last 4 days.</p> <p><strong>UPDATE:-</strong> STILL WONDERING OVER IT</p> <p>now, if I set up template and block hints in Mag admin, it starts working </p> <p>also, if I clear the breakpoints in admin console, it works then too</p> <p>also, its not working ONLY WHEN I TRY TO CREATE AN ORDER FROM ADMIN BACKEND AND SELECT DATE THERE, in other locations at admin backend it works </p> <p>so much annoying, please help me, its more then weeks now... Thanks.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USZaffar Saffee
    1. USZaffar Saffee
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POMagento Built in Calendar not working in admin back end
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    2. VO
      singulars
      1. POMagento Built in Calendar not working in admin back end
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    1. COIn admin, do you have any error in you JS console? What version of magento are you using?
      singulars
      1. POMagento Built in Calendar not working in admin back end
      1. USRenon Stewart
    2. COno error, its EE 1.12
      singulars
      1. POMagento Built in Calendar not working in admin back end
      1. USZaffar Saffee
    3. COthanks for hint, I tried using fire bug and found this
      singulars
      1. POMagento Built in Calendar not working in admin back end
      1. USZaffar Saffee
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload