Forum Replies Created
Hi,
As I checked in your live site, serialized is data already exist, no seems nothing is removed. The only issue is seme PHP function unserializing the same data properly in a staging site, but not in product site. Please send me FTP and also staging site’s login info.
Hi,
Our customization team is separate from tech support tea. We sent your quote for the first customization request, you didn’t make any reply there and added created Second Customization Request. May you please clear up the first one first.
Hi,
Sorry for your trouble, I’ve found the issue, it was due to the recently changed plugin folder name. I’ve fixed and released an update, please update to 3.0.7
We shall adjust the title issue with the next update, for now, please add title separately using elementor title module.
It is not activating as any of your active plugins using outdated guzzlehttp library. So, now, I only activated the dropbox closer option ( it works without using API ).
Sorry for the delay, somehow we missed it, shall adjust with the next update.
That message will show for the package/download pages too, probably you are seeing from the cache, please clear the server and browser cache.
Hi,
It is not about download manager, it is WordPress or PHP itself. In staging, if it is working with the download manager using the same DB, means it is not related to the download manager.
Again, it is not even related to the plugin update. May you please discuss with your hosting support once, they probably will be able to explain your better.
It is now accepting again with new packages, now when post serialize function serializing data in a different way, which is not even a custom function, it is a built-in PHP function.
Still don’t worry, We can make a workaround for you, but that’s not the point, may you please ask your hosting support once, what did they change, show them my reply #159022.
The issue was actually with the plugin ( Query.php ), we have fixed it on our side and also updated it there.
The serialization issue is not related to wpdm. It will require custom coding.
Found the reason, a:1:{i:1597129208640;s:16:"malaysia_map.zip";} is not working, when array index stored as integer ( i:1597129208640;) in serialized data, but a:1:{s:13:"1627892469459";s:65:"1627892469wpdm_Fibonacci series in c _ Programming Simplified.pdf";} is working, when array index are string ( s:13:"1627892469459"; ). Only reason for that could be some changes in your server, as it is not a wpdm function. May you please contact server support.