viennamex

My post starts off with “I am checking out your Demo site.”

Then I end with:

“I would figure that your Demo site would be primed for maximum response.

I stopped considering a purchase once this kept happening.”

My “sample link” are all of the Demo Calendars at the Events Manager sales and demo site itself.

Look at your entry. How could anybody know what to say or do from what you have written??

Like, WHAT KIND OF ERROR? How about really describing the ERROR??

Step-by-step explain what you were trying to do.
Explain why the “internal error” message led you to this code.

Help people to help you.

Now I see WHY the Capability to address CSS and modify it is NECESSARY with your plugin!

Adminimize rewrites the page code with its own INLINE redefinitions.

#mw_adminimize_admin_bar {
left: 0px;
right: 0px;
height: 33px;
z-index: 999;
border-bottom: 1px solid rgb(223, 223, 223);
}

#mw_adminimize_admin_bar #mw_adminimize_login {
padding: 8px 15px 0px 0px;
display: block;
float: right;
}

Using Adminimize now means that things like this example have to be REDEFINED if for instance I want to make the LOGIN “FLOAT: LEFT”

All of the settings are in arrays in the wp_options table which are hard to read separately. And I would have to write changes directly into a huge array in the database field itself.

Adminimize needs to allow a way for its new inline #mw_adminimize_ prefix revision to have its own CSS definitions editable.

Adminimize is very good at “taking away” and hiding but it creates a need for me to modify the things that ARE visible when I want to adjust the CSS that is now linked to all of the #mw_adminimize_ rewrites that Adminimize installs.

Premium Press does not like this topic and has not responded to forum and Support Tickets.

Thank you very much, Frank, for your kind response.

When you say “this plugin lists all queries inside the install “

Do you mean ALL Queries even if they are not wp proprietary queries?

I assume since you developed this to help developers that you are also meaning that Custom queries to the same database but to NON-wordpress tables in that database are also exposed when the Query Tab is checked?

Thank you!

Ich danke Ihnen sehr für dieses Plugin!

Now, please, bitte, tell me how I can use it to see what is failing on queries when I am experimenting on modifying some plugins I use a lot.
I asked for various queries to be in the reports and messages while I am working on these queries.

My own error code tells me when a query fails with just a little bit of data from mysql but I principally installed your plugin to first see if it could show me the queries being processed.

I am sure you have this provided for!

I appreciate any help you can offer.

Vielen Danke,

Hamburg Area

Hi Marcus,

Thank you so much for responding to this and for spending time working on it again!

Before I posted here I had experimented with the spacing between the last double quote and the closing tag. I experimented with spacings including spacings between the last focus() and the last double quote and the last closing tag />

None of my experiments helped the issue. I also tried \ in front of the quotes, etc.

I know you have an extremely complex issue trying to create something that works across browsers and servers with different settings for magic quotes, etc.

I am glad you are the expert on this, Marcus.

It is also difficult to post the actual code example on this forum. The code blocks shown with backticks and the pastebin did not solve that problem in posting.

Today I am going back to this issue and upgrade to 1.3 try the settings you mention.

Okay, I see today that my “bad code” was all nicely cleaned up in my comment here.

I have tried to show the actual rendering with dustbin now and the “code” button but this site simply will not allow the actual problem characters to show that wound up in the code such as below:

input name=”Benutzername0″ type=”text” id=”Benutzername0″ size=”1″ maxlength=”1″ onkeyup=”if(this.value.length>=1) document.loginForm.Benutzername1.focus() here is the problem ” />

So I will put a space between each character that was generated instead of the last quote mark ” in each line. Remove the spaces and that was the replacement character string for a quote mark.

& # 8 2 2 1 ;

Thank you, Marcus, for kindly making version 1.1 available to me again!

Hello Marcus! Love the Authentic Mex and Tex Mex in Austin!

So here is the issue that I started getting as soon as I upgraded your very fine plugin a few days ago:

A WordPress plugin that uses a Username and Password log-in to access a form suddenly partially disappeared as far as the fields required for data input before submission.

The Username was a series of numbers — always a 7 digit number. To make it easier for the user to “count” I separated the Username field into 7 inputs. Each time the user input a number the focus moved to the next field until they had entered 7 digits. It was more user-friendly and lessened mistakes.

Before updating to the latest version of “Preserved HTML..” my code would look like this:

<td>
<input name="Benutzername0" type="text" id="Benutzername0" size="1" maxlength="1" onkeyup="if(this.value.length>=1) document.loginForm.Benutzername1.focus()"/>
<input name="Benutzername1" type="text" id="Benutzername1" size="1" maxlength="1" onkeyup="if(this.value.length>=1) document.loginForm.Benutzername2.focus()" />
<input name="Benutzername2" type="text" id="Benutzername2" size="1" maxlength="1" onkeyup="if(this.value.length>=1) document.loginForm.Benutzername3.focus()" />
<input name="Benutzername3" type="text" id="Benutzername3" size="1" maxlength="1" onkeyup="if(this.value.length>=1) document.loginForm.Benutzername4.focus()"/>
<input name="Benutzername4" type="text" id="Benutzername4" size="1" maxlength="1" onkeyup="if(this.value.length>=1) document.loginForm.Benutzername5.focus()" />
<input name="Benutzername5" type="text" id="Benutzername5" size="1" maxlength="1" onkeyup="if(this.value.length>=1) document.loginForm.Benutzername6.focus()"/>
<input name="Benutzername6" type="text" id="Benutzername6" size="1" maxlength="1" onkeyup="if(this.value.length>=1) document.loginForm.password.focus()" /></td>

AFTER updating to 1.2 it turned into this with the ending value quote character " being rendered as ”
And this stopped the form's inputs from displaying in all browsers.

<table border="0" cellpadding="3" width="400">
<tbody>
<tr>
<td><strong>Benutzername</strong></td>
<td>
<input name="Benutzername0" type="text" id="Benutzername0" size="1" maxlength="1" onkeyup="if(this.value.length>=1) document.loginForm.Benutzername1.focus()”/>
<input name="Benutzername1" type="text" id="Benutzername1" size="1" maxlength="1" onkeyup="if(this.value.length>=1) document.loginForm.Benutzername2.focus()” />
<input name="Benutzername2" type="text" id="Benutzername2" size="1" maxlength="1" onkeyup="if(this.value.length>=1) document.loginForm.Benutzername3.focus()” />
<input name="Benutzername3" type="text" id="Benutzername3" size="1" maxlength="1" onkeyup="if(this.value.length>=1) document.loginForm.Benutzername4.focus()”/>
<input name="Benutzername4" type="text" id="Benutzername4" size="1" maxlength="1" onkeyup="if(this.value.length>=1) document.loginForm.Benutzername5.focus()” />
<input name="Benutzername5" type="text" id="Benutzername5" size="1" maxlength="1" onkeyup="if(this.value.length>=1) document.loginForm.Benutzername6.focus()”/>
<input name="Benutzername6" type="text" id="Benutzername6" size="1" maxlength="1" onkeyup="if(this.value.length>=1) document.loginForm.password.focus()” /></td>
</tr>

[Moderator Note: Please post code or markup snippets between backticks or use the code button. Or better still – use the pastebin. As it stands, your code may now have been permanently damaged/corrupted by the forum’s parser.]

Why your plugin would be involved is because the plugin output is rendered through shortcode on a WordPress page.

As far as I recall your previous version of this plugin did not impact the output of all of these ” quote marks.

I tried various ways in the plugin code itself to isolate and stop this from happening but your latest plugin version saves the worst for last on every line. That last quote mark gets “special” treatment. I found before that placing a ; after each focus() made no difference in the functionality so I removed them, by the way.

So, unfortunately, I have to deactivate your spiffy plugin for now.

There is a discrepancy at the author’s page

https://www.cliconomics.com/exclusive-content-password-protect/

In his video he only shows using bracket code [password-protect] content stuff to protect [/password-protect]

THIS WORKS.

But in the text portion of the page it instructs users to code it this way — to precede and follow with the [sd] and [/sd]:

Go to your post/page and put [sd][password-protect][/password-protect][/sd] short code to protect certain section of your content.

Note: You must enclosed your content like this [sd][password-protect]your content here[/password-protect][/sd]

These [sd] and [/sd] are not supported in the plugin functions.

When removed password protect works just fine.

Hello Tobias, as you know by now I have replied to you in private.

Sorry to be the bearer of less than glad tidings this Holiday Season!

As I have already written to you in the past hours I would love to return to this forum and give you much applause and praise for a great plugin! I would be thrilled to come back and say this problem is solved and that I was able to use the other fine features that you promote as part of your plugin.

All I am asking is that you modify your plugin so that it does not immediately start loading every single row of a table when you have no way of knowing just how big any user’s table might be.

In SQL, as you know, of course, it is a simple as specifying “LIMIT 0,30” as part of the SELECT query of that imported table.

And your documentation does not warn the user that a newly imported table will simply reload as a SELECT * …. immediately.
Your documentation gives no warning about restricting a table to having no more than x amount of rows because your plugin will immediately try to load up the ENTIRE table and display it with no limits on the number of records it will keep loading.

I would put in the default “LIMIT 0,30” display limitation myself so that I could then work with your plugin but I can’t find the place in your code where it would put that limitation into effect.

At any rate, this just looks like an oversight that is easily corrected by the plugin creator.

That one change would allow me or anyone importing a large table to watch the table quickly load and be ready to work with without causing the browser to go into a lockup and have to be shut down over and over when your plugin was invoked in the Admin editing area.

I thank you for considering this change.

The best of the rest of the Holidays to you from Wien.

Table Options poorly defined. Documentation only talks about one of the Optiions, not the Extended option. Does not explain clearly the differences between the 4 options. does not even discuss all of the options.

This Plugin needs to set some VIEWING PARAMETERS FIRST!

I cannot use the Editing tools if this Admin Edit view does not apply PAGINATION first!

The editing view must be the first thing that is limited so that the page restricts itself to 10 or 20 or 30 rows with pagination just like phpmyadmin.

I cannot use this plugin if it is not modified to give a more sophisticated restriction to table viewing as the default setting.

I just made the mistake of going back in to Admin to examine WP-Table Reloaded and the large table I just uploaded. Apparently this plug in is way, way too simplistic.

It seems to make the assumption that displaying ALL of the table at one time on one page is quite alright for all situations.

This plugin promises that I can Edit the uploaded table but it is impossible! It wastes bandwidth and time trying to show the whole table from row 1 to row 2912.

I cannot find any way to work this table the way WP-Table Reloaded calls for its display. This is amazingly shortsighted!

I have to shut down my browser again!

Another thing that I am surprised about is that the Import Table options do not include SQL Import??

The SQL Import file also gives instructions for column names, field types, collation, auto-number, etc. Why is the single most useful Export and Import method for WordPress tables or any mysql table purposely OMMITTED?

It does not make any sense.

SQL files take care of everything important in one step!

magic-wordpress-filter-categories disabled wp-admin dashboard when I uploaded it by FTP to my plugins folder.

I did NOT ACTIVATE it. Just sitting in the plugins folder it interfered with my WordPress 3.2.1 site.

I had to Delete this plugin — folders and files completely to get my WP-Admin dashboard to work again.

I tried this twice and both times it created white page errors when logged in as the Admin that I did not have sufficient permissions to see any administrative page.

It was not even officially ACTIVATED.

Something in the Install hooks may be the first incompatability with WordPress 3.2.1.