After 2.0.0 update – few questions

1. That has been resolved in the 2.0 update
2. Previously the images for the boxes were applied via CSS background property. Now they are inline elements which have the float property applied. Are you running into a specific issue with the new setup?
3. My apologies… the new documentation is located at https://docs.arconixpc.com. I will be updating the fogbugz wiki with a link to the new location today.
4. All the elements are styled via CSS whether it was pre-2.0 or not. Or perhaps I don’t understand your question?
5. It is possible, yes, but I’m not sure to what extent. I’ve tried to maintain as much backward compatibility as possible — where shortcode parameters are no longer used I transitioned those values to the new ones to ensure they don’t just break — however I did fundamentally change the construction of the boxes, and I’m not sure what other issues you may run into. In the includes/css directory, there’s a file called arconix-shortcodes_old.css. If you copy that to your theme’s directory and remove the _old part so that it reads arconix-shortcodes.css, my plugin will load that file in place of the new one. You’ll have to update the paths to the images as noted in the file as normal.

All that said, I did make a branch of the 1.x plugin, so if you’d like to use the old version with the fix from #1 implemented, let me know and I could certainly get that done. You’d simply have to deactivate the existing plugin and upload the “new” one.

1. Ok, thanks.
2. It’s not really an issue, it’s more like feature i don’t really like, let me show you what i have on my mind:
https://s29.postimg.org/ppuq1rglj/icon.jpg
(pardon my paint skills)
i would like to have it on “before”.
3. Good to know. You should include graphical examples for Shortcode References, just a suggestion ??
4. It’s ok – sometimes those kind of things have styling included in some kind of settings in Admin Panel, that’s why i asked.
5. I just want to have old boxes look – nothing else, i can use 2.0.0 – i have no problem with that. Information you included will be sufficient for that?

2. I understand now. I agree that is not ideal. I’ve added it as an issue and I will be looking to address it asap.
3. I welcome all feedback. What kind of graphical assistance do you think would be helpful to have?
4. No admin panel on my plugin
5. If you just are looking for the boxes setup to improve, there’s nothing you need to do. I’ll be getting that fixed asap.

Thanks!

3. I think that simple screenshots like in here:
https://arconixpc.fogbugz.com/default.asp?W5
would be sufficient ??
5. The thing is i would like to have pre-2.0.0 boxes layout ?? The new one is not really cooperate with my template style – and if possible i would like to make it without reorganizing whole CSS.

Just an fyi, I fixed the vertical alignment issue and will be releasing the update soon

Ok so once again regarding point nr 5:
I used old css file and boxes layout work as it should, problem is that images still does not work…

I just copied “images” folder to my template root folder then changed paths in css file from:
../../images/
to
images/

and it still does not want to read those images – what i am missing?

EDIT: Ok, two other problems:

Tabs now looks like this:
https://s16.postimg.org/3ritpjmit/tab.jpg

and there’s still icon issue with old css:
https://s27.postimg.org/m1zckt0pv/box.jpg

Off the top of my head as long as the path is updated the images should work if you’re using the old css file. Have you viewed the boxes in Firebug or Chrome Developer tools to see what might be going on (404 error on the images, CSS specificity, etc.)?

Regarding the toggles, I forgot I’m applying some CSS items via jQuery. Save the following into the root directory of your theme https://raw.githubusercontent.com/j-gardner/arconix-shortcodes/v1.2.0/includes/arconix-shortcodes.js and that part should be resolved.

Version 2 introduces issues with backwards compatibility to previous versions. It’s why I gave it v2.0 as opposed to v1.3. Ultimately if you were happy with v1.2, it may make more sense for you to use that version than try to get v2.0 to look like the old version.

Copied included file in theme root folder and no effect :\

Also i checked chrome dev console – no errors regarding icon, from what i saw icon still uses class:
.fa.pull-left from font-awesome, is it as it should be?

there’s no image reference in dev console – just like something is overwriting it.

I was happy with 1.2 yes, but in future when you will update it to newer versions, then it might be problem later with WP incompability etc. and i would like to use this plugin on other websites as well ??

oh, and as of 2.0.1 I have the icon alignment fixed: https://demo.arconixpc.com/box-test/

yes i installed 2.0.1 and icon aligment fix worked for new layout, for old i’m still fighting with it does not unfortunely :\

ok, so to remove the pull-left, use the box parameter icon_other and set it’s value equal to an empty space.

[box icon_other=" "]

If you want to configure it so you don’t have to set that value each time you build a box you can set a filter to default that param. See this gist for an example: https://gist.github.com/j-gardner/6475499

The more I think about it, I think I know why the images aren’t working. Previously, when using the old setup, building a box was

[box style=download] [/box]

or

[box style=blue] [/box]

it would assign the box a class of .arconix-box-download or .arconix-box-blue respectively. But because we can use FontAwesome icons now, I couldn’t keep that style parameter. Now if you use

[box style=download] [/box]

On the backend I convert the style param into an icon=fa-download and color=green so .arconix-box-download is never applied. This is an instance where I broke backward compatibility from the position of being able to re-use the CSS exactly as it was before. Now you’d effectively have to re-code that section of CSS and split it into 2. 1 section would apply the icon and the other would apply the color. It could be done, but it’d be a bit of work.

ah, so after all it’s easier to just use 1.2 i’ll just probably go with it…

just tell me – is there anything in 2.0 that i will specifically miss in older version?(like optimization or something)

I have no problem with adding classes to CSS, if it would not be a half-measure, but from what i understand it still would be just temporary.

What you see in the release notes is really what you get:

Other - Removed the googlemap shortcode. There are other plugins available that are better for the task. If you are currently using my googlemap shortcode, please add code from this link (https://gist.github.com/j-gardner/0f3adc735eb9ec7b5b39) to your theme's functions.php file to add the shortcode back in
Feature - Updated the color spectrum to be more modern and support more default colors.
Feature - Added support for FontAwesome icons with most shortcodes. The entire list of icons available here: https://fontawesome.github.io/Font-Awesome/icons/
Enhancement - Added 2 additional button styles (flat and clear) which gives users additional display options
Enhancement - Remove the MSIE specific filter property which was preventing sites from passing a W3C check
Enhancement - Minify the CSS which improves download time and site speed
Enhancement - On relevant shortcodes (accordions and columns) the use of last=y is no longer necessary as last by itself will work
Enhancement - Improved sanitization strings which should fix broken output in certain non-English languages
Fix - updated the function names so there should no longer be conflicts with other themes/plugins/frameworks

Whether that’s stuff you really want or not is up to you. If you go to the shortcodes-1.x branch of my GitHub repo for the plugin, I have already added the bugfix from 2.0 to that, so you at least get that benefit. The features and most of the enhancements are all CSS-focused and could be replicated without too much difficulty… they’re probably mostly nice-to-have as opposed to can’t-live-without.

ok good to know and thank you for your time ??