Ian

I found the solution so issue is now resolved, here’s how, for anyone else that’s having problems:

The directory structure for the contact.php file should be:
/my-theme/wp-car-manager/single-vehicle/contact.php

• This reply was modified 5 years, 8 months ago by Ian. Reason: Forgot to mark this as resolved

Hi AlanP57,

I can also confirm that the update fixed the PHP warnings ??

FYI, the layout issues were still present at first when I updated the plugin to 3.3.2 but disappeared shortly after, I assume my browser had cached some css files from before the update to 3.3.1.

The only issue that I still wonder about is, I no longer get asked to choose between “Display Images” and “Display File Names Only”, when I have a lot of images in a folder. I’m guessing you may have temporarily removed this feature in order to provide a quick update fix for the PHP issues?

Finally can I send you a massive thanks for such a quick resolution to the issue.

Regards,

Ian

Hi,

I have just updated Media Library Folders from version 3.3.0 to 3.3.1 and immediately discovered similar issues with the 2 warnings appearing when I edit a PAGE.
The first warning I receive relates to the method ‘mlp_media_button’ and the 2nd about the method ‘mlp_button_admin_footer’.

The errors I receive are not displayed in the page itself like Guy. I have the WP PHP Console plugin installed on my site, so the errors are being displayed as a notification by the associated Chrome plugin.

In addition I have issues with the admin screen for Media Library Folders.

When browsing folders, after the Ajax loader gif disappears it takes around 4 seconds for any images to appear. When they do appear I have to scroll the page to see the images.

If the folder has a lot of images I see a message asking me to choose whether to show images or filenames. The message is split in 2 parts, the first part appears above the main buttons (Copy/Move, Rename, Delete etc.) and the rest appears above the buttons to Display Images and Display File Names Only. Clicking on either of these buttons does nothing.

As it is this plugin is now unusable, so I hope you can resolve these issues as soon as possible.

Regards,
Ian

This issue has been flagged on the GitHub repository above, as a bug due to be fixed in the 1.3.6 release. No date is given for when this version will be available.

Reported on GitHub: https://github.com/CalderaWP/Caldera-Forms/issues/613

Same here but it doesn’t seem to happen for all select fields.
After trying to track down what’s different with the fields that are duplicated and those that aren’t the only thing I could find was as follows:

The values of the select fields that are not duplicated allow the user to choose imperial sizes such as 4ft 10″ or just 20″. Don’t know if it has anything to do with it but it seems strange, or a coincidence, that those that are not duplicated contain the double quote character.

Just tested the above. I created a small form with 2 select fields.
In the first I added the values 1, 2 and 3
In the 2nd I added the values 1″, 2″ and 3″

Submitted the form multiple times then swapped the values around. (First select with inches and 2nd without). The results were consistent, The fields with an integer are always duplicated in the entry list and those with the double quote were not duplicated. Note: fields containing text but not a double quote are also duplicated so it’s nothing todo with integers.

Obviously once the entry duplication is fixed it won’t matter why this strange behaviour but it might help track down the bug?

I am reporting this on the plugin’s GitHub page.

Caldera Forms Version 1.3.5.3

Hi Jack,

You should find the Geo Mashup menu in the WP Settings menu.

Regards,

Ian

I’ve made some progress.

If I change line 95 of geo-mashup-search.php

from
$geocode_text = empty( $geolocation ) ? $location_text : $geolocation;

To
$geocode_text = empty( $geolocation ) ? $location_text . 'uk' : $geolocation;

it works. Both Perth and Carlisle in the UK are used for the search.

This tweak is obviously not safe from upgrades, is there a different way I can achieve this?

Regards,

Ian

Sorry needed to make an edit and didn’t spot the edit button so posted another message, now can’t delete it. ??

Hi goldenagemedia,

Fried_eggz seems to have posted a link to the wrong thread above.
This is the correct one: multi page

Regards Ian

No problem Fried_eggz, hope all goes well for you.
Not wanting to put you under any additional pressure but I see from your other recent comments that you still hope to get this working.

I have put a demo on my site so you can see that the new functionality does work as described. You can find it at https://iannicholson.co.uk/sticky-list-demo-page/

The page includes 4 different forms: Multi-Page with progress bar, progress steps, progress none and a single page form.

Just let me know when you’re back ??

Ian

Hi again fried_eggz, wondering if you’ve managed to take a look at my code?
Can you give me some info on what happens when you run it?
As I said previously the additional functionality works well on my side, so it’s hard for me to start tracking down any bugs without a bit more info.

Do you see any difference at all on the client side with or without the new code?

I would really like to get this tied up so the new functionality can be added to the plugin .

Regards

Ian

Just made a new commit to repo, realised that I had forgotten to hide the new text box that holds the “Mode” value “View” after testing. This of course doesn’t fix the issue you are having.

Not sure what else I can do from my end at the moment.
As you will see the changes to your code are minor:

class-sticky-list.php from line 860 i add some comments, prepend a new hidden field with name = mode and value = view and finally enqueue a new js file called multi-page-view.js

This js file mainly manipulates css classes and styles to provide the desired functionality.

If you don’t manage to find the issue do you have a live wp install that I can take a look at, assuming the js file is enqueued properly I should be able to debug the code with only client side access to the form.

Regards Ian.

I have tested this in 3 different wordpress sites all running locally on my laptop using Bitnami WordPress stacks. Bitnami contains version 4.4.2 of WordPress so I don’t see this being an issue.

I assume you’ve cleared your local cache? Obvious but thought I should ask. ??

I’m on UK time (11.30 pm) so about to head off to bed, will be in touch again tomorrow.

Ian

That explains it then.

I have now issued a pull request in the correct repo. Looking forward to any feedback and hope to see my code added to the plugin.

Regards, Ian