melkerh
Forum Replies Created
-
Hello,
That’s a pity because my site is live now, and I can’t have my site broken in order to show you the error. Have you tried looking at the comments made with your plugin on the “Twenty-twenty” theme?
Regards,
MelkerThanks Mark.
I’m now making some progress…it seems this plugin is lacking some basic input checks. The error over here was due to not having selected the Form Type, and IMO there should be some kind of warning before one is allowed to save or update the form. Once I selected Registration/Profile/Login, the data is shown both in Live Preview and on the page with the shortcode.
Thanks for the reply, not stupid at all. Yes I did save the form, and also tried adding and updating it with more fields…no go. I’m working on localhost with OSX and everything else seems to work since I could install WordPress and this plugin without any problems. Are there any external network requests necessary for this plugin to function properly?
I now remember having read somewhere that Ultimate forms can’t be created from scratch, is that correct? What I did was just create a new form and add some fields.
Thanks, I’ve made some progress with this and it’s starting to make sense.
I suppose this means that a UM form can’t be simply dropped in on any page? One must edit the default UM pages and put user-specific shortcodes on those…right? My issue with this is that there doesn’t seem to be a way to not show the default fields and only show the custom ones.Just to clarify, I have two different shortcodes that correspond to two different forms on the same User page, and they only show the same User info TWICE: Name, profile photo and banner, About, Posts, Comments.
[ultimatemember form_id=6] [ultimatemember form_id=42]- This reply was modified 8 years, 3 months ago by melkerh.
Same problem here on WordPress 4.5.3:
Putting an existing username in the input box “Search for users” and pressing return makes the user and its email appear above the box, but clicking “Add Members” has no effect… Trying with Firefox and Chrome.
Also, the list below says “No members found.”There’s also a field in Edit User called Access Levels which does not respond to input either.
Wow, I get a timeout too now on the first request. Arvixe isn’t helping much at all, and I’m now considering contacting a higher level representative there (if possible).
What’s puzzling is how the XML-RPC request can time out only the first time, seems like voodoo. Could you maybe help me with a snippet of code that repeats the same Publicize connect request within, say, three seconds?
I really don’t like the idea of having to change hosting provider just for this.
Arvixe hosting can’t seem to figure it out.
I’ve even opened a new free hosting account at X10hosting.com and installed WordPress+Jetpack, and Publicize will connect, though jetpack-debugger fails. The plugin Query Monitor says: 400 Bad Request GET https://jetpack.wordpress.com/jetpack.testsite/1/
?url=http://(xxxx).x10host.com/xmlrpc.php. Loading /xmlrpc.php through the browser returnsXML-RPC server accepts POST requests only.Returning to my main site, I don’t know how to proceed now. A fresh install doesn’t work. Arvixe at least seems to have corrected something, since the command
curl -A 'Jetpack by WordPress.com' -d '<methodCall><methodName>demo.sayHello</methodName></methodCall>' http://melkeramik.com/wq/xmlrpc.phpreturns Hello at the first intent now.PHP version is 5.4. Other possible culprits? Server cache? I don’t use Cloudflare or the likes.
Thanks. I’ve tested this same command now from my computer, and the following happens:
The first time there’s an instant timeout, but if the same command is sent again in less than a minute, it returns<string>Hello!</string>. If one waits more than approximately a minute it throws the same error again — though the response comes so instantly that it’s hardly a “normal” timeout. I don’t know if this is a server issue or not, but I’ll open a support ticket with Arvixe.Forum: Plugins
In reply to: [IndieWeb] Tried and tried…h-card validation errorThank you pfefferle! OK, so just to confirm:
If in addition to the homepage h-card widget, my author page (using SemPress) has all the relevant info and social links then I’m good — right? And any author who has filled out his/her info on the author page will get a valid h-card, although the site’s main h-card has a different author’s data?(And I insist, all this would be so much more popular and used by so many more if there was a central, comprehensive, hands-on tutorial for the main CMS and blog systems like WordPress, Joomla etc. Documents like https://indiewebcamp.com/authorship (for example) are very technical and should only have to be consulted by developers and coders, not by people who just want to manage their own WordPress blog and social presence. I really, really appreciate all the heavy lifting that has gone into IndieWeb, but there has to be a simpler user experience if you want this to get more popular.)
Thanks again for your work.
Forum: Plugins
In reply to: [IndieWeb] Tried and tried…h-card validation errorThanks Chris! That got the validation working. Oops a couple more questions pop up:
- Is an h-entry necessary if I’m the only author on the website? And if so, where does one configure this in WordPress? There seems to be no simple info regarding this online.
- Why on Earth isn’t the information you’ve given me an integral part of the SemPress theme that supposedly makes these functionalities easier? Or a read-me or walkthrough on the install screen perhaps? I know lots of people that would probably benefit from IndieWeb features on their craft sites, but either they don’t even know this exists or they find it too complicated to set up.
Thanks again for your help,
MelkerI’m unable to replicate this error, but later on the computer I could see that the post had repeated text — no error by Jetpack.
qTranslate Plus doesn’t seem to be maintained anymore, so I doubt if it’s worth the trouble to investigate further. I’ve disabled it and will use something else instead.
Sorry for the false alarm 😛
Sorry! This may be a conflict with the qTranslate Plus plugin for WordPress. Anyhow, I don’t know if this really is qTranslate Plus’s fault per se or if something should be changed in Jetpack to filter away multi-language content.