ronin Creativos

friend, the error is still there (after updating to 1.10.5)

the changelog in the install folder enumerates the fix, but the code apparently does not reflect it. commenting out the original 118 line and pasting the lines above in this thread has fixed the issue indeed.

please verify your upload ??

thank you

hi,
unfortunately, its not that simple. these folks tend to hit the send button many times *before* any message (error or success) is shown, in hopes the message is “delivered faster” so to speak, resulting in several submissions sent.

i did manage to disable the send button on press, via jquery in a customized page template/footer (clicking in a control of the form will enable it again, so user can make corrections or fill up required fields). not perfect, but lets see how effective it is ??

i figure cf7 would have to disable the button on click, make the proper checkings (when its showing the spin image) and if everything is ok, send the message. otherwise, give the alert response and re-enable the submit button. i could have tried do this in cf7 directly but then i would have lost the changes upon plugin update..

thanks anyway ??

if youre using Contact Form 7 you *must* disable “send email as html” below CF7 email template options for it to work ??

yeah i saw the add-on but its not quite what i need ??
thnx

mmm well, what i need is for a user to see everybodys files in the front end, even if that user doesnt own it or did not create it. giving one user “private files” access does this, but only in the backend. ??

Unfortunately i cant, since this is the only site i manage which uses varnish and is a store in production (dreamhost dreampress site), so i cant run tests either. i knew it was this plugin cause it was the only one i had upgraded and as soon as i renamed the plugin folder, the site did load.
during the outage, the site was completely unaccessible and gave 503 error but no further details beyond that “guru meditation” thing. support did mentioned something related to memory, but no more details. i did try disabling varnish first by renaming that folder but it did not work. only when i prevented GAD from loading. i also did upgrade this plugin in other sites without error.

hi.
could it only read the files inside all dirs within the main dir in the shortcode? like a “flat view”? ??

hi there. i was also having this “issue”..
so if i set a custom role “pseudo admin” which has no access to the wp backend, then that user cannot see them files correct? however, having this access, i can click on “view file” (in the backend) and oh surprise: i land in the front end with the file listed. why doesnt this simply work out of the box with a list of all files? thats what the “admin” (not the wp operator, but the one overseeing the files that is) should see after all. hopefully i described this one ok ??

where do these outgoing connections go? a particular ip address or domain? (i may have to white list them)

yes exactly. its same error, thats why i asked here. though i already opened a thread about it here
thanks

hello Alin
you said in your last comment that “the issue was already discussed” but i cant find the post where this specific error was addressed. can you please point me in the right direction. i appreciate it. thank you ??

go to that file super-link-preview.php and comment out this line:
// $urls = [];

and then it works ??

heh- that explains a lot. ive had some trouble before with WPBE, but didnt quite pay much attention to it.
ill take a look at the other plugin you suggested. (in another thread)

great plugin and work (btw i recall being reluctant to install your plugin before, on the account of kevin costner being featured in your header =)) –not the best movie to be related to ?? j/k)

thanks, mate

huh. guess what. [apparently] i have to create the key *after* a bucket is created for it to work –oo fancy that. now onto it.
thanx for your help <3

alright. uninstalling wp-optimize allowed me to reset the keys. but the error persists :[

<<
the lock out was a dreampress memcache issue after the wp update. the guys worked it out =)