hughhempel

Don’t expect one click at all and fully agree with your point…

I can envision an “interim” step in your current sync process which would simply display a list of current (unassigned) cf fields and allow those fields to be selected (by check box) for “add” to sync for that group…

I am not a code warrior, but I suspect that the code to display that list with a check box is pretty trivial (maybe 20-30 lines).

I further suspect that the code required to take the “array” created by that checkboxed list submission and run it through your sync process as if those cf names already existed in the CFS meta table would be pretty “doable”…

Sure, I can brute force the issue with a bunch of typing (and fixing typos), but it seems so “arcane” given the fact that the existing cf name/slug data is already readily accessible in the DB…

I defer to you code warriors. I am sure if it was as easy as I believe it to be, you would have done it already or simply said “good idea, I’ll give it a try”…

I wish I had the time and skills to throw together a sample snippet for you… Would love to pitch in to the effort! Alas, I wish I could sing too… Just not in my skills portfolio…

At this point, I am likely to pursue the “brute force” version… As you said, it doesn’t take that long and I already spent more time on this email than it would take to do it manually… :~)

Keep up the enthusiasm and great work!

Ok… Thanks…

The reality is that CFS does very little to help with the migration of the CF fields… It is an entirely manual process requiring the retyping of possibly 100s of custom fields by Name (not slug) into the appropriate CFS “group”…

As I said above, it is a stretch (at best) to claim that “migrating existing CFs is easy”…

Truth is, you are required to effectively “start from scratch”…

I am going to go back to the drawing board and look for alternatives… I suspect that I am going to run into similar probs with all the other plugins however…

It seems that no one has yet really effectively tackled the REAL challenges of using existing CFs in a new framework…

I am sure that your plugin is fantastic for “fresh” installs where manual creation of CFs is expected… I was hoping that you had some “magic” for those of use with old sites needing to move forward…

Thanks again!

OK…

1) I created a new CFS group (test).
2) I have MANY existing CFs
3) I go to “synchronize” and select “test” as the group to sync
4) I get “Sync Successful”
5) I go to the “test” group UI
5a) Nothing has happened… No fields are added…

What logic does the CFS sync apply to “scan your existing custom fields, mapping any applicable values into Custom Field Suite.”?

Do I need to manually add the existing CF slug as a “new field” in my CFS group before sync? How does CFS decide what fields to sync?

Thanks again!

This was a totally fresh install of CFS.

There are 2 other possible explanations:

1) I started out trying Advanced Custom Fields Plugin and abandoned the effort after bad experiences with compatibility. This does not explain the DB issue as ACF does not create a similar DB name

2) I enabled/disabled/enabled CFS during a period of time where my system was a bit “unstable”…
I don’t feel compelled to chase the issue since things appear to be working, but I thought you might want to know…

I will report any future glitches…

I think I am finally getting it… Let me give it another try and report back…

Thanks for your patience and understanding!

Thanks for the reply!

Correct me if I am wrong, but from what I interpret you are saying above, it appears that unless my existing WP custom fields already have a “cfs group” assigned (in the meta table), the “sync” feature will not ‘map’ them to the CFS group. This seems to be a chicken/egg condundrum.

Perhaps you are telling me (not so clearly) that I must “manually” create the CFS groups AND the “corresponding (existing) CFs” from within the CFS UI so that the “sync” feature can then take action???

If this is so, I suggest that there is no “easy” way to add existing Custom Fields to a CFS group. I am required to manually recreate (re-type) my entire custom field list from within the CFS UI?? It seems very cumbersome and typo prone…

Your plugin description says: “Quickly and easily migrate existing custom fields into CFS”… I do not see how this is a true statement under my current assumptions about how to make this happen.

I suspect instead, that I am missing something really obvious here…

So I will re-frame my original question in the hopes to get some clarity:

“Does CFS provide any tools to “scan” for existing CFs and then “assign them” to either “new” or “existing” CFS groups when the existing custom field DOES NOT already have a group assigned by CFS or other method?”

The analogous capability exists in the “TYPES” plugin where they provide a list of existing CFs and allow the “assignment” of that custom field to “Types” control…

Sorry if I am just being slow on the uptake here, but there is nothing in your documentation or in the support forum that does a reasonable job of explaining clearly how to migrate existing CFs…

I appreciate that plugins are “volunteer” and applaud your efforts. Don’t want to sound unappreciative at all! Just trying to make it work if possible.

Thanks again!

I “might” have experienced the same exact problem as Jay. I am unable to reproduce at the moment as “wp-Views” will not activate at all after what appears to be “corruption” that resulted when my “views” changed to “posts”… I love your switcher program and think that Types/Views has potential, but the plugin conflict makes me very nervous…

Will advise if I am able to recreate and assist.

The process suggested directly above for defining two separate lines with First/Last does not work as described. The admin labels need underscores… so your labels should read “first_name” and “last_name” (without the quotes) respectively.

Thanks for the reply…

I do like Meteor and for “static” images it is great!

I will use NIVO and/or Easy Rotator for my post-thumb widget requirements instead… I recently discovered that both of these tools provide the functionality required without hacking templates…

Thanks again!

Hi Marquex,
Really great plugin! Nice work…
I am sure someone already asked, but is there a reason that you label the “replacement” sidebars “sidebar-1, sidebar-2, etc…”?
Since my site has 11 active sidebars, it would be ideal to have the names of the sidebars (visible in your admin UI) match those displayed in the “edit page/post” areas…
This capability would make this plugin perfect! I would donate to have the work done…
Please advise,
Hugh

Hi Alex,

Thanks again for you post/reply and your fix! After a modest amount of testing, the fix seems to have worked… I can upload AND I can smush old files… Congrats!!

My issue now is that the whole process is painfully slow… When I upload a 70k .png image, the upload is almost instant, but the “processing time” until I get my “media library” screen back is 20-30 seconds…

For my shop, this amount of wait time is not viable…

It occurs to me that this plugin processing could happen in the background allowing me to go about my business without waiting for the plugin to actually process the SMUSH…

I reiterate how wonderful this plugin is conceptually and I encourage you to stick with it!

Thanks again!

Hi Steve,
I would also vote to either allow the user to set this limit OR simply increase the number of characters to at least 250… really no reason to limit in my mind…

Great plugin! Thanks for you work!

Thanks for the reply Alex!

I did as you suggested… Same outcome…

For the first time I got a red HTTP error message that I did not see before… You can also see that the “crunching” message is “frozen” and I am forced to abandon the upload by clicking off the media upload screen…

One of the screen grabs shows how the media loader (with WP SMUSH.IT enabled) is unable to accurately process the image to capture the proper size…

The third screen grab shows that the actual image is uploaded and the thumbnails are created (but media library is still hosed because it does not know the “actual” dimensions of the image)

This screen grab shows the media library BEFORE I attempt to SMUSH manually and this screen grab shows the media library error message AFTER I attempt to SMUSH manually (resulting in the could not find message discussed above)…

I hope some of this info helps to debug… I am forced to deactivate WP SMUSH.IT as it literally prevent my Media Library from functioning whatsoever.

Once again, thanks for the prompt response and a GREAT plugin!

I am experiencing the “could not find” issue described above… About the only change to my system since this problem started was an upgrade to WP 3.05

The error message is:
Could not find /home/sparkpr/public_html/wp-content/uploads/ RESMUSH

I am running the latest (re-installed fresh copy moments ago) version of WP SMUSH.IT

Any help would be most welcome! This plug in is GREAT!!

Same Problem here… I found 2 (Search_Post_Module & Search_Comment_Module) of the 4 “classes” mentioned by Lembit… Can someone specify the other 2 classes and confirm that they are located in “search-module.php”…

I love this plugin, but I am unable to POST after making the proposed changes…

Running 3.04 and 1.0.6

Where the heck is the author in all of this??? How can there be a “new version” as of January 6, 2010 and this known issue (more than a year old) was not addressed or mentioned…