-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pluggin not implementing APEX 20.1.0.00.13 #77
Comments
Hi @LudinJozabeth |
Hi @Dani3lSun , I assume @LudinJozabeth is talking about this new Plugin type page using the APEX wizard to create a page. Probably a plugin component setting that just needs to be turned off as using it in this style makes no sense if I am correct? Or is this option desired? I have never used that feature. Pretty sure it is new. |
Creating a page based on a plugin is a normal feature, I use it from time to time when I want to create a page and start it off with a region based on a plugin. I can reproduce this problem on apex.oracle.com (20.1.0.00.13) and on 18.2.0.00.12. As far as I can see it only occurs for this plugin. The page is not actually created at all. It's possible something in the plugin is triggering a bug in APEX, but I have no idea what this might be. The workaround is to create a Blank page first, then add the dropzone region to the page afterwards. |
Martin, that's a different issue entirely. Looks like an issue with loading the javascript file for the plugin. |
Hi Jeffrey, |
Expected behavior
To be able to implement this puggin in the new version APEX 20.1.0.00.13
Real behavior
The installation does not give an error, the pluggin is installed, but when creating a page with a custom table, all the plugging data is loaded and the page is not created
Steps to reproduce the problem
install plugin, create a new plug-in type page, fill out the form, create page
APEX version (4.2.6 / 5.0.3)
APEX 20.1.0.00.13
Used web server / version and platform (ORDS 3.0.3 / Tomcat 7 / Apache 2.4 / Linux x64)
workspace at https://apex.oracle.com/
Used web browser / version and platform (Chrome 48 Mac / Firefox 44 Windows)
chrome
The text was updated successfully, but these errors were encountered: