I have developed a module for PrestaShop and integrated the auto-update logic for modules into it and now I'm trying to test it, because the changes were submitted in the marketplace.
I get the message that there's an update for my module and if I click on "Update it!" button it shows the success message "All modules updated successfully.", but in the end nothing happend. The update button is still there and no upgrade script was run.
Did anyone came across something like this? I can't find the root cause for this.
Thanks!
It may be caused by three kind of facts :
- There is a licence with that module and you can't update to the new one because it expired. Prestashop never fixed this.
- Installation / Update script isn't working as it should and returns OK (true in fact) when it's triggered, whatever happened.
- Permissions problems, which returns no errors but doesn't work anyway.
I encourage you to check your folders permissions first and then try to download manually on Prestashop's Website if necessary.
Related
This new functionality - Link Preview / Verify Links Access / Verify Recipients Access - for MS Outlook desktop app, was ported from Web based app without changes to UI settings to turn off.
I have no idea how to skip it.
The execution of code is stuck on NewEmail.Send until the window receives "Send" or "Send Anyway" msg.
Of course, I was banging my head for 2 weeks trying to find a window by its name, etc...
and when I was in the middle of writing this plea for help one last idea came to my mind.
To comment out following line:
NewEmail.Display
It worked. From all of the sub-ideal solutions, this one is kind of satisfying. You can always put .Display in ErrorHandler. This line is here in first place, because many of macros are being run with task scheduler on VDIs/NPSAs, but some of them are being run by users, so .Display and .Send are always there as a comment or as a code.
I wonder if you have any other ways to manage this change until they will provide registry key or update the UI?
Recently all my Shopify apps have stopped working due to this error. I can still pull data from the api (photos, titles, etc) but I can no longer add items to my cart or check out. this error isn't just happening on my current build but previous builds too. I think I might have made too many requests due to refreshing pages and have been banned from the API temporarily (I've had this happen with another API before). but it's now been 2 days and still no fix.
I'm pretty confident there's nothing wrong with my code because it's happening to other websites that were working before & haven't been touched for a while.
package used: "shopify-buy": "^2.11.0"
Thanks,
Mitchell D
turns out this error occurred because I was in PAUSE AND BUILD mode. so I must be on a plan to add items to the cart using the API? they must have made this change recently
I am getting this error when trying to add weight ranges to shipping carriers that I have. It mostly seems to happen at random and I have been able to complete some of the carriers but others will cause the error every time. The console reports the following: Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
Is there a solution for this? I couldn't find anything online about it.
I have v. 1.6.1.4
Thank you!
You have to use firefox developper and when you get the "Parseerror"
using the developper tools you go to network and select your last query.
On the right you have a window with all the options of the query : cookies parameters... select response.
You should see the response of the parse error.
For me it was just a parameter of the form that could not be empty.
Putting a random word made everything work fine.
The same thing happened to me when adding weight ranges.
The annoying thing is i had to restore a backup of the tables ps_range_weight and ps_carrier.. as for every single instance of
"Prestashop Technical Error: Details: Error Thrown: [Object Object] Text Status: Parsererror" it made a new entry and i ended up with over 700 weight ranges.
Anyways, i restored to the last fucntioning versions of ps_range_weight and ps_carrier (needed doing) and disabled the standard paypal plugin from prestashop. After that it worked fine.
.
Hope this helps someone.
I have found a solution for this on Prestashop 1.7
This happened to me as well when I changed the theme, however, I checked the Database and found that the carrier ID in ps_range_weight has randomly changed!
Solution
Fix the carrier ID in the database to the correct one and this error should not be appearing again! Good luck
ps_range_weight
Let's say I have a plugin Foo in osclass. In that plugin we register a hook for when an item is posted. According to the osclass hooks documentation the only hook that is run when an item is posted is posted_item.
But as far as I can tell from looking at the code this is run after the initial item data has already been validated and stored in the database. What if a validation of some plugin specific code fails and I would like to show the user an error message and present him with the form again to give him/her the chance to alter this information? Much like if you try to submit a new item but don't fill in one of the base information like description for instance.
I can't seem to find a way to do this. Only workaround I find to avoid the item being posted despite containing invalid plugin specific data, without editing the main osclass code, is to delete the posted item again in the posted_item hook callback function of my plugin. This feels extremely cumbersome and also requires every other plugin to check that the item still exists to make sure they don't save data connected to an item that is now deleted.
What I would like, and wonder if I have missed, is a hook that is run when an item is posted but before it's written to the database and have the ability to generate "errors" that would cause the item to not be posted and the user redirected back to the form with the "error" displayed just like for the basic item information.
Anyone have a solution I have missed? This feels like a very important part of plugins and without it posted items could become very fragmented.
A user on the osclass forums (teseo) told me about the undocumented hook pre_item_add that can be used.
<?php
function cust_my_plugin($aItem) {
osc_add_flash_error_message('My plugin has a complaint.');
$pItem = new CWebItem();
$pItem->redirectTo( osc_item_post_url() );
}
osc_add_hook('pre_item_add', 'cust_my_plugin');
?>
He also sais
The only bad news is that you can't merge your plugin validation
process with that of the core script, so if the ad had an error
related to your plugin and other errors, it would be rejected twice,
one by your plugin, the second by the core script. I couldn't see any
workaround for this little issue.
I have few simple Xpages, where i test and learn the newest features in Domino 8.5.3.
Now, after some latest changes somehow i'm not able to delete Documents. The Application asks me for the User Name and password, which i enter and which are correct. However, nothing happens (well, the system thinks few seconds over) and i'm asked for my credentials again... and again.. If i press "cancel" -> i got the expected result -> error 401.
The strange thing as well, if even i give for the "anonymous" the editor rights with the "delete documents" checked, i'm still asked for the credentials...
Well, i think I need now some ideas and tips where can i look after in order to solve the "undeletable documents" problem.
The "Delete" button is made using the Simple Action "Delete Selected Documents".
Update: After looking into the logs (thanks Simon O'Doherty for the hint below!) i found out the following message
28.02.12 19:20: Exception Thrown
com.ibm.xsp.acl.NoAccessSignal: NotesException: Notes error: Document locking is enabled. You must lock the document before deleting.
After removing the setting "Allow Document locking" everything works fine.
The next question, however, and it seems to be intresting, if i want to use this setting - how to make the standart actions (it looks like at least "Delete Selected Documents" has some problems) work properly ?
Or do i have to use SSJS only ?
In the ACL settings. Click Advanced tab. Check that "Maximum Internet name and password access" is at least a level that allows you to edit documents.
May need to restart your browser for that to be registered.
If it is still an issue at that point then the following Debug may give more hints.
Check the XPages logs in the IBM_TECHNICAL_SUPPORT folder of the server.
Check the elements on the page are not being pulled from another location that would require access.
Check for Authors/Readers fields.
The following debug on the server will allow you to see when an ACL call is made, what is asked for and what it got.
Warning This is very verbose debug, so it should only be activated for the test. Also do not paste the results anywhere externally without first sanitizing. (as it would be confidential to you).
DEBUG_THREADID=1
DEBUG_SERVER_ACL=2
I have also seen this behaviour in our application.
The issue is caused by the "Allow document locking" option.
Either you do not need this feature; then just uncheck in the application properties. If you intend to use the feature, you have to lock the document in your code prior to deleting it.
Add a execute script simple action before delete simple action and write the following code
var doc:NotesDocument = currentDocument.getDocument();
doc.lock();
or
dataSource.getDocument().lock();
It might be as easy as:
- check your ACL. Do you have delete rights? Default is off