Dani3lSun / apex-plugin-dropzone

Oracle APEX Region Plugin - Dropzone
MIT License
72 stars 19 forks source link

Dropzone plugin is broken after APEX 24.1 upgrade #93

Open bwetherall opened 5 months ago

bwetherall commented 5 months ago

Expected behavior

Customised Messages are displayed by the plugin such as "Drop files here or click to upload"

Actual behavior

"undefined" is displayed instead

APEX version (4.2.6 / 5.0.3)

APEX 24.1

We have fixed this by updating the plugin PLSQL a little bit.

1) Using the supported PROCEDURE approach rather than FUNCTION 2) Using different method for getting attributes into the PLSQL:

p_plugin.attributes.get_varchar2('attribute_01')

If anyone needs this fix get in touch :)

jeffreykemp commented 5 months ago

The issue with getting the legacy "attribute_nn" attributes was a known regression in APEX 24.1 that affects other plugins as well, I believe this should be fixed in APEX 24.1.0-22.

bwetherall commented 5 months ago

Thanks for the update @jeffreykemp

Ereback commented 4 months ago

I am using your Dropzone plugin in APEX 24.1 and I am encountering the error you mentioned. I see that you have solved it. Is there any possibility to get access to the solution?

jeffreykemp commented 4 months ago

If you're unable to update APEX itself, a workaround you can use is to paste your Google Maps API Key directly into the plugin.

  1. Under Shared Components, Plugins, edit JK64 Report Google Map R1
  2. Under Source, PL/SQL Code, find the following line:

l_api_key plugin_attr := p_plugin.attribute_01;

Modify the line to set the API key directly (put your actual Google Maps API key in), e.g.:

l_api_key plugin_attr := 'AIzaSyA-..lt1EE';

bwetherall commented 4 months ago

render_dropzone_ajax_dropzone.zip

Have attached the version of the plsql that we fixed if that helps? :) paste this into the plugin Source section. There was a dropdown to change the plugin to use procedures rather than functions too.

elizandrews-bmwmc commented 1 month ago

Thank you for the PL/SQL update @bwetherall ! Unfortunately, I am having the same problem in my application, but in APEX 23.2.6, and my version of Oracle does not include APEX_JSON. My attempts to manually recreate the get_varchar2 function result in ORA-06502 Numeric or Value Error : character string buffer too small. Does anyone have any advice for either re-writing the PL/SQL or locating a version of the APEX_JSON package I can download?

jeffreykemp commented 1 month ago

in APEX 23.2.6, and my version of Oracle does not include APEX_JSON

Every version of APEX includes APEX_JSON.

elizandrews-bmwmc commented 1 month ago

Hi Jeffrey, appreciate the quick response! Apologies for the confusion. I am relatively new to Oracle, and when I received the error "get_varchar2 must be declared" I apparently jumped to the wrong conclusion. However, I am hitting a wall with getting the function to run correctly. Any tips?

jeffreykemp commented 1 month ago

Sorry, I didn't read your comment closely enough. It seems you're trying to run the plugin for APEX 24.1 on APEX 23.2 which didn't have the new JSON attributes.

You will need to either upgrade your APEX to 24.1, or install the older version of this plugin that should work on 23.2 I think.