nuggetsol
Forum Replies Created
-
Forum: Plugins
In reply to: [Oasis Workflow] Create more processesOasis Workflow only has three processes at this time. You can add multiple instances (called tasks/steps) of these processes in the workflow.
If you have posts/pages in the workflow, then here’s how you can modify a workflow which is being actively used. This tutorial video will help – https://www.youtube.com/watch?v=mJ2hPsSBGcE
If you do not have any posts/pages in the workflow, you can simply drag and drop the processes in the work area and create new connections. This tutorial video should help – https://www.youtube.com/watch?v=TLWrjTvsTRs
Hope this helps.
Forum: Plugins
In reply to: [Oasis Workflow] Modal datepicker not working after theme changeI was able to reproduce the issue after activating the hueman theme.
After analyzing the issue, it looks like the hueman theme has a CSS override for the jquery “ui-datepicker” class in file themes/hueman/option-tree/assets/css/ot-admin.css on line 2888.
It has set the z-index: 101 to !important, which is overriding all the z-index.
Oasis Workflow plugin also uses jquery, but we do not override the datepicker CSS. The oasis workflow plugin uses the default jquery settings for date picker.
One option is to remove the !important from the hueman – ot-admin.css. That will fix the display issue. Go ahead and try it and see if this works.
You might have to work with the theme developer and see if there is a better solution for this issue.
Hope this helps.
Forum: Plugins
In reply to: [Oasis Workflow] Auto Submit and Workflow TeamsWith the latest version of Oasis Workflow Pro and Teams Add on, the above issue is resolved. The Teams Add on is now compatible with the Auto Submit.
Forum: Plugins
In reply to: [Oasis Workflow] Auto Submit and Workflow TeamsYes, we are working to make auto submit compatible with Teams Add on. We mentioned about it in the release notes for the Teams Add on, but I will also update the site to put this message.
We will soon release a new version of the plugin which will make Teams Add on compatible with Auto Submit.
Thanks again for choosing Oasis Workflow.
I commenting out the BPS Query String rules line by line, and finally found the offending line.
RewriteCond %{QUERY_STRING} (localhost|loopback|127\.0\.0\.1) [NC,OR]
If I remove this line what are the issues?
Nope. They don’t have any of those characters.
Wow!!! I was not expecting a response so quick especially on a Saturday evening. You guys rock.
I will try out this last option and let you know what I discover.
sorry for a late reply.
I tried the last option of adding code to “CUSTOM CODE WP REWRITE LOOP START”, but that also didn’t work.
Also, this is NOT a GWIOD site.
Let me know what I can try next.
This is a standard/single wordpress installation.
I will try the option you suggested and get back to you soon.
that’s correct. Those are not part of the URL structure.
HTTP_REFERER: https://<mysite>/my-account?action=manage_licenses&payment_id=XXX&license_id=XXX
REQUEST_URI: /my-account?action=manage_licenses&payment_id=XXX&license_id=XXX&edd_action=deactivate_site&site_url=<anothersite>&license=XXX
HTTP_REFERER: https://<mysite>/my-account?action=manage_licenses&payment_id=XXX&license_id=XXX
REQUEST_URI: /my-account?action=manage_licenses&payment_id=XXX&license_id=XXX&edd_action=deactivate_site&site_url=<anothersite>&license=XXX
XXX – represents some number.
I added that, and still that didn’t help.
Just so that I include the premium feature (edd-software-licensing) to that bypass rule, I added the following
# EDD software licensing plugin skip/bypass rule
RewriteCond %{REQUEST_URI} ^/wp-content/plugins/edd-software-licensing/ [NC]
RewriteRule . – [S=14]
# EDD plugin skip/bypass rule
RewriteCond %{REQUEST_URI} ^/wp-content/plugins/easy-digital-downloads/ [NC]
RewriteRule . – [S=13]Even the above didn’t help. 🙁
I stopped at step 1; after going back to the default .htaccess, I was able to deactivate (in other words, I’m not getting the 403 error)
Thanks for the code snippet.
I tried it, but it didn’t work 🙁
To be doubly sure, I checked the .htaccess file and it does have the above code.
Your analysis is correct. Essentially, the user is trying to deactivate the license on “another site” from his account.